Re: [Json] Schemas & so on

I don't see any need to specify upper or lower bounds on integers. We don't
do this in C, C# or any major programming language.

We do specify bounds on representation, int32, uint32 etc. But that is more
a matter of convenience and space management. It isn't something we need in
JSON serialization.

What we do need is a model for how to extend JSON based protocols. When is
it allowed to add in new elements to structures? what structures are
backwards compatible with the old? My answers to those being 'always' and
'when the tag is the same'.

On Mon, May 2, 2016 at 9:01 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Mark Nottingham scripsit:
>
> > 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.
>
> Here's what I think the bare necessities are for a schema language.
> This is loosely based on FtanGram, the schema language for FtanML,
> a markup language similar to XML and JSON.
>
> 1) A language for specifying the types of JSON items.  A type is a set of
> JSON items.  If the root item matches the root type and each sub-item
> recursively matches the subtype, then the JSON document is valid,
> otherwise not.
>
> 2) The following primitive types:
> 2a) The set containing only JSON null.
> 2b) The set containing both JSON booleans.
> 2c) The set containing only JSON true.
> 2d) The set containing only JSON false.
> 2e) The set containing all JSON numbers.
> 2f) The set containing all JSON integers.
> 2g) The set containing all JSON strings.
>
> 3) The type of JSON numbers with a specified upper and/or lower bound
> (inclusive or exclusive).
>
> 4) The type of JSON integers with a specified upper and/or lower bound
> (inclusive or exclusive).
>
> 5) The type of JSON strings that match a specified regular expression.
>
> 6) The type of all JSON arrays.
>
> 7) The type of JSON arrays that match a specified regular expression
> over types which match the elements of the array.  The regular expression
> operators are sequence, choice, and bounded and unbounded repetition.
>
> 8) The type of all JSON objects.
>
> 9) The type of JSON objects with specified keys, with the types of the
> values corresponding to those keys.  Keys may be required or optional.
> In addition, a way to specify whether other keys are allowed or forbidden.
>
> 10) The type of all JSON items.
>
> 11) The ability to name a type and refer to it by name.
>
> 12) The ability to define type libraries and import types from them.
>
> Comments?
>
> --
> John Cowan          http://www.ccil.org/~cowan        cowan@ccil.org
> Awk!" sed Grep. "A fscking python is perloining my Ruby; let me bash
>     him with a Cshell!  Vi didn't I mount it on a troff?" --Francis Turner
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>