Re: [Json] FYI ECMA, W3C, IETF coordination on JSON

"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Tue, 08 October 2013 20:01 UTC

Return-Path: <pfpschneider@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E291711E8101 for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 13:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.852
X-Spam-Level:
X-Spam-Status: No, score=-2.852 tagged_above=-999 required=5 tests=[AWL=-0.253, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fG99WzznuZVJ for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 13:01:52 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B196911E80F5 for <json@ietf.org>; Tue, 8 Oct 2013 13:01:51 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id w5so780677qac.8 for <json@ietf.org>; Tue, 08 Oct 2013 13:01:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=No6yzEQ9Od7Vw0iRHxq2Jt2KTx+YNiEdSNvEHv5wiOs=; b=Aacuy5a225rdtS1sS38arahqYjkZ+9n2lYSpcl+GpFP0jl+upkfNLqRO5Gp48ms0lM GYJVBgq6T3OKQDsRUh1C+21hRCeoVYiF97TSsaDDkSXBwRvAs0CXeecDwjW3VBRKV46B iWvqUTT9k8Lg4THKSEKZcRLlWq4OQ7zGpr6MITh9niqXtfGaEa55cN93rkEIXE3Y1Lxu HQITGxtsi/5jUIQXmwxWaM5I9aF1WW+3qi9ATm4bJVHNZC6oLEwrwEuzcMoMnwTrqmB1 Q8AhAcXmnW4xkXlPI89MuyMqMct23Um2r0sZeHW/gGQjQwO9Ru2EY48pZ5J30J0D5VwE uVjQ==
X-Received: by 10.224.171.67 with SMTP id g3mr6334452qaz.13.1381262511184; Tue, 08 Oct 2013 13:01:51 -0700 (PDT)
Received: from [192.168.1.104] (out-on-245.wireless.telus.com. [207.219.69.245]) by mx.google.com with ESMTPSA id h2sm67798626qev.0.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 08 Oct 2013 13:01:50 -0700 (PDT)
Message-ID: <525464AA.8000608@gmail.com>
Date: Tue, 08 Oct 2013 13:01:46 -0700
From: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130805 Thunderbird/17.0.8
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <C68CB012D9182D408CED7B884F441D4D3482260661@nambxv01a.corp.adobe.com> <CAHBU6ivjOHyfMeSNPK3+A_4+VVsyH5Y9XDj77J01OZCjdB6wmA@mail.gmail.com> <525429ED.5000705@gmail.com> <04FC3123-33A4-40DA-AD5D-DA543435DE56@wirfs-brock.com> <20131008164219.GA16081@mercury.ccil.org> <52544E3C.7000907@gmail.com> <EC79C919-F229-4467-8781-4B1E1AABD1AC@tzi.org>
In-Reply-To: <EC79C919-F229-4467-8781-4B1E1AABD1AC@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] FYI ECMA, W3C, IETF coordination on JSON
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2013 20:01:53 -0000

I think that everyone agrees that JSON text is a sequence of Unicode code 
points, but that's not the issue.  The issue is whether JSON strings represent 
sequences of Unicode characters or something else.

The JSON syntax in ECMA-404 appears to allow "\uDEAD" as a string. What 
Unicode character does this represent?

A similar problem infects JSON numbers.  There is no debate as to the syntax 
of JSON numbers.   However, there is very little guidance on what a JSON 
number represents.  Is -0 the same as 0?  Is -0.0 the same as 0?  Is 
1.10000000000000000000000000000000000000000000001 the same as 1.1?  Is 1E1 the 
same as 10?

peter

On 10/08/2013 12:37 PM, Carsten Bormann wrote:
> On Oct 8, 2013, at 20:26, "Peter F. Patel-Schneider" <pfpschneider@gmail.com> wrote:
>
>> The paragraph on strings, also below, ignores all the problems with escaped code units that do not represent a Unicode code point.
> Actually, no, this point is not ignored at all.
>
> It makes it very clear that JSON is composed of Unicode code points.
> UTF-16 only occurs once, where the twelve-character-escape for non-BMP code points is explained.
> So that may be one point where following ECMA-404*) might make the work of this WG simpler.
>
> Grüße, Carsten
>
> *) Great numbering :-)
> We should try to get RFC 7404 :-)
>