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

Noah Mendelsohn <nrm@arcanedomain.com> Sat, 30 November 2013 18:57 UTC

Return-Path: <nrm@arcanedomain.com>
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 603F51AE1B1; Sat, 30 Nov 2013 10:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 mJz1Q2Z63GWM; Sat, 30 Nov 2013 10:57:13 -0800 (PST)
Received: from homiemail-a5.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9CF1AE1AB; Sat, 30 Nov 2013 10:57:13 -0800 (PST)
Received: from homiemail-a5.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a5.g.dreamhost.com (Postfix) with ESMTP id 3A94170406A; Sat, 30 Nov 2013 10:57:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=arcanedomain.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= arcanedomain.com; bh=USq/aRfi019ci5J9/EFqepOH5kQ=; b=KegB4DL6rjA LlKF4kujsO6BYIpeZmFR5MIMTy/qlCeIYxU56ZK6oNItF9fRoKtfQuNnXYWvbtey p7O2yLfbmnIgIqvR68Mnn4L+PoJeo39KzvdkpJpzd+mC+2gySiD8LKbDT9LAVdC1 fQjWY2ZJojwJz/ncmNixlzwHE2vdjJWw=
Received: from [192.168.1.102] (unknown [146.115.66.224]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: webmaster@arcanedomain.com) by homiemail-a5.g.dreamhost.com (Postfix) with ESMTPSA id 099B5704063; Sat, 30 Nov 2013 10:57:09 -0800 (PST)
Message-ID: <529A350A.60602@arcanedomain.com>
Date: Sat, 30 Nov 2013 13:57:14 -0500
From: Noah Mendelsohn <nrm@arcanedomain.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Tim Berners-Lee <timbl@w3.org>, Tim Bray <tbray@textuality.com>
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>
In-Reply-To: <6C28E0DD-5E45-42DB-A915-795EE0A489CC@w3.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 30 Nov 2013 13:44:33 -0800
Cc: IETF Discussion <ietf@ietf.org>, JSON WG <json@ietf.org>, Alex Russell <slightlyoff@google.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: Sat, 30 Nov 2013 18:57:14 -0000

On 11/27/2013 11:51 PM, Tim Berners-Lee wrote:

> JSON is interesting in being a subset of ECMAscript.  That is a big
> dependency -- will it be preserved?


> However as it is unwise to feed JSON into an ECMAscript processor for
> security reasons, that dependency may not affect code, just mean that
> JSON and ECMAscript parsers can share parts at  the moment.

There may be many other situations in which there is benefit to having JSON 
be a proper subset of ECMAscript. For example, one can imagine tool chains 
used for development or testing that would depend on the ability to copy 
text fragments between JSON and ECMAscript source documents, and one might 
foresee more "vertical" standards that would depend on the commonality as 
well.

Noah