> The insistence of the JSON-people to sabotage any kind of data validation is absurd to me.
I don't understand what you mean by this. JSON supports schemas which can be used to validate input. It's not super advanced, but it's functional.
I don't understand what you mean by this. JSON supports schemas which can be used to validate input. It's not super advanced, but it's functional.
JSON itself succeeds as a way to represent JavaScript objects but it is far less useful than XML for representing custom types, which are easily enforced through XML Schema.
JSON Schema adds some of this, but it isn't a standard (yet).
It just about works, but it's horrible to write and horrible to maintain. What you can actually do with the validation is surprisingly limited in some forms and the fact that you have to write JSON to write the schema shows just how non-user-friendly JSON is.
A friend told me that she writes JSON schemas in YAML and then uses a build step to downgrade that to JSON for the actual validator. I wish I'd thought of that.