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

[Pete Cordell <[e-mail]>]

Since nobody else seems to struggle with "over a network protocol", I'll 
withdraw this proposed wording change and support Matt's proposed wording.

Roll the presses!

Pete.
-- 
---------------------------------------------------------------------
Pete Cordell
Codalogic Ltd
C++ tools for C++ programmers, http://codalogic.com
Read & write XML in C++, http://www.xml2cpp.com
---------------------------------------------------------------------
On 18/07/2017 10:41, Pete Cordell wrote:
> On 18/07/2017 09:27, Matthew A. Miller wrote:
>> Hello all,
>>
>> I see consensus for the updated text below.  A note to the RFC editor is
>> added to ensure publication does not move forward until section 8.1 is
>> updated, and the change noted in the appendix.
>>
>> """
>> 8.1.  Character Encoding
>>
>> When transmitting over 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]).
> 
> I struggle here with "over a network protocol".  Perhaps we have a 
> different idea of what "over a network protocol" means, but these days 
> everything goes over a network protocol at some point in my mind.
> 
> Here's another stab at some wording in place of the first proposed 
> paragraph:
> 
>      When transmitted as part of an IETF defined protocol, JSON text
>      MUST be encoded in UTF-8 (Section 3 of [UNICODE]).
> 
>      Protocols defined outside the IETF are strongly encouraged to adopt
>      a similar "MUST be encoded in UTF-8" requirement, but mandating this
>      recommendation is beyond the scope of this specification.
> 
> Regards,
> 
> Pete Cordell
> Codalogic Ltd
> C++ tools for C++ programmers, http://codalogic.com
> Read & write XML in C++, http://www.xml2cpp.com
> 
> _______________________________________________
> json mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/json
>