Re: [Json] "best practices" Vs. Profile for i-json

[Nico Williams <[e-mail]>]

On Mon, Aug 04, 2014 at 01:47:49PM -0400, John Cowan wrote:
> Nico Williams scripsit:
> 
> > Is a MUST really needed?  Suppose you have an encoder that produces
> > numbers (not irrationals) that require better-than-IEEE754 to represent
> > exactly.  A parser that can only handle IEEE754 should accept such
> > numbers, but with loss of precision/range -- exactly what we already
> > knew to expect from JSON as far as interoperability goes.
> 
> A fair point.  We can use the verbal formula employed by Unicode for
> normalization, something like this:
> 
>    A sending implementation [MUST NOT/SHOULD NOT] expect a receiving
>    implementation to distinguish between two numeric literals whose
>    decimal values round to the same IEEE754 double-precision value
>    (using standard round-to-nearest, ties-to-even rounding).
> 
> How's that?

Perfect.  Make that a MUST NOT.  Do we need a requirement/recommendation
that parsers implement at least IEEE754?

Nico
--