title: JSON Schema compared with XML Schema and their future
body: <p>I was looking for JSON schema standards and their corresponding php implementations.  Expecting some open source out there and I was surprised, to find only one php implementation.  I was about using this technology (JSON) and the schema lib to parse my incoming browser requests.  </p>
  
  <p>This natural parse/validate activity seems natural in XML and make me wonder why this is not the case in JSON.</p>
  
  <p><strong>I end up with a doubt situation.  Should I pursue my JSON structure data exchange or switch to XML?</strong>  I first chose JSON for its simplicity and less verbose syntax compared to XML, but if I have to redevelop all existing standard in the world these arguments becomes lighter.  I also chose JSON hoping to limit the size of communications between my web server and my mobile apps.  Playing with comet apps, XMPP seems to be implemented and used by big names like Google, Facebook, for their real time chat chat text or video based messages.</p>
  
  <p>So the actual questions are:</p>
  
  <ol>
  <li>Is JSON for the poor web server developer that wants to know what happen on its traffic, and focus on over simplicity (do not be mistaken, here, I include myself)?</li>
  <li>Does IETF draft for JSON schema is a serious work, since only few implementation exist on the server side (PHP)?</li>
  <li>Am I missing something, or maybe, the best communication pattern is to send data in xml to the server and expect a json response (many json schema implementation exist in javascript)?</li>
  <li>Or did I only faced the actual proof, that this concern has not been well served by the developer community because web developer using JSON do not test deeply their incoming request data?</li>
  </ol>
  
  <p>Please help me understand, I am missing some experience here?</p>