- From: Philippe Le Hegaret <plh@w3.org>
- Date: Tue, 26 Nov 2013 17:31:33 -0500
- To: Mark Nottingham <mnot@mnot.net>, paul.hoffman@vpnc.org, mamille2@cisco.com, json@ietf.org
- Cc: public-ietf-w3c <public-ietf-w3c@w3.org>, Wendy Seltzer <wseltzer@w3.org>, Daniel Appelquist <daniel.appelquist@telefonica.com>, Peter Linss <peter.linss@hp.com>, Yves Lafon <ylafon@w3.org>, Tim Berners-Lee <timbl@w3.org>
Dear All, The W3C Technical Architecture Group has a concern regarding the ongoing coordination of the industry standardization work on JSON. JSON is a key integration technology for Web applications and a key data interchange format for the Web. The current state of affairs, where there are now two different JSON specifications which may be normatively referenced, one developed in ECMA as ECMA-404 and one developed in IETF as RFC 4627 and in last call as RFC 4627bis is not ideal and could lead to confusion in the industry. Because the two specs vary slightly, we believe this could lead to interoperability issues. For example, today there are JSON parsers (conforming to ECMA-404) that can parse "42" (a JSON document consisting of a single integer). There are also parsers (conforming to RFC 4627/draft-ietf-json-rfc4627bis-07) that cannot parse "42" today, but they can be meaningfully upgraded to do so too. This would not break applications using those parsers, unless they depend on parsing "42" as an error, which is a far more unlikely scenario than parsing it as 42 given precedence. Regardless of the historical reasons for the current situation, the W3C TAG believes that having one definition of JSON would be beneficial for the Web and for the wider community of JSON implementors and JSON consuming and producing applications. We suggest that the IETF JSON working group should re-enter discussions with ECMA TC39 in order to facilitate aligning RFC 4627bis with the current ECMA-404 specification. Thank you, Philippe Le Hegaret, IETF co-team contact for the W3C
Received on Tuesday, 26 November 2013 22:31:37 UTC