Re: [Json] Call for Consensus: Proposed Text for "8.1 Character Encoding"

[John Cowan <[e-mail]>]

On Mon, Mar 20, 2017 at 12:26 PM, Matthew A. Miller <
[e-mail]> wrote:

JSON text MUST be encoded in UTF-8, UTF-16, or UTF-32 Section 3 of
> [UNICODE].  The default encoding is UTF-8, and JSON texts that are
> encoded in UTF-8 are interoperable in the sense that they will be
> read successfully by the maximum number of implementations; there are
> many implementations that cannot successfully read texts in other
> encodings (such as UTF-16 and UTF-32).  Text encoded in character
> encodings other than UTF-8, UTF-16, or UTF-32 cannot be used with
> the media tye "application/json".
>
> Implementations MUST NOT add a byte order mark (U+FEFF) to the
> beginning of a JSON text.  In the interests of interoperability,
> implementations that parse JSON texts MAY ignore the presence of a
> byte order mark rather than treating it as an error.
>
> Recipients that wish to support Unicode encodings other than UTF-8
> can do this using a detection mechanism that is based on the fact
> that the first character will always have a Unicode code point less
> or equal than 127, thus the UTF-16/32 variants can be detected by
> inspecting the first octets for nulls.
>

Two minor corrections: for "media tye" read "media type", and for
"less than or equal to 127" read "greater than 0 and less than 128".

--
John Cowan          http://vrici.lojban.org/~cowan        [e-mail]
Fundamental thinking is ha-ard.  Let's go ideology-shopping.
                        --Philosopher Barbie