Re: [Json] JSON Schema Language

[Nico Williams <[e-mail]>]

On Mon, May 06, 2019 at 02:26:43PM -0700, Austin Wright wrote:
> > On May 6, 2019, at 14:15, Nico Williams <[e-mail]> wrote:
> >>> On May 6, 2019, at 12:24, Nico Williams <[e-mail]> wrote:
> >>> Because some of us have generic parsers with associated DSLs and we
> >>> don't want to be left out.
> >> 
> >> Left out of what, exactly? See below.
> > 
> > Out of interoperating with other applications using this schema thing.
> 
> You’ll need to provide a specific example, I think there’s a misunderstanding.

I did.  Any application that uses an off-the-shelf generic parser and
encoder and does schema validation in a different step.

> > I explained how this would preclude use of jq or any other XSLT/XPath-
> > alike for JSON from interoperating with applications using such a schema
> > language.
> 
> I never suggested this. While JSON doesn’t specify what an “integer”
> is (i.e. we could define it to be any subset of number that we want),
> JSON Schema tries to be liberal and specifies that excessive precision
> still qualifies as an integer. (I’m the one who added that language.)

Then accept 10.0 as an integer.

Nico
--