Re: [Json] Proposed minimal change for strings

["Manger, James H" <[e-mail]>]

> <chair hats on>
> 
> Do either or both of these proposals work for people in the WG?
> 
> --Matt Miller and Paul Hoffman
> 
> The following are proposed minimal changes to make the JSON spec
> interoperable with respect to which unescaped code units are legal in
> strings.
> 
> Proposal 1 (allow all code units in their unescaped form):
> 
> In section 1 (Introduction):
>   Change the sentence about Unicode characters to:
>     A string is a sequence of zero or more Unicode code units
> [UNICODE].
> In section 2.2 (Strings):
>   Leave the production for "unescaped" as-is.
> In section 3 (Encoding):
>   Add "Some strings, notably those that have unescaped surrogate code
> units
>   (value 0xD800 to 0xDFFF), cannot be encoded in UTF-8."
> 
> Proposal 2 (prohibit unescaped surrogates):
> 
> In section 1 (Introduction):
>   A string is a sequence of zero or more Unicode scalar values
> [UNICODE].
> In section 2.2 (Strings):
>   Change the production for "unescaped" to be:
>     unescaped = %x20-21 / %x23-5B / %x5D-D7FF / %xE000-10FFFF


Yes, proposal 2 works for me.

--
James Manger