3 ms·
> JSON Schema is a non-starter. No one ever seems to use it, and I don't think it ever made it out of committee. It pretty much goes against why JSON is popular
by com2kid 6y ago
> JSON Schema is a non-starter. No one ever seems to use it, and I don't think it ever made it out of committee. It pretty much goes against why JSON is popular.
My company heavily uses JSON schema.
The OpenAPI project uses JSON Schemas, and AWS also allows for their usage in places.
And finally, there are a couple good projects that automatically generate JSON Schemas from Typescript definitions, which is my preferred way to go. :)
- ChrisMarshallNY 6y agoThis is nicely done: https://json-schema.org/specification.html https://json-schema.org/specification.html But note "draft." Compare to: https://www.w3.org/standards/xml/schema https://www.w3.org/standards/xml/schema
- berkes 6y agoWhenever I encounter JSON schema, It makes me aware that the important difference between JSON and XML is not the syntax (my IDE handles that fine), nor the features. But the difference in rigidity. JSON when agility is needed. XML when rigidity is needed. I fail to see any benefit of a rigid, typed, schema'd JSON that XML does not offer more naturally.
- com2kid 6y agoLots of APIs pop out JSON. JSON schema let's you make that a bit safer.
- berkes 6y agoMy point is that if they need this "safer", why not pop out XML instead. The largest benefit of JSON is that is not XML. That it doesn't get bogged down in schema's, strong typing, interfaces, contracts and so on. You loose all that by turning JSON into XML-written-in-a-different-syntax.