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

[John Cowan <[e-mail]>]

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?

-- 
John Cowan          http://www.ccil.org/~cowan        [e-mail]
A few times, I did some exuberant stomping about, like a hippo auditioning
for Riverdance, though I stopped when I thought I heard something at
the far side of the room falling over in rhythm with my feet.  --Joseph Zitt