IETF Logo Mail Archive

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

"Peter F. Patel-Schneider" <pfpschneider@gmail.com> Tue, 08 October 2013 18:58 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 C6FD321F842B for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 11:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.792
X-Spam-Level:
X-Spam-Status: No, score=-3.792 tagged_above=-999 required=5 tests=[AWL=0.807, BAYES_00=-2.599, GB_I_LETTER=-2]
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 2LfFcodqdpWM for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 11:58:42 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0193721F841D for <json@ietf.org>; Tue, 8 Oct 2013 11:58:39 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id ne12so7003947qeb.24 for <json@ietf.org>; Tue, 08 Oct 2013 11:58:37 -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=sQrJm6zPMLx5epWk4FESGKL6bz0Uqz23/Bv+nbwrrHw=; b=dXOn2o1bV1yAzAboygyenuXsZOZUWLq3cd1TOq4cnr/t4kSp9QDWSRfP0MZBGPQDhX UdBXAuHQvm/tChI6YC0mdhoGT0kvmvJyIELgGEvpZhF6PP/jMo2s/M3UbfYSOzVP7kJl /h+OhynEVHjf0BjxQMZ0O9mxs5IwWwwMFbbp4ZPO+0H44MmQG7rxtWpl0Par+g3KOGMw vqrcjIQ1LUezbpse37GP4OMuuWbch50eNQYqf1MaaMhOyT9oqFw18e3h6S7xUrcUKIOb catud0jzCLMatyjnQaz4hM7a7EupTzIUk7NzTfcaPRIeFIbGJLqICec/9xKuxyxyGoQn E8Mw==
X-Received: by 10.49.116.19 with SMTP id js19mr4481374qeb.34.1381258717821; Tue, 08 Oct 2013 11:58:37 -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 x1sm76925007qai.6.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 08 Oct 2013 11:58:37 -0700 (PDT)
Message-ID: <525455D4.8090105@gmail.com>
Date: Tue, 08 Oct 2013 11:58:28 -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: Tim Bray <tbray@textuality.com>
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> <CAHBU6it5Gw-JDWZk1AdqoCe_i-jqwUu3eMLrbZZe1VC3uVFkuw@mail.gmail.com>
In-Reply-To: <CAHBU6it5Gw-JDWZk1AdqoCe_i-jqwUu3eMLrbZZe1VC3uVFkuw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: Allen Wirfs-Brock <allen@wirfs-brock.com>, JSON WG <json@ietf.org>, John Cowan <cowan@mercury.ccil.org>, "www-tag@w3.org" <www-tag@w3.org>, Larry Masinter <masinter@adobe.com>
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 18:59:19 -0000

Yes indeed.  Yes indeed.   The double quote may not appear within quotation 
marks, by a two-to-one vote.

peter

On 10/08/2013 11:32 AM, Tim Bray wrote:
> On the other hand, the opening paragraph of section 9 makes sure that you’re 
> really clear about which characters may and may not be placed between 
> quotation marks.
>
>
> On Tue, Oct 8, 2013 at 11:26 AM, Peter F. Patel-Schneider 
> <pfpschneider@gmail.com <mailto:pfpschneider@gmail.com>> wrote:
>
>     The paragraph on numbers, see below, seems rather dangerous, as well as
>     being incorrect.  The paragraph on strings, also below, ignores all the
>     problems with escaped code units that do not represent a Unicode code point.
>
>     peter
>
>
>     On 10/08/2013 09:42 AM, John Cowan wrote:
>
>         Allen Wirfs-Brock scripsit:
>
>             The draft was approved by a letter ballot of the Ecma General
>             Assembly.  It is now available as Ecma-404:
>
>         Almost all of it is derived directly from the RFC, with some editorial
>         cleanup.  The Introduction, however, is new.  I reproduce it here in
>         case
>         the Editor wishes to mine it for anything:
>         [...]
>
>
>              JSON is agnostic about numbers. In any programming language,
>              there can be a variety of number types of various capacities
>              and complements, fixed or floating, binary or decimal. That
>              can make interchange between different programming languages
>              difficult. JSON instead offers only the representation of numbers
>              that humans use: a sequence of digits. All programming languages
>              know how to make sense of digit sequences even if they disagree
>              on internal representations. That is enough to allow interchange.
>
>              JSON text is a sequence of Unicode code points. JSON also depends
>              on Unicode in the hex numbers used in the \u escapement [sic]
>              notation.
>         [...]
>
>
>

v2.23.0 | Report a Bug | By Email