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

[Pete Cordell <[e-mail]>]

On 10/05/2017 18:13, Matthew A. Miller wrote:
> Assuming the Working Group finds that scope acceptable and finds UTF-8
> only acceptable, here is a starting proposal for text:
>
> """
> 8.1.  Character Encoding
>
> When transmitting over a network protocol, JSON text MUST be
> encoded in UTF-8 (Section 3 of [UNICODE]).
>
> Previous specifications of JSON have not required the use of UTF-8
> when transmitting JSON text. However, the vast majority of
> JSON-based software implementations have chosen to use the UTF-8
> encoding, to the extent that it is the only encoding that achieves
> interoperability.
>
> 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.
> """
>
> If you find this acceptable, please indicate that.  Otherwise, please
> provide suggested changes.


A strong +1 to the spirit of the proposal.

I realise that the term "network protocol" is necessarily vague, but I 
wonder if it might be possible to avoid some confusion with the likes of 
NetBEUI (if that's still around) with a phrasing something like:

     When transmitted as the syntax of a network protocol, or as a
     payload of a network protocol intended to be interpreted as part of
     a protocol, JSON text MUST be encoded in UTF-8 (Section 3 of
     [UNICODE]).

Thanks,

Pete