Re: [Json] On representing what ECMA wants

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 19 June 2013 03:47 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 05A1B21E80B3 for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 20:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level:
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, 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 0CImaJsUDD2r for <json@ietfa.amsl.com>; Tue, 18 Jun 2013 20:47:56 -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 6BAAE21E8056 for <json@ietf.org>; Tue, 18 Jun 2013 20:47:56 -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 r5J3lsOo007940 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Jun 2013 20:47:55 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAK5yZYhsLhzsWF7P-NXUVZZtxzA2tO+y9httZQzCmOmvLzg0wg@mail.gmail.com>
Date: Tue, 18 Jun 2013 20:47:54 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD39C8CA-4B91-4E6F-8981-DC203B99CF80@vpnc.org>
References: <51B9EA49.2050604@crockford.com> <BF7E36B9C495A6468E8EC573603ED9411528A0E2@xmb-aln-x11.cisco.com> <51C1121E.8050004@crockford.com> <C9893DB6-027A-409C-92F2-A267FFE64BAA@vpnc.org> <CAHfnhfqyVL3n03y=UPa98MaFXjA4tLwFF9VLesaRL_7KNdg=4g@mail.gmail.com> <CAK5yZYhsLhzsWF7P-NXUVZZtxzA2tO+y9httZQzCmOmvLzg0wg@mail.gmail.com>
To: es-discuss <es-discuss@mozilla.org>, "json@ietf.org" <json@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: Re: [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:47:57 -0000

On Jun 18, 2013, at 8:39 PM, Mark Miller <erights@gmail.com> wrote:

> Hi Paul, I'm missing all the context, but from this out of context fragment, your response seems inappropriate. A statement like Doug's "I think this is the standard that ECMA wants to publish" sounds to me like speculation on how TC39 will react to some proposed standard.

If that's truly the case, such speculation from a random person is fine. Clearly, Douglas is not a random person: he is both the author of RFC 4627 and a TC39 member. If he meant to make that statement as neither, he needs to have said so.

> Whether coming from someone on TC39 or not, I do not see that any assertion of authority is involved. Here on es-discuss, both members and non-members of TC39 speculate and argue all the time on what kinds of things TC39 might approve of. Member of TC39 participate in these discussions, not to speak for TC39 as a whole, but to speak a) for themselves as participants in TC39, and b) as someone who is more informed than most, but still fallible, speculating about howTC39 might react to something. Perhaps this line gets blurry sometimes, but a statement like "I think this is the standard that ECMA wants to publish" seems to me clearly on the non-blurry side of that line.

Different SDOs have different customs, and in the IETF, custom says that you make clear when you are speculating and when you are representing. Douglas' earlier statement about ECMA was misinterpreted by WG members, so it felt worthwhile for the chairs to make clear who is and is not representing whom to the IETF.

--Paul Hoffman