Re: [Json] Schemas & so on

FWIW -

This general area of discussion came up in the IETF maybe two years ago; can dig around in archives if people are interested, but IIRC it was mostly hallway-based.

I'd characterise the general feeling then as "run away screaming"; the wounds of XSD / WS-* were too fresh.

It came up again more recently (again, the hallway track), and the feeling I got was that people were more amenable to it, but still concerned about the numerous pitfalls.

It strikes me that it might be worth writing down what we think is good in such a beast, and what would be not-good. Getting agreement on that might be... interesting, but if we had such a document (or maybe just a wiki page), we'd be able to evaluate the current contenders, at least.

Cheers,

> On 2 May 2016, at 6:55 AM, Tim Bray <tbray@textuality.com> 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?
> 
> -- 
> - Tim Bray (If you’d like to send me a private message, see https://keybase.io/timbray)
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json

--
Mark Nottingham   https://www.mnot.net/