Re: [Json] Schemas & so on

[Martin J. Dürst <[e-mail]>]

Hello Tim,

On 2016/05/02 05:55, Tim Bray wrote:
> I find myself tasked with specifying a JSON-based DSL and preparing it for
> public release, with a validator and so on.
>
> I had never really concerned myself much with options for JSON language
> definition, but have discovered they’re not very good.  The JSON Schema
> project is not terribly appealing - opaque spec, poor documentation and
> tools - and smells of neglect (last I-D expired in 2013).  It's been
> suggested that a good approach would be just to write a jq program that
> emits true or false.
>
> Is there good conventional wisdom about formally specifying a JSON dialect?

Sorry for playing the devil's advocate, but asking the same for XML 
would give a lot of different opinions. I wouldn't expect the schema 
landscape (if it developed) to be much different, because there's a 
large span between simplicity and expressiveness that can be covered, 
and a lot of notational choices.

In addition to that, many people use JSON because they don't want to use 
XML (if they don't have any actual experience, they at least heard that 
it's somehow "problematic", and that often extends to schemata). So the 
JSON's users tendency seems to be to try and avoid schemata.

Regards,   Martin.