5 comments

[ 1.8 ms ] story [ 24.7 ms ] thread
Please don't let JSON go the way of XML, with namespaces and complexity.
Not meant to be this. It's there to validate data coming from an untrusted source to fit to your data model. The best usecase is a document database (like MongoDB, CouchDB) that uses JSON as data representation. The logic and validation has to be done somewhere and to have standardized way to define constraints is a good start.
Just another textual factoring of a data composition structure?
Even disregarding schema validation, I like that it defines standard JSON representations for vCards, events, addresses, etc.