Re: [Json] Nudging the English-language vs. formalisms discussion forward

["Pete Cordell" <[e-mail]>]

----- Original Message From: "Nico Williams"

> I really want any JSON schema to be expressed in JSON itself: we all
> have JSON parsers, so at least the first step is done and we won't
> have to worry about how difficult it is to write LALR(1) grammars for
> ASN.1 or whatever.


Personally I think it's more important that the schemas are easier to read 
and write by a human.  Compare:


    int<0..65535>? port;

to:

    [ {
        "name": "port",
        "type": "int",
        "minOccurs": 0,
        "maxOccurs": 1,
        "minInclusive": 0,
        "maxInclusive": 65535
        } ]

Comments are also nice in schema!

An important consideration in designing a schema like the above is to have 
some kind of 'escape' mechanism for extending the definition such as 
attributes and annotations in C# and Java.

Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com