Subject: Re: [Json] Proposal for strings/Unicode text
From: "Joe Hildebrand (jhildebr)" <[email-masked]>
To: Paul Hoffman <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Date: Mon, 17 Jun 2013 17:30:13 +0000
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>

On 6/17/13 11:27 AM, "Paul Hoffman" <[email-masked]> wrote:

>On Jun 17, 2013, at 10:21 AM, Joe Hildebrand (jhildebr)
><[email-masked]> wrote:
>
>> On 6/16/13 11:02 PM, "Manger, James H" <[email-masked]>
>> wrote:
>> 
>>> Fixing typos and tweaking the comment:
>>> 
>>> unescaped = %x20-21 / %x23-5B / %x5D-D7FF / %xE000-10FFFF
>>>   ; any Unicode scalar value, except those that must be escaped
>>>   ; (control characters, quotation mark, and reverse solidus)
>> 
>> After discussion, this?
>> 
>> unescaped = %x20-21 / %x23-5B / %x5D-D7FF / %xE000-10FFFF
>> ; any Unicode scalar value, except those that must be escaped
>> ; (C0 control characters,
>> ;  "QUOTATION MARK" [U+0022], and
>> ;  "REVERSE SOLIDUS" [U+005C])
>> 
>> The caps and codepoint references make it clear we're only talking about
>> those precise codepoints.
>> 
>> Others may argue that non-C0 control characters should be prohibited,
>>but
>> that's a separate backward-compatibility argument from this starting
>>point.
>
>What value is that comment? Doesn't it invite misinterpretation of the
>ABNF, which is exact?

We have comments after most everything else.  Some of the readers of this
doc aren't going to be savvy enough to be able to read the ABNF easily
without the comment.

However, I'd be fine with removing it.

-- 
Joe Hildebrand