Re: [Json] JSON & ECMA

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 16 March 2013 16:52 UTC

Return-Path: <paul.hoffman@vpnc.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 BB45021F8922 for <json@ietfa.amsl.com>; Sat, 16 Mar 2013 09:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 8EpbW20n5TAY for <json@ietfa.amsl.com>; Sat, 16 Mar 2013 09:52:00 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3687F21F8901 for <json@ietf.org>; Sat, 16 Mar 2013 09:52:00 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r2GGpuri093727 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 16 Mar 2013 09:51:57 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51437A60.607@crockford.com>
Date: Sat, 16 Mar 2013 09:51:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAAE16FA-508A-4E49-9F8D-B3F94E1DFAD7@vpnc.org>
References: <51437A60.607@crockford.com>
To: Douglas Crockford <douglas@crockford.com>
X-Mailer: Apple Mail (2.1503)
Cc: json@ietf.org
Subject: Re: [Json] JSON & ECMA
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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, 16 Mar 2013 16:52:00 -0000

On Mar 15, 2013, at 12:45 PM, Douglas Crockford <douglas@crockford.com> wrote:

> The JSON Standard was inspired by ECMA's ECMAScript Standard, Third Edition, but is not dependent on it. ECMAScript Fifth Edition does not define JSON, but implements the JSON standard in ECMAScript.

I read the text in v5.1 as defining JSON, even if the JSON community doesn't allow that. That is, I don't see anything there that says "this is not really the standard".

> Changes in the ECMAScript Standard have no impact on JSON. JSON is language independent.

Both are good to hear.

> There is a question about where the JSON Standard should live. One theory is that it should be at IETF, because there is an informational RFC that associated JSON with the MIME type application/json. The other theory is that the standard should live at ECMA because JSON was initially derived from ECMAScript, and because ECMA is related to ISO.
> 
> I do not know how this should be decided.

In some sense, the people who decide that are the JSON-using community. There is no law here, just code.

--Paul Hoffman