JSON is now a formal international data processing standard: ECMA-404.
317 plus ones
Shared publicly•View activity
View 14 previous comments
- No, the part that was formalized is pretty much "as it is"... The IETF discussions are a separate matter and may be worrisome if they break things in the name of greater interop.Oct 11, 2013
- Finally! We have waited this day for a very long time!Oct 11, 2013
- , was the definition of a valid "JSON text" deliberately changed from RFC-4627? ECMA-404 seems to now allow non-array non-object top-level values, which used to be prohibited.
(I've posed this question in general at http://stackoverflow.com/q/19569221/1114, but I haven't got an answer yet.)Oct 24, 2013
- JSON is just a grammar, and the grammar includes numbers and strings. Uses of JSON must necessarily be more restrictive. RFC-4627 is one possible use, and was never intended to be the standard for JSON itself.Oct 24, 2013
- congrats, you did it :)Oct 30, 2013
Add a comment...