Re: [Json] Complete section 3 proposal

[Nico Williams <[e-mail]>]

On Tue, Jun 18, 2013 at 3:40 PM, Joe Hildebrand (jhildebr)
<[e-mail]> wrote:
> Combining the threads
>
> """
> Without an external mechanism that specifies encoding, when serialized to
> an octet stream, JSON text SHALL be encoded in one of the following
> Unicode encoding schemes: UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, or
> UTF-32LE.  The default and RECOMMENDED encoding is UTF-8.

Note that if a JSON string in JSON data contains unescaped naked
surrogates then the encoding of that data will not be valid UTF-8,
UTF-16, nor, for that matter, CESU-8.  And some implementations
probably produce CESU-8-encoded data.  I'm not sure whether that's
worth stating here or elsewhere, but the fact that there's
not-quite-UTF-8 JSON out there means this SHALL is either
interop-breaking or the matter must be mentioned nearby.

With this caveat, +1.

>     Note: the MIME type registered in [Section 6] does not specify such an
> external mechanism, so when used in a MIME context, one of the above
> encoding schemes MUST be used.

Agreed.

Nico
--