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

[Julian Reschke <[e-mail]>]

On 2017-03-20 17:26, Matthew A. Miller wrote:
> Thank you for the suggested changes, Julian.  To consolidate the
> changes, I believe the following is your suggested text for all of
> Section 8.1:
>
> """
> 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

Put "Section 3 of Unicode" into parentheses.

> 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

Replace "in other encodings (such as UTF-16 and UTF-32)" by just "in 
other encodings". The proposed text implies that there encodings other 
than UTF-16 or UTF-32 which could be allowed.

> 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.
> """
>
> Does the working group object to this change?

+1, with the comments above.

Best regards, Julian