IETF Logo Mail Archive

Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)

Carsten Bormann <cabo@tzi.org> Thu, 28 November 2013 16:16 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 206C11ACCFC; Thu, 28 Nov 2013 08:16:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfFx7X2fFnji; Thu, 28 Nov 2013 08:16:42 -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 011DF1AC404; Thu, 28 Nov 2013 08:16:41 -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 rASGGZ7C012519; Thu, 28 Nov 2013 17:16:35 +0100 (CET)
Received: from [192.168.217.105] (p5489053C.dip0.t-ipconnect.de [84.137.5.60]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 4254F70A; Thu, 28 Nov 2013 17:16:34 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6C28E0DD-5E45-42DB-A915-795EE0A489CC@w3.org>
Date: Thu, 28 Nov 2013 17:16:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <38918D14-D7ED-4983-8A46-4CA4D1C7BE96@tzi.org>
References: <CADnb78h8AjPcQLOCwNm0Pt3pObh6uFV5+zy0c_YU6B-u4MtY1Q@mail.gmail.com> <AA45B3C6-1DC5-4B1E-8045-C9FE76022584@vpnc.org> <C93F89AD-81D2-4489-ADC4-AB05A5B10883@cisco.com> <CAHBU6itgE9=WP+c0oXt1W647b1zz+N6+4ZqRa63Ve91TUsGzTA@mail.gmail.com> <CANr5HFVhG5SNhW4yJxDicvFman94FaNi8UZHhcpQbH6AG6pfQg@mail.gmail.com> <CAHBU6it-yHeHVY+3EFvPd0pVu4uLLdH3Gmz53LL4DZWJSyyUuQ@mail.gmail.com> <6C28E0DD-5E45-42DB-A915-795EE0A489CC@w3.org>
To: Tim Berners-Lee <timbl@w3.org>
X-Mailer: Apple Mail (2.1822)
Cc: IETF Discussion <ietf@ietf.org>, JSON WG <json@ietf.org>, Alex Russell <slightlyoff@google.com>, Tim Bray <tbray@textuality.com>, "Matt Miller (mamille2)" <mamille2@cisco.com>, "www-tag@w3.org" <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
Subject: Re: [Json] Consensus on JSON-text (WAS: JSON: remove gap between Ecma-404 and IETF draft)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Nov 2013 16:16:43 -0000

On 28 Nov 2013, at 05:51, Tim Berners-Lee <timbl@w3.org> wrote:

> JSON is interesting in being a subset of ECMAscript.  

That was a clever device used by Douglas Crockford to minimize the bike shedding that was inevitable when he designed the data format.  That device is no longer necessary, indeed, it has become a liability as ECMAscript moved forward.

> That is a big dependency -- will it be preserved?

There is no dependency any more, and the subset relationship has already been destroyed by the introduction of Line/Paragraph separators (U+2028/U+2029) in recent versions of ECMAscript (these are valid in JSON strings but not in ECMAscript 5 strings).

It is best to acknowledge the role of JavaScript as the inspiration for the JSON data interchange format (and one of its biggest customers), but otherwise consider the two specifications independent of each other.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email