- From: John Cowan <cowan@mercury.ccil.org>
- Date: Fri, 22 Nov 2013 13:57:59 -0500
- To: "Matt Miller (mamille2)" <mamille2@cisco.com>
- Cc: JSON WG <json@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
Matt Miller (mamille2) scripsit: > There does seem to be rough consensus that using an encoding other > than UTF-8 can have interoperability issues. I agree. > The also seems to be rough consensus that the current text and table > in section 8.1 for detecting the encoding will be inaccurate (and > potentially harmful). If it is inaccurate, it should be fixed, but as it is a statement of fact and not normative, I can see no grounds for removing it altogether. > That appears to mean the approach with the most consensus is to remove > the encoding detection entirely, leaving only: > > JSON text SHALL be encoded in Unicode. The default encoding is > UTF-8. I do not believe this is strong enough. I think an interoperability problems warning similar to those we already have would be better. Proposed text: The use of other encodings is known to cause interoperability problems. -- One Word to write them all, John Cowan <cowan@ccil.org> One Access to find them, http://www.ccil.org/~cowan One Excel to count them all, And thus to Windows bind them. --Mike Champion
Received on Friday, 22 November 2013 18:58:23 UTC