IETF Logo Mail Archive

Re: [Json] [apps-discuss] JSON mailing list and BoF

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 19 February 2013 23:52 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 4DB5E21F88B9 for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 15:52:41 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJdvLt3o0L5H for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 15:52:40 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4122721F889A for <json@ietf.org>; Tue, 19 Feb 2013 15:52:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1910; q=dns/txt; s=iport; t=1361317955; x=1362527555; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=aK+2IBeM7EOyjH7OCVNpdjvWwY1t3FzYmQOhHoE0BuI=; b=EIrYbOSjs0/VCN4a8l1G+Dr0gLQkRXuGysNyKFlKYS34TZY2A6ZCze8J nXjZP38sjJkM3IrnLH1KoK306Gcu1ChjBFCljkHDv/Hs75A5Y791f0c1n YrqRvkJzIUkG2h5tZXiGXksHOUZsko8RmHGZnK54/ZG28mQhiN27lyUC+ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFABEPJFGtJXHB/2dsb2JhbABFwESBDRZzgh8BAQEEbgsSAQgOCgpFESUCBAENBQiHeAMPDLAlhkINiVqMN4IkAjEHgl9hA4gwjCCNHoUVgweBayQY
X-IronPort-AV: E=Sophos;i="4.84,698,1355097600"; d="scan'208";a="175938452"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 19 Feb 2013 23:52:34 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1JNqYeT002654 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Feb 2013 23:52:34 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.195]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Tue, 19 Feb 2013 17:52:34 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Tim Bray <tbray@textuality.com>, Francis Galiegue <fgaliegue@gmail.com>
Thread-Topic: [Json] [apps-discuss] JSON mailing list and BoF
Thread-Index: AQHODu/VV0zn7u2LJ02Uk/kU6xbmZ5iBsyqAgAB3XoCAAAEJgP//kdsAgAB2rYCAAAg/AP//jWIA
Date: Tue, 19 Feb 2013 23:52:34 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70F898351@xmb-rcd-x10.cisco.com>
In-Reply-To: <CAHBU6iub4vp2QrcGNmAg+2rz=JhP1x7fW43e5L3gNkuLz442wg@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.1.130117
x-originating-ip: [10.21.119.56]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <99D1A35882B1F44AAE12D63DAFBA3C30@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Nico Williams <nico@cryptonector.com>, "json@ietf.org" <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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, 19 Feb 2013 23:52:41 -0000

Nor was I suggesting we do so.

I was suggesting that if you want to get \u0000 - \u001f, excluding
\u0008(\b), \u0009(\t), \u000a(\n), \u000c(\f), and \u000d(\r) into the
canonicalized output, you have to use the \u notation, which means we
can't outlaw \u notation entirely in the canonicalized form, as some of us
thought Tim had suggested in the first place.

Note, I was wrong about \u0000 being the only codepoint we care about.
>From section 2.5 of 4627:

"All Unicode characters may be placed within the
   quotation marks except for the characters that must be escaped:
   quotation mark, reverse solidus, and the control characters (U+0000
   through U+001F)."



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

>I haven¹t heard anyone saying U+0000 should be illegal in JSON.  It¹s too
>late to redesign JSON. -T
>
>
>
>On Tue, Feb 19, 2013 at 3:13 PM, Francis Galiegue
><fgaliegue@gmail.com> wrote:
>
>On Wed, Feb 20, 2013 at 12:08 AM, Joe Hildebrand (jhildebr)
><jhildebr@cisco.com> wrote:
>[...]
>>>
>>>
>>>He means "\u0000 is an exception to Tim's proposed 'forbid escaping'
>>>rule".
>>
>> Exactly.  It's the only code point that I know of that MUST be escaped
>> using \uxxxx notation when serialized (either canonically or otherwise).
>> All of the other codepoints that need to be escaped have \x versions.
>>
>
>
>OK, but why should it be considered illegal at all? Any ASCII
>character is representable by such a sequence, it just happens that 0
>can where ASCII can't... I don't see this as a reason to outlaw this
>particular sequence... Or there is something I don't understand in
>your argument.
>
>--
>Francis Galiegue, fgaliegue@gmail.com
>Try out your JSON Schemas:
>http://json-schema-validator.herokuapp.com
><http://json-schema-validator.herokuapp.com>
>
>
>
>
>
>
>
>



-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email