IETF Logo Mail Archive

[Json] JSON & ECMA

Larry Masinter <masinter@adobe.com> Sat, 16 March 2013 22:20 UTC

Return-Path: <masinter@adobe.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 E37E921F8739 for <json@ietfa.amsl.com>; Sat, 16 Mar 2013 15:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.522
X-Spam-Level:
X-Spam-Status: No, score=-104.522 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077, 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 2H0Toaa2fr2G for <json@ietfa.amsl.com>; Sat, 16 Mar 2013 15:20:39 -0700 (PDT)
Received: from exprod6og103.obsmtp.com (exprod6og103.obsmtp.com [64.18.1.185]) by ietfa.amsl.com (Postfix) with ESMTP id 566CB21F86E6 for <json@ietf.org>; Sat, 16 Mar 2013 15:20:39 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob103.postini.com ([64.18.5.12]) with SMTP ID DSNKUUTwN1XWR4myrc2L9InYTaRqgyrVKYL8@postini.com; Sat, 16 Mar 2013 15:20:39 PDT
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r2GMHX1v018399 for <json@ietf.org>; Sat, 16 Mar 2013 15:17:33 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r2GMKcAV009244 for <json@ietf.org>; Sat, 16 Mar 2013 15:20:38 -0700 (PDT)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Sat, 16 Mar 2013 15:20:38 -0700
From: Larry Masinter <masinter@adobe.com>
To: "json@ietf.org" <json@ietf.org>
Date: Sat, 16 Mar 2013 15:20:36 -0700
Thread-Topic: JSON & ECMA
Thread-Index: Ac4ik25uekMU3EPmRSeQIXoUGNxzjA==
Message-ID: <C68CB012D9182D408CED7B884F441D4D1E883516CD@nambxv01a.corp.adobe.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sat, 16 Mar 2013 22:20:40 -0000

I wish the charter included an explicit liaison statement about coordinating with TC39 to insure that the new IETF spec is suitable for, and used as normative reference from ECMAScript 6. 

I also wish the charter included an explicit liaison with both W3C and WHATWG that made forking unlikely, because of participation in the review.

I'd like to work on updating http://tools.ietf.org/html/bcp70 , RFC 3470, "Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols" to cover JSON and also the considerations of XML vs. JSON,  as a working group item.

v2.23.0 | Report a Bug | By Email