IETF Logo Mail Archive

Re: [Json] On characters and code points

Bjoern Hoehrmann <derhoermi@gmx.net> Fri, 07 June 2013 18:40 UTC

Return-Path: <derhoermi@gmx.net>
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 AD84B21F9948 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 11:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_14=0.6]
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 PBgZgxn2fsJK for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 11:40:51 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3BF21F8D0D for <json@ietf.org>; Fri, 7 Jun 2013 11:40:51 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0LfDpm-1U0wKA1irw-00on2a for <json@ietf.org>; Fri, 07 Jun 2013 20:40:50 +0200
Received: (qmail invoked by alias); 07 Jun 2013 18:40:50 -0000
Received: from p5B2339AC.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [91.35.57.172] by mail.gmx.net (mp020) with SMTP; 07 Jun 2013 20:40:50 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+mbUEBOQCmXU+1aH5YS39VuZ0wRcx6KVTtxPdT67 oLwJzjB4EehZzl
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stephen Dolan <stephen.dolan@cl.cam.ac.uk>
Date: Fri, 07 Jun 2013 20:40:51 +0200
Message-ID: <o4a4r8ldc0sp12k310b9gv3486ht4sis2l@hive.bjoern.hoehrmann.de>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC2E7E1@xmb-rcd-x10.cisco.com> <51B06F38.8050707@crockford.com> <CAHBU6iuFBuW-RfgBLQF5q4BnUOzs088QXW3uOQG1OjBFjZttkw@mail.gmail.com> <51B1B4E7.8090101@it.aoyama.ac.jp> <9ld3r8pc0tufif18dohb2fmi0ijna1vs4n@hive.bjoern.hoehrmann.de> <56A163E9-E7CD-46B3-9984-8F009EBFF500@vpnc.org> <CA+mHimO-bUvodjgM89Nskg+tqWrsTAfL8EWRx++fd16t1hFR_g@mail.gmail.com>
In-Reply-To: <CA+mHimO-bUvodjgM89Nskg+tqWrsTAfL8EWRx++fd16t1hFR_g@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] On characters and code points
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: Fri, 07 Jun 2013 18:40:55 -0000

* Stephen Dolan wrote:
>(3) includes such beasts as U+FFFE (which you can only get by reading
>a UTF16 byte order mark with the wrong byte order). The set (1)
>increases with every Unicode revision to include characters from (2),
>but (3) is stable (see
>http://unicode.org/policies/stability_policy.html).

>I think JSON should allow characters from (1) and (2) to avoid being
>dependent on a specific Unicode revision. I do not think (3) should be
>allowed - this would cause problems with many existing parsers which
>represent JSON strings using another system's native unicode
>representation.

Please see <http://www.unicode.org/versions/corrigendum9.html>.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

v2.23.0 | Report a Bug | By Email