http://tools.ietf.org/html/draft-staykov-hu-json-canonical-form-00
The I-D doesn't mention the total mess regarding character escaping out in the wild which seems to be based on "this feels right" and "IE 7 doesn't like certain characters": http://www.ietf.org/mail-archive/web/jose/current/msg03377.html http://stackoverflow.com/questions/6011012/making-json-not-escape-forward-slashes IMO it is better addressing canonicalization directly in JSON encoders and decoders by the use of a copy of the textual data for property values instead of relying on complex, slow and potentially brittle post-processing like most XML-based systems do. To "straighten-up" the representation of floating-point numbers like described in the I-D would be awesome, but is in my take on the matter not an absolute necessity. FWIW, V0.51 is almost there thanks to very useful feedback: https://openkeystore.googlecode.com/svn/resources/trunk/docs/JSON-Clear-Text-Signature-Scheme.pdf Anders _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
