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

[Tim Bray <[e-mail]>]

​I’m meh on the network-or-not language.

I have one source of heartburn.  The stated purpose of 7159bis is to
achieve harmony with ECMA 404.  That document does *not* constrain JSON
encoding.  I’m fine  with saying that JSON has to be UTF-8, but I think we
should consult with ECMA and see if the goal of spec harmonization is still
possible if we make the UTF-8 restriction.

I’m much more positive about the UTF-8 restriction than the ECMA harmony
(which I think is ridiculous political bushwah) but at least the WG should
know the context before making a call.​

On Wed, May 10, 2017 at 1:30 PM, Pete Cordell <[e-mail]>
wrote:

> 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
>
>
> _______________________________________________
> json mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/json
>



-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)