W3C home > Mailing lists > Public > www-tag@w3.org > November 2013

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

From: Joe Hildebrand (jhildebr) <jhildebr@cisco.com>
Date: Wed, 13 Nov 2013 20:43:10 +0000
To: Carsten Bormann <cabo@tzi.org>
CC: Paul Hoffman <paul.hoffman@vpnc.org>, Anne van Kesteren <annevk@annevk.nl>, es-discuss <es-discuss@mozilla.org>, IETF Discussion <ietf@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, JSON WG <json@ietf.org>
Message-ID: <CEA9315C.2CD5F%jhildebr@cisco.com>
On 11/13/13 1:32 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

>On 13 Nov 2013, at 12:24, Joe Hildebrand (jhildebr) <jhildebr@cisco.com>
>wrote:
>
>> changing the ABNF:
>> 
>> JSON-text = value
>
>(would need to add the whitespace ‹ that is not visible in the ECMA 404
>racetracks because they use an implicit whitespace rule.)

Good catch.

>There has been a long discussion in the WG about this potential change, I
>donąt want to repeat it here.
>It may be worthwhile to dig up pointers to how that resulted in not
>making the change, for observers outside the WG.

I would argue that we didn't have adequate representation from TC39 in
that discussion, and that their getting involved is as good a reason as
any to double-check that we've still got the same consensus.  I know that
I for one decided to stop pushing for this when it looked like there were
a few more participants that wanted the status quo.

-- 
Joe Hildebrand
Received on Wednesday, 13 November 2013 20:43:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:59 UTC