IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 13 November 2013 21:41 UTC

Return-Path: <cabo@tzi.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 625C721E816D; Wed, 13 Nov 2013 13:41:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 WTUBB2z5QZda; Wed, 13 Nov 2013 13:41:15 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id CFE8D21E8142; Wed, 13 Nov 2013 13:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id rADLe85r013006; Wed, 13 Nov 2013 22:40:08 +0100 (CET)
Received: from [192.168.101.128] (unknown [64.245.0.218]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C07E0E18; Wed, 13 Nov 2013 22:40:04 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <3389CD77-B1CC-4A76-907A-6D400DA028CC@vpnc.org>
Date: Wed, 13 Nov 2013 13:40:01 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <017375D1-898E-4012-8328-83A35C9ABFA3@tzi.org>
References: <CEA92854.2CC53%jhildebr@cisco.com> <3389CD77-B1CC-4A76-907A-6D400DA028CC@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1822)
Cc: es-discuss <es-discuss@mozilla.org>, IETF Discussion <ietf@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, JSON WG <json@ietf.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: Wed, 13 Nov 2013 21:41:21 -0000

On 13 Nov 2013, at 13:27, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> It would be nice if ECMA-404 was clearer on this

I think the only way to read the English prose in ECMA-404 is to always allow insignificant whitespace around every token, including the single token that makes up an out-of-container JSON value.
That is also consistent with the most widely deployed extensions of JSON for out-of-container values, including the one in recent JavaScript.

(Yes, it is easier to be unambiguous with ABNF.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email