On 17/03/08 09:54, Julian Reschke wrote: > On 2017-02-21 23:01, Barry Leiba wrote: >> ... > > Looking at > <https://tools.ietf.org/rfcdiff?url2=draft-ietf-jsonbis-rfc7159bis-03.txt&url1=rfc7159>, > I see: > > "Section 15.2 has been updated to remove ECMA 404, update the version of > ECMA-262, and refresh the errata list." > > However, the ECMA-262 reference changes from > >> [ECMA-262] Ecma International, "ECMAScript Language Specification >> Edition 5.1", Standard ECMA-262, June 2011, >> <http://www.ecma-international.org/publications/standards/ >> Ecma-262.htm>. > > to > >> [ECMA-262] >> Ecma International, "ECMAScript Language Specification, >> Third Edition", Standard ECMA-262, December 1999, >> <http://www.ecma-international.org/publications/files/ >> ECMA-ST-ARCH/ >> ECMA-262,%203rd%20edition,%20December%201999.pdf>. > > > ...which looks like a downgrade to me. > > I believe this should be: > >> [ECMA-262] Ecma International, "ECMAScript(R) 2016 Language >> Specification, 7th Edition", ECMA 262, June 2016, >> <https://www.ecma-international.org/ecma-262/7.0/>. > > Best regards, Julian Hello Julian, the rationale for referencing third edition specifically is to give evidence of the JSON's specification history. Maybe the word "update" is debatable here, but I think the reference itself is valid. - m&m Matthew A. Miller
Attachment:
signature.asc
Description: OpenPGP digital signature