Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

[Pete Cordell <[e-mail]>]

Thanks Matt and all for your patience on this issue and going the extra 
mile (or 2 or 3).  Hopefully it'll save some confusion for readers in 
the future.

Cheers,

Pete.

On 16/08/2017 04:01, Matthew A. Miller wrote:
> Thanks you all.  We can take Pete Cordell's suggestions, with the
> reference corrected from [UNICODE] to [RFC3629]:
> 
> 
> """
> 8.1.  Character Encoding
> 
> JSON text exchanged between systems that are not part of a closed
> ecosystem MUST be encoded using UTF-8 [RFC3629].
> 
> 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 networked-transmitted 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.
> """
> 
> Unless there are strong objections, this is the text we'll submit to the
> editor.
> 
> 
> - m&m
> 
> Matthew A. Miller
> 
> On 17/08/14 10:56, Peter Saint-Andre - Filament wrote:
>> On 8/14/17 10:50 AM, Paul Hoffman wrote:
>>> On 14 Aug 2017, at 9:40, Matthew A. Miller wrote:
>>>
>>>> On 17/08/01 10:28, Pete Cordell wrote:
>>>>> On 01/08/2017 17:01, Peter Saint-Andre - Filament wrote:
>>>>>>
>>>>>> We're not writing a novel here. :-)
>>>>>
>>>>> I had been thinking that too.  I do like the direction of focussing the
>>>>> requirement on open systems communication though (not to be confused
>>>>> with systems built on open software!).  I think the following is pretty
>>>>> simple and side-steps issues about what is a network protocol, payload,
>>>>> serialization etc.:
>>>>>
>>>>> 8.1.  Character Encoding
>>>>>
>>>>>     JSON text exchanged between systems that are not part of a closed
>>>>>     ecosystem MUST be encoded using UTF-8.
>>>>>
>>>>>     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 networked-transmitted 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.
>>>>>
>>>>>
>>>>
>>>> Hello JSONbis Working Group,
>>>>
>>>> does anyone have comments on Pete Cordell's suggested text?
>>>
>>> The current wording works for me, and so does Pete's.
>>
>> What Pete suggested seems good enough.
>>
>> Peter
>>
> 
> 
> 
> 
> _______________________________________________
> json mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/json
>