IETF Logo Mail Archive

Re: [Json] A possible summary of the discussion so far on code points and characters

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 08 June 2013 21:09 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 9BAA521F935A for <json@ietfa.amsl.com>; Sat, 8 Jun 2013 14:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.105
X-Spam-Level:
X-Spam-Status: No, score=-102.105 tagged_above=-999 required=5 tests=[AWL=-0.106, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, 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 H5EbizUN4LH5 for <json@ietfa.amsl.com>; Sat, 8 Jun 2013 14:09:39 -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 44D2F21F92F5 for <json@ietf.org>; Sat, 8 Jun 2013 14:09:39 -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 r58L9ZX5049438 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 8 Jun 2013 14:09:35 -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: <CAChr6SwLDCUk0DC9pGTKqUu_V5vJHvs7Sgv4EneTJMryn1iKSA@mail.gmail.com>
Date: Sat, 8 Jun 2013 14:09:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D27EA9DC-9EFE-419B-BC34-3BF3FC8F5260@vpnc.org>
References: <AF793CAF-B30B-44A7-B864-82CEF79EA34D@vpnc.org> <CAChr6SwLDCUk0DC9pGTKqUu_V5vJHvs7Sgv4EneTJMryn1iKSA@mail.gmail.com>
To: R S <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] A possible summary of the discussion so far on code points and characters
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: Sat, 08 Jun 2013 21:09:39 -0000

On Jun 8, 2013, at 1:52 PM, R S <sayrer@gmail.com> wrote:

> A seventh point of view, which I happen to agree with: JSON strings are a sequence of code units.

That aligns with (2).

> 2) The ABNF is more liberal about what can be in a string than that statement:
>       char = unescaped /
>           escape ( ...
>               %x75 4HEXDIG )  ; uXXXX                U+XXXX
>       ...
>       unescaped = %x20-21 / %x23-5B / %x5D-10FFFF

--Paul Hoffman

v2.8.10 | Report a Bug | By Email