Can anyone go into the detail of the impact ,if any, of this?
I'd be interested to know if this has any impact on the "don't be evil" clause in the JSON license.
That's just a license for software available on json.org, so no impact at all.
ECMA-404: The JSON Data Interchange Format [pdf]
21–30 of 199 posts
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#22404 Standard Not Found
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#23Does this mean comments will be added to the spec?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#24Does this mean comments will be added to the spec?
Nope, sorry.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#25If he want to be formalis JSON e he should use a standard license for the software.
I accept "The Software shall be used for Good, not Evil." is amusing and "good" but must cause difficulties for people wanting to package with other software under standard licenses.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#26My 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...
ECMAScript 3 did not allow trailing commas in object literals, its section 11.1.5 is:
ObjectLiteral :
{ }
{ PropertyNameAndValueList }
ObjectLiteral :
{ }
{ PropertyNameAndValueList }
{ PropertyNameAndValueList , }
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#27What's so awesome about JSON? Its standard documentation is 5 pages. So simple, so awesome.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#28If he want to be formalis JSON e he should use a standard license for the software. I accept "The Software shall be used for Good, not Evil." is amusing and "good" but must cause difficulties for people wanting to package with other software under standard licenses.
That is the license on just one of dozens, perhaps hundreds of JSON implementations. It has nothing at all to do with standardization of the format.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#29No 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?
Probably because he's very aware of it already and people here may not be.
(Meta: Why have any conversation on an HN back-channel when there are comments open at the source?)