IETF Logo Mail Archive

Re: [Json] Proposed change: update the Unicode version

John Cowan <cowan@mercury.ccil.org> Wed, 05 June 2013 16:55 UTC

Return-Path: <cowan@ccil.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 C52EA21F9BD3 for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 09:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WkFiCE2P1vW1 for <json@ietfa.amsl.com>; Wed, 5 Jun 2013 09:55:36 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 4E58421F9AFE for <json@ietf.org>; Wed, 5 Jun 2013 09:55:36 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UkGzm-0008JJ-5o; Wed, 05 Jun 2013 12:55:34 -0400
Date: Wed, 05 Jun 2013 12:55:34 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <20130605165534.GI3680@mercury.ccil.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC286AF@xmb-rcd-x10.cisco.com> <51AE6E95.3050007@stpeter.im> <CAHBU6iu083Q+tFcBt=CshS68DWFZ-8JH3ahquXKGW1t1GgCyjg@mail.gmail.com> <51AE736D.7030209@stpeter.im> <BF7E36B9C495A6468E8EC573603ED9411527BCD5@xmb-aln-x11.cisco.com> <5DC8FE77-10A8-4835-8415-ACC3FC323663@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5DC8FE77-10A8-4835-8415-ACC3FC323663@tzi.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
Cc: json@ietf.org, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] Proposed change: update the Unicode version
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: Wed, 05 Jun 2013 16:55:40 -0000

Carsten Bormann scripsit:

> It would help me if you could briefly explain what the reference to
> 2.7 specifically adds here.  (To me that is a bit confusing, as 2.7
> is about internal programming language representation, not about
> representation for interchange.  But maybe I just don't understand.)

+1

I also do not understand why JSON strings can't contain characters that
are unassigned as yet.  Checking this restriction is onerous if you don't
have 6.2 or later Unicode tables, or even if you do.

-- 
John Cowan  cowan@ccil.org  http://ccil.org/~cowan
If I have not seen as far as others, it is because giants were standing
on my shoulders.
        --Hal Abelson

v2.23.0 | Report a Bug | By Email