IETF Logo Mail Archive

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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 04 June 2013 19:56 UTC

Return-Path: <jhildebr@cisco.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 31A7721F9408 for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 12:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 OPFgel1EeV-m for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 12:56:47 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBBA21F9590 for <json@ietf.org>; Tue, 4 Jun 2013 11:56:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1448; q=dns/txt; s=iport; t=1370372212; x=1371581812; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=/2oy+kBx1lE1jLr8AiOJDZ93iwgFvJcTMm7xIWlTD3o=; b=G8zvtbX2NX7f7uISExokPvixwR4F6MS/8cCyweygOTyv9bOZw6/RLPVx Z6+lqIIPVBF9GbX2uwK/ppCJz5TFBjHtoCare2NjnARBhhwDh0zuNY26u 8CfEZvIAqemFXeVZtPHpik/JLgqpWOCkpjz/rnsiwNMAdz3dL1VtfquLB Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAMk3rlGtJXG//2dsb2JhbABagwkwvyl7FnSCIwEBAQQ6PxIBCBgKFEIlAgQBDQUIAYgEDL1pjVeBHDEHgnphA6h/gw+CJw
X-IronPort-AV: E=Sophos;i="4.87,801,1363132800"; d="scan'208";a="218743691"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-5.cisco.com with ESMTP; 04 Jun 2013 18:56:51 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r54IupNJ025873 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Jun 2013 18:56:51 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Tue, 4 Jun 2013 13:56:51 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Paul Hoffman <paul.hoffman@vpnc.org>
Thread-Topic: [Json] Proposed change: update the Unicode version
Thread-Index: AQHOYUwcF9XONJEgqUaP+nfdT45kJZkmK8CA//+rbYA=
Date: Tue, 04 Jun 2013 18:56:50 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70FC27CC9@xmb-rcd-x10.cisco.com>
In-Reply-To: <51AE2B03.5070100@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.21.74.153]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0406A3772592BB4E9FE2615F130598CB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "json@ietf.org" <json@ietf.org>
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: Tue, 04 Jun 2013 19:56:52 -0000

On 6/4/13 11:59 AM, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:

>On 6/4/13 10:58 AM, Paul Hoffman wrote:
>> <no hat>
>> 
>> The current spec refers to the then-current Unicode spec:
>> 
>>    [UNICODE] The Unicode Consortium, "The Unicode Standard Version 4.0",
>>              2003, <http://www.unicode.org/versions/Unicode4.1.0/>.
>> 
>> 
>> I propose to update the reference to:
>> 
>>    [UNICODE] The Unicode Consortium, "The Unicode Standard Version 6.2",
>>              2012, <http://www.unicode.org/versions/Unicode6.2.0/>.
>
>There are other i18n issues that we might want to clarify, but updating
>the Unicode reference seems uncontroversial.

Suggested change to section 1:

WAS:

A string is a sequence of zero or more Unicode characters [UNICODE].


SUGGESTED:

A string is a sequence of encoded Unicode codepoints defined in
[UNICODE6.2] or later versions of the Unicode specification.

Goals:

- we're defining a protocol, not an infoset
- make it clear that codepoints that become valid in the future are valid
JSON

Section 3 also needs to be tweaked:

WAS:

JSON text SHALL be encoded in Unicode.  The default encoding is
   UTF-8.


SUGGESTED:

JSON text SHALL be transmitted as encoded Unicode codepoints.  The default
encoding is
UTF-8.

Note: the rest of section 3 may need to change if we allow strings as root
JSON objects later.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email