Re: [Json] Schemas & so on

[Austin William Wright <[e-mail]>]

On Sun, May 1, 2016 at 1:55 PM, Tim Bray <[e-mail]> 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?
>

JSON Schema _is_ an active and ongoing effort. But as is usually the case
with anything powerful and self-descriptive, there's a lot of problems that
will crop up, a tiny few of which we've identified for the next release,
but still certainly plenty more. This is compounded by the fact JSON Schema
is hypermedia.

We're actively soliciting feedback for a release at the GitHub repo:
<https://github.com/json-schema-org/json-schema-spec>

We'd like to hear what relative weaknesses you've encountered, and
comparisons to other technologies. As far as tooling goes, there's a
standard test suite, and as far as I'm aware JSON Schema has more
implementations than anything else.

Thanks,

Austin Wright.