Where this might be important: governments and bureaucracies which have a fondness for formally specified standards. Now they can adopt JSON.
ECMA-404: The JSON Data Interchange Format [pdf]
11–20 of 199 posts
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#12Can anyone go into the detail of the impact ,if any, of this?
More of a formality than anything else. Since JSON was already defined by Javascript, formalizing it doesn't really engrave the standard, it just gives it the recognition that its not just some whacky thing created by Dave.
"Dave" being recognised as generic name for any developer.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#13Earlier quoted context omitted.
I'm guessing it may help bring JSON to use in the more restrictive companies that are scared of 'nonstandard' file formats. The kind that currently uses XML for everything.
the kind that correctly uses XML for everything.
Why do you believe that using XML is better than JSON in every case? Or am I misinterpreting your comment?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#14No thanks to Mr. Crawford for not fixing the \u2028-9 issue. JSON as defined is not a subset of javascript. It is a design mistake that was pointed out to him years ago, but he is too stubborn or arrogant to fix it.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#15Re: ECMA-404: The JSON Data Interchange Format [pdf]
#16Earlier quoted context omitted.
More of a formality than anything else. Since JSON was already defined by Javascript, formalizing it doesn't really engrave the standard, it just gives it the recognition that its not just some whacky thing created by Dave.
"Dave" being recognised as generic name for any developer.
Out of interest, does anyone know the most common first name for a developer?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#17Great stuff. On a side note, this ECMA website is fantastic. I've never seen it before, but it's really quite interesting to change the URL to random numbers to find out what other standards ECMA has done.
For instance, there's a standard for measuring computer equipment in controlled rooms: http://www.ecma-international.org/publications/files/ECMA-ST...
And here's an important one, DVD-RAM discs: http://www.ecma-international.org/publications/files/ECMA-ST... and their cases: http://www.ecma-international.org/publications/files/ECMA-ST...
Plus, NFC: http://www.ecma-international.org/publications/files/ECMA-ST...
It's all new to me!
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#18My faint hopes for trailing comma support are now crushed.
I'm actually very confused by it - I thought the specification for ECMAScript 3 already specified trailing comma support for JSON. Will need to look it up...
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#19Re: ECMA-404: The JSON Data Interchange Format [pdf]
#20No thanks to Mr. Crawford for not fixing the \u2028-9 issue. JSON as defined is not a subset of javascript. It is a design mistake that was pointed out to him years ago, but he is too stubborn or arrogant to fix it.
Why do you ask him without the stubborn and arrogant comment on G+ and about trailing commas? Or is indirect better?