[Json] JSON & ECMA

Douglas Crockford <douglas@crockford.com> Fri, 15 March 2013 19:45 UTC

Return-Path: <douglas@crockford.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 7F88921F8873 for <json@ietfa.amsl.com>; Fri, 15 Mar 2013 12:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.522
X-Spam-Level:
X-Spam-Status: No, score=-0.522 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJ_ALL_CAPS=2.077]
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 RQy4tG0beHt2 for <json@ietfa.amsl.com>; Fri, 15 Mar 2013 12:45:43 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id E484521F8891 for <json@ietf.org>; Fri, 15 Mar 2013 12:45:42 -0700 (PDT)
Received: from [192.168.113.95] ([216.113.168.135]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MVNTS-1UEoOo3DtG-00ZB0k; Fri, 15 Mar 2013 15:45:42 -0400
Message-ID: <51437A60.607@crockford.com>
Date: Fri, 15 Mar 2013 12:45:36 -0700
From: Douglas Crockford <douglas@crockford.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: json@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:ut2IQMIHLlcKBrPnzSBMjc8N88P1FImyzF9T7Z4QnXo /5PT61zxfdsJ726dP8JJbTdSW5Jd0NBbqOSzSBCRw0JjYfQ0UD 0aohxdYjnWSP+TPLpE3V8nt8pIQQQNBr8cR9Ofl7CdDbIjaW8l Vv42Da8IRAlo4xfmVqBKibogVd1JDE7b7rIysQkmRodZCwgvJo IhNZ/TjQuHaBBDI55J32p1DjF53rtugQGjOLY5frd0x9XvhdXf yK5PvEGd7z/V+HpUPb+3rMlbiXl/ZMiDbJjfQr0lmoyklCGghT TP55UJSSI2CZOoaWa4vzx71UV3IB3EGQZotqKiZWAb3yLMGHXR uMJ0aY+V0zQqoxi4vhts=
Subject: [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: Fri, 15 Mar 2013 19:45:43 -0000

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. Changes in 
the ECMAScript Standard have no impact on JSON. JSON is language 
independent.

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.