On 2014-01-07 10:12, Carsten Bormann wrote: > On 07 Jan 2014, at 09:33, Anders Rundgren <[email protected]> > wrote: > >> This spec. describes an ultra-simple JSON canonicalization scheme: >> https://openkeystore.googlecode.com/svn/resources/trunk/docs/jcs.html > > That’s not JSON. > ("Parsing Restrictions:” "• The original property order must be preserved.”)
It is a correct but [somewhat] restricted JSON syntax. This restriction is probably a minor problem (since it should be easy to support), while the "cheap trick" canonicalization method preserving non-normalized numbers like 4.50 was the thing that _required_ an upgraded parser. But as the latter turned out to be quite simple, I (FWIW) didn't see that as a showstopper. It was [almost] fun to write :-) Regards, Anders > > (Members of the JSON WG will be painfully aware that, yes, this can be done > in > currently deployed in-Browser JavaScript implementations if certain key values > are not being used, but it cannot be done in JSON in general.) > > Grüße, Carsten > _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
