[Json] On representing what ECMA wants

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 19 June 2013 03:01 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 C786411E812F for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 20:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level:
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, 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 voJfRlKy-5ZJ for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 20:01:54 -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 D059111E8133 for <json@ietf.org>; Tue, 18 Jun 2013 20:01:49 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r5J31iPo007100 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 20:01:45 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51C1121E.8050004@crockford.com>
Date: Tue, 18 Jun 2013 20:01:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9893DB6-027A-409C-92F2-A267FFE64BAA@vpnc.org>
References: <51B9EA49.2050604@crockford.com> <BF7E36B9C495A6468E8EC573603ED9411528A0E2@xmb-aln-x11.cisco.com> <51C1121E.8050004@crockford.com>
To: Douglas Crockford <douglas@crockford.com>
X-Mailer: Apple Mail (2.1508)
Cc: json@ietf.org
Subject: [Json] On representing what ECMA wants
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 19 Jun 2013 03:01:59 -0000

<two chair hats on>

On Jun 18, 2013, at 7:06 PM, Douglas Crockford <douglas@crockford.com> wrote:

> I think this is the standard that ECMA wants to publish.

As you know from our earlier off-list discussions, you do not represent ECMA, nor even TC39, to the IETF, nor even to this WG. Everyone from TC39 represents themselves here. Your statement above still implies authority that doesn't exist.

ECMA and TC39 leadership has had, and probably will continue to have, discussions about whether ECMA wants to have an official position on what they want to see from the IETF. Until we hear that from those higher-ups, no one speaks for ECMA here (and no one speaks for the IETF in TC39). Please try harder to refrain from suggesting that particular technical or process decisions would be what ECMA wants. Thanks in advance.

--Matt and Paul