IETF Logo Mail Archive

Re: [Json] JSON: remove gap between Ecma-404 and IETF draft

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 14 November 2013 03:15 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 4EFF021E812D; Wed, 13 Nov 2013 19:15:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.993
X-Spam-Level:
X-Spam-Status: No, score=-101.993 tagged_above=-999 required=5 tests=[AWL=-0.594, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, J_CHICKENPOX_45=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 6q+YsphG5hAi; Wed, 13 Nov 2013 19:15:50 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id D5D3C21E8056; Wed, 13 Nov 2013 19:15:50 -0800 (PST)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id rAE3FT5Q000759 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 13 Nov 2013 20:15:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <2E62DA50-F941-4A0E-A7B3-966A0DDE4C7A@wirfs-brock.com>
Date: Wed, 13 Nov 2013 19:15:28 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8176E98-1CFB-4A3D-A8D7-EBBC759152AA@vpnc.org>
References: <CEA95C60.2CF3C%jhildebr@cisco.com> <2E62DA50-F941-4A0E-A7B3-966A0DDE4C7A@wirfs-brock.com>
To: Allen Wirfs-Brock <allen@wirfs-brock.com>
X-Mailer: Apple Mail (2.1822)
Cc: John Cowan <cowan@mercury.ccil.org>, IETF Discussion <ietf@ietf.org>, JSON WG <json@ietf.org>, Joe Hildebrand Hildebrand <jhildebr@cisco.com>, Anne van Kesteren <annevk@annevk.nl>, "www-tag@w3.org" <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
Subject: Re: [Json] JSON: remove gap between Ecma-404 and IETF draft
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: Thu, 14 Nov 2013 03:15:51 -0000

<no hat>

On Nov 13, 2013, at 6:35 PM, Allen Wirfs-Brock <allen@wirfs-brock.com> wrote:

> 
> On Nov 13, 2013, at 3:51 PM, Joe Hildebrand (jhildebr) wrote:
> 
>> On 11/13/13 3:47 PM, "John Cowan" <cowan@mercury.ccil.org> wrote:
>> 
>>> It's not clear that 404 disallows it, since 404 is defined in terms of
>>> characters, and a BOM is not a character but an out-of-band signal.
> 
> However, for example, a conforming implementation of the ECMAScript JSON.parse function would reject any string passed to it that starts with a U+FFEF code point because the unquoted occurrence of that code point does not conform to the ECMA-252, 5th Edition or Ecma-404 JSON grammar.
> 
> In order to be successfully processed, that code point would have to be stripped from the string prior to calling JSON.parse.

The question was specifically about ECMA-404, not ECMA-252. It would be great to hear from TC39 whether or not ECMA-404 allows or disallows it.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email