Re: [Json] JSON Schema Language

[Austin Wright <[e-mail]>]

> On May 4, 2019, at 22:56, Carsten Bormann <[e-mail]> wrote:
> 
> On May 5, 2019, at 04:51, Austin Wright <[e-mail]> wrote:
>> 
>>> On that web page, it also says “For consistency, integer JSON numbers SHOULD NOT be encoded with a fractional part.”
>>> 
>>> What does that mean?
>> 
>> It’s a non-normative suggestion
> 
> RFC 2119:
> 
> 4. SHOULD NOT   This phrase, or the phrase "NOT RECOMMENDED" mean that
>   there may exist valid reasons in particular circumstances when the
>   particular behavior is acceptable or even useful, but the full
>   implications should be understood and the case carefully weighed
>   before implementing any behavior described with this label.
> 
> Very much normative.  This is an RFC 2119 interoperability keyword because it creates an expectation in peers that they can mostly rely on this behavior, except for exceptional circumstances (which, by the way, should be spelled out with the SHOULD NOT).
> 
> I’m asking because we have a lot of experience with specifications that purport to use a base standard but instead attempt to create their own fork of that base standard by making mandates that meddle with the functioning of that base standard.  Not good.

You’re right. I should add, it’s not _supposed_ to be normative: it’s not our intention to modify how JSON works or impose restrictions on encoders. I don’t think we can do that even if we wanted to.

Austin.