Re:SVG: The Good, the Bad and the Ugly
by ChrisMarshallNY on Friday February 12, 2021 @12:40PM
(#26116258)
This is nicely done: https://json-schema.org/specification.html
But note "draft."
Compare to: https://www.w3.org/standards/xml/schema
It's been "draft" for years.
Hasn't stopped tooling from being built around it.
Whenever 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.
Lots of APIs pop out JSON.
JSON schema let's you make that a bit safer.
My 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.
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. :)