Re: [Json] JSON Schema Language

[Carsten Bormann <[e-mail]>]

On May 5, 2019, at 08:16, Austin Wright <[e-mail]> wrote:
> 
> If the encoder knows the value will always be an integer, why add a fractional part?

(1) The encoder may not be privy to that information (it is a generic encoder).
(2) The encoder may try to fulfill a conflicting set of rules, set up by a different fork of the base standard, e.g.:

If the data comes as a floating point typed value, encode it as NR2 or NR3.
If the data comes as an integer typed value, encode it as NR1.
(This rule set is intended to preserve the distinction in implementation types, which may be important to some other application.
It is common in programming language notation, and since JSON was also derived from a programming language notation [albeit one without this rule set!], it is a common mistake to assume that this rule set can be applied to JSON without cost or damage.)

These conflicting sets of rules are exactly why it's so detrimental to fork a base standard with your own set of rules.

Grüße, Carsten