Re: [Json] Proposed minimal change for strings

John Cowan <cowan@mercury.ccil.org> Wed, 03 July 2013 04:41 UTC

Date: Wed, 03 Jul 2013 00:41:50 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20130703044150.GW31347@mercury.ccil.org>
References: <9BACB3F2-F9BF-40C7-B4BA-C0C2F33E4278@vpnc.org> <20130703012614.GL31347@mercury.ccil.org> <2CD8DA4E-8E03-4B4A-AC99-166B7094DCF9@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2CD8DA4E-8E03-4B4A-AC99-166B7094DCF9@vpnc.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: "json@ietf.org WG" <json@ietf.org>
Subject: Re: [Json] Proposed minimal change for strings
Precedence: list

Paul Hoffman scripsit:

> It does not appear that the Unicode Standard requires mentioning its
> size, at least in the definition of "code unit" in D77.

That is so.  But are we to understand, then, that a JSON string is a
sequence of code units of some unspecified size?  For example,
is the 8-bit code unit sequence <FF, FE, FF, FE> a JSON string?
How about the 32-bit code unit sequence <ABCDABCD, 10101010>?
Might 3-bit or 17-bit or 99-bit code unit sequences be allowed also?
Surely not.

> John is correct. After further review, we should have worded the above
> as "...cannot be encoded in any Unicode encoding form".

As noted, that should have been "unpaired unescaped surrogate code units".

-- 
John Cowan  cowan@ccil.org  http://ccil.org/~cowan
If I have seen farther than others, it is because I was standing on
the shoulders of giants.
        --Isaac Newton

Re: [Json] Proposed minimal change for strings John Cowan
[Json] Proposed minimal change for strings Paul Hoffman
Re: [Json] Proposed minimal change for strings Paul Hoffman
Re: [Json] Proposed minimal change for strings Nico Williams
Re: [Json] Proposed minimal change for strings Manger, James H
Re: [Json] Proposed minimal change for strings John Cowan
Re: [Json] Proposed minimal change for strings John Cowan
Re: [Json] Proposed minimal change for strings Paul Hoffman
Re: [Json] Proposed minimal change for strings Paul Hoffman
Re: [Json] Proposed minimal change for strings John Cowan
Re: [Json] Proposed minimal change for strings Nico Williams
Re: [Json] Proposed minimal change for strings Norbert Lindenberg
Re: [Json] Proposed minimal change for strings Joe Hildebrand (jhildebr)
Re: [Json] Proposed minimal change for strings Jorge
Re: [Json] Proposed minimal change for strings Stephen Dolan
Re: [Json] Proposed minimal change for strings Bjoern Hoehrmann
Re: [Json] Proposed minimal change for strings Jorge
Re: [Json] Proposed minimal change for strings Manger, James H
Re: [Json] Proposed minimal change for strings Bjoern Hoehrmann