IETF Logo Mail Archive

Re: [Json] Complete section 3 proposal

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 19 June 2013 13:39 UTC

Return-Path: <paul.hoffman@vpnc.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 8F1F021F9BAF for <json@ietfa.amsl.com>; Wed, 19 Jun 2013 06:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level:
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8CXIpV0KzD6A for <json@ietfa.amsl.com>; Wed, 19 Jun 2013 06:39:49 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1C76221F91A5 for <json@ietf.org>; Wed, 19 Jun 2013 06:39:49 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5JDdiCX032230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Jun 2013 06:39:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <210C6860-3EAA-423B-93FD-926D71151C07@tzi.org>
Date: Wed, 19 Jun 2013 06:39:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE9011E2-508B-4CDC-958B-6B726F98F8CA@vpnc.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC58C0B@xmb-rcd-x10.cisco.com> <C9A3CF00-3B30-4DE4-95C4-9F3E6CA2DA86@vpnc.org> <210C6860-3EAA-423B-93FD-926D71151C07@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1508)
Cc: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Complete section 3 proposal
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, 19 Jun 2013 13:39:49 -0000

On Jun 19, 2013, at 12:36 AM, Carsten Bormann <cabo@tzi.org> wrote:

> On Jun 19, 2013, at 00:16, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> 
>> Because the first code point of a JSON text will always be a character in the range U+0022 to U+007B,
> 
> The following six characters can occur at the start of a JSON text:
> 
>           %x20                ; Space
>           %x09                ; Horizontal tab
>           %x0A                ; Line feed or New line
>           %x0D                ; Carriage return
> 
>           %x5B                ; [ left square bracket
>           %x7B                ; { left curly bracket
> 
> Four of those six characters are not in that range.

Very good point. s/U+0022/U+0009/.

> They are all in the ASCII subset of Unicode.

The "ASCII subset of Unicode" is not well-defined, and for bonus confusion, includes U+0000.

> (Of course, that set might increase if we redefine what a JSON text is, but it is likely to stay ASCII.)

We are trying to deal with one discussion topic at a time. We are not succeeding, but we are trying.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email