IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Tue, 08 October 2013 19:37 UTC

Return-Path: <cabo@tzi.org>
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 7634E21F9343 for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 12:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.159
X-Spam-Level:
X-Spam-Status: No, score=-106.159 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 4SXS2anHaXx9 for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 12:37:25 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF7721F9AC4 for <json@ietf.org>; Tue, 8 Oct 2013 12:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r98JbF6q015999; Tue, 8 Oct 2013 21:37:15 +0200 (CEST)
Received: from [192.168.217.105] (p5489368E.dip0.t-ipconnect.de [84.137.54.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id D21A3B5F; Tue, 8 Oct 2013 21:37:13 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <52544E3C.7000907@gmail.com>
Date: Tue, 08 Oct 2013 21:37:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC79C919-F229-4467-8781-4B1E1AABD1AC@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>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
X-Mailer: Apple Mail (2.1510)
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 19:37:34 -0000

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 :-)

v2.30.2 | Report a Bug | By Email | System Status