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

[Joe Hildebrand <[e-mail]>]

> On May 10, 2017, at 11:13 AM, Matthew A. Miller <[e-mail]> wrote:
> 
> """
> 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.  

Suggestion: change "JSON text" here to "network-transmitted JSON text"
Rationale: it's not clear that this restriction applies to the JSON described up 2 paragraphs.

> 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.

Other than my nit, +1

— 
Joe Hildebrand