IETF Logo Mail Archive

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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 04 June 2013 22:45 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 D46E821F994A for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 15:45:35 -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 vZkjvthnlJjb for <json@ietfa.amsl.com>; Tue, 4 Jun 2013 15:45:30 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 4897421F998D for <json@ietf.org>; Tue, 4 Jun 2013 15:45:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=582; q=dns/txt; s=iport; t=1370385930; x=1371595530; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=P+gM2EVRNVdXe8xTG4v2p0IqEFYWlYSzX9pO12rdtvo=; b=BqCsookey/8Yf2S2RphHYLOTUGQZa54kUVbe5xbHsODrPqxXIxrLqivb jV+s6JCkPtcifZ8KX0qRbRIkapxBNXMyVsAXlzoSzQC+8dRPw9rZ7gDR1 L0r/NYQW7wmD+18NGP9lQ1udlO6mnWN7vSQG1pjVMetj9jnO0XOZETvo+ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8FAFVtrlGtJXG+/2dsb2JhbABagwmDJbw1fRZ0giUBBHkSAQgOFFYlAgQOBQiIBb1xjnMxB4J6YQOIaKAXgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,802,1363132800"; d="scan'208";a="218815217"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 04 Jun 2013 22:45:28 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r54MjR85016265 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Jun 2013 22:45:27 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Tue, 4 Jun 2013 17:45:27 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Tim Bray <tbray@textuality.com>
Thread-Topic: [Json] Proposed change: update the Unicode version
Thread-Index: AQHOYUwcF9XONJEgqUaP+nfdT45kJZkmK8CA//+rbYCAAH8ngP//wLiA
Date: Tue, 04 Jun 2013 22:45:26 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70FC286AF@xmb-rcd-x10.cisco.com>
In-Reply-To: <CAHBU6isjx7rWvDXZBRqO9h5pjtjS_BL2SeiwtOM5vXA5GPrgug@mail.gmail.com>
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.212]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E67DD24C1E28864F82F9E9D5F4A420A0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Peter Saint-Andre <stpeter@stpeter.im>, "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 22:45:36 -0000

On 6/4/13 2:31 PM, "Tim Bray" <tbray@textuality.com> wrote:

>So how about ³A string is a sequence of zero or more Unicode characters
>defined in version 6.2 (or any subsequent version) of [UNICODE].²

Much better.

>WAS:
>
>JSON text SHALL be encoded in Unicode.  The default encoding is
>   UTF-8.
>
>Whether it¹s transmitted or read out of a file is irrelevant.

My point was that "Unicode" is not an encoding.

>JSON text takes the form of a Unicode string [UNICODE, section 2.7]; the
>default encoding is UTF-8.

That's fine.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email