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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Wed, 13 November 2013 21:54 UTC

Return-Path: <jhildebr@cisco.com>
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 DF18911E810A; Wed, 13 Nov 2013 13:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.381
X-Spam-Level:
X-Spam-Status: No, score=-10.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 KtcZpBqYybCM; Wed, 13 Nov 2013 13:54:31 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 47EC121E80DC; Wed, 13 Nov 2013 13:54:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=882; q=dns/txt; s=iport; t=1384379671; x=1385589271; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=eiaT16M54LqUWLs7B6x7UZcQxB/bovnBPJ/An6/1MwU=; b=FoMBvXPvLMZYMkCxUwjAcIqAitLSTCvwz5G2ozYAuSTy2mhahPuKevDz udjFi5OB3ppGQsgJfs1Dfj/rGdw7BFLl7bBR45Tn0dmSsEavqwJAZa4yM 3HTP+0m4gDYGuHc0XIcr7yh4gsONCMRL3Tmw0O4XXJ5vqTO3aBb99Jm0o E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFANzzg1KtJV2a/2dsb2JhbABZgweBC78sgSgWdIIlAQEBBDotEhIBCA4KHkIlAgQBDQWIAcAoj18HhDEDmBCSC4Mogio
X-IronPort-AV: E=Sophos;i="4.93,695,1378857600"; d="scan'208";a="284280306"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 13 Nov 2013 21:54:31 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rADLsUvw012706 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Nov 2013 21:54:30 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Wed, 13 Nov 2013 15:54:30 -0600
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>
Thread-Topic: [Json] JSON: remove gap between Ecma-404 and IETF draft
Thread-Index: AQHO37wfJCh2AJRFT02Gmc0EpJu9eJojjGwAgACHIgCAAANegP//jrEA
Date: Wed, 13 Nov 2013 21:54:29 +0000
Message-ID: <CEA942AB.2CEB4%jhildebr@cisco.com>
In-Reply-To: <017375D1-898E-4012-8328-83A35C9ABFA3@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.129.24.62]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B4709C57FF01F7448C282DEA4B892E0C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: JSON WG <json@ietf.org>, IETF Discussion <ietf@ietf.org>, "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: Wed, 13 Nov 2013 21:54:37 -0000

On 11/13/13 2:40 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

>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.)

Note further that since ECMA-404 says:

"The whitespace characters are: character tabulation (U+0009), line feed
(U+000A), carriage return (U+000D), and space (U+0020)"

that the encoding detection does not need to be modified again with this
change.

-- 
Joe Hildebrand