Re: [Json] JSON & ECMA

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 25 March 2013 15: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 090AD21F8EEA for <json@ietfa.amsl.com>; Mon, 25 Mar 2013 08:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.372
X-Spam-Level:
X-Spam-Status: No, score=-101.372 tagged_above=-999 required=5 tests=[AWL=-1.228, BAYES_00=-2.599, FRT_ADOBE2=2.455, 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 JVPdOm3LUwCg for <json@ietfa.amsl.com>; Mon, 25 Mar 2013 08:51:59 -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 92CF821F8D35 for <json@ietf.org>; Mon, 25 Mar 2013 08:51:59 -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 r2PFptRS009143 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 25 Mar 2013 08:51:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D1E88488177@nambxv01a.corp.adobe.com>
Date: Mon, 25 Mar 2013 08:51:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA571E22-6F75-474F-A371-335BF7358C78@vpnc.org>
References: <C68CB012D9182D408CED7B884F441D4D1E883516CD@nambxv01a.corp.adobe.com> <6F8EC872-CF09-428A-A675-E96462DD5972@vpnc.org> <CAHBU6isfWR=qP5aK0T=tH7ozFF+JjQh+rNB=m7F-5h=vK=MYPQ@mail.gmail.com> <C68CB012D9182D408CED7B884F441D4D1E88488177@nambxv01a.corp.adobe.com>
To: Larry Masinter <masinter@adobe.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: Mon, 25 Mar 2013 15:52:00 -0000

On Mar 24, 2013, at 1:56 PM, Larry Masinter <masinter@adobe.com> wrote:

> How about “The working group should work to ensure that the JSON specification produced will be suitable for being the normative definition of JSON referenced from specifications from other standards groups, including W3C and ECMA TC39.”

How is that an actionable statement for the charter?

What could this WG do that would *not* make the specification we produce "be suitable for being the normative definition of JSON referenced from specifications from other standards groups, including W3C and ECMA TC39"?

> That doesn’t require any direct coordination, but makes it clear that the intent is that other specs normatively reference this one.

I think us putting in the charter things that put pressure on other SDOs is not terribly productive for anyone. Maybe let's keep the charter about the IETF work.

--Paul Hoffman