Re: [Json] Proposal for strings/Unicode text

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 17 June 2013 18:23 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 8439D21F9C62 for <json@ietfa.amsl.com>; Mon, 17 Jun 2013 11:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level:
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, 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 KImlx9CUmBUX for <json@ietfa.amsl.com>; Mon, 17 Jun 2013 11:23:52 -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 C82FF21F99A5 for <json@ietf.org>; Mon, 17 Jun 2013 11:23:50 -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 r5HINl10043198 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 17 Jun 2013 11:23:47 -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: <E69AED08-B07F-4D1B-9BEF-9A7B06454672@tzi.org>
Date: Mon, 17 Jun 2013 11:23:46 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BF89BC7-94E4-419D-BF7B-787022F7E7B2@vpnc.org>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC52202@xmb-rcd-x10.cisco.com> <52755324-4C8D-452A-9A84-14691ACEEC7E@vpnc.org> <E69AED08-B07F-4D1B-9BEF-9A7B06454672@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1508)
Cc: "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, json@ietf.org
Subject: Re: [Json] Proposal for strings/Unicode text
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: Mon, 17 Jun 2013 18:24:00 -0000

Even though there are currently comments for all the simple strings, my personal preference would not to be to add a comment to this more complex one, and to instead let the ABNF stand on its own. 

So far, the proposed comment additions have confused what JSON requires to be *escaped* from what JSON *allows as codepoints* in strings. Adding comments to spell out the character names will make this misunderstanding worse, in my opinion.

--Paul Hoffman