Re: [Json] JSON Schema Language

[Nico Williams <[e-mail]>]

On Sun, May 05, 2019 at 09:12:05AM +0200, Anders Rundgren wrote:
> On 2019-05-05 09:00, Nico Williams wrote:
> > On Sun, May 05, 2019 at 07:52:18AM +0200, Anders Rundgren wrote:
> > > On 2019-05-05 07:39, Nico Williams wrote:
> > > > On Sat, May 04, 2019 at 06:47:35AM +0200, Anders Rundgren wrote:
> > > > > Example: although 10.0 is a valid JSON Number, in system where you expect
> > > > > an integer, this should be flagged as a syntax error.
> > > > 
> > > > As a maintainer of one popular implementation, this idea that having a
> > > > zero fractional part makes a number non-integer annoys me a great deal.
> > > 
> > > As I described, this is incompatible with other popular
> > > implementations like Jackson for C#.
> > 
> > That sounds like a bug in Jackson.
> 
> It also flags numbers that doesn't fit into the declared type.

That's a different story.

An application may not have control over what its encoder does here, but
it will have control over the semantic values.  So if a value is
expected to be an integer between 0 and 9, inclusive, then 10.0 is not
valid.  But 9.0 must be because there can be and almost certainly are
encoders that will output integers with a zero fractional part.

Nico
--