Re: [Json] Response to Statement from Ecma International TC39
Nico Williams <nico@cryptonector.com> Thu, 05 December 2013 06:58 UTC
Return-Path: <nico@cryptonector.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2235B1A1F3E for <json@ietfa.amsl.com>; Wed, 4 Dec 2013 22:58:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ebCp4qLfi19V for <json@ietfa.amsl.com>; Wed, 4 Dec 2013 22:58:09 -0800 (PST)
Received: from homiemail-a109.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id 8A47D1A1F3D for <json@ietf.org>; Wed, 4 Dec 2013 22:58:09 -0800 (PST)
Received: from homiemail-a109.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTP id 81C292005D908; Wed, 4 Dec 2013 22:58:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=4gzmI0wNwCj8yl7SkaYPNS6zE6w=; b=eNUd6HiJUwm nt3hvdASYvNXEh5Ityp45p/ftOA+a7oLJisO194u7XrmtVVLI3zrzey85CVkjT8X 5Fxiw1SAmo0ftv39TV5R56jiXRlcAlHzEVH8Bb4Qqbm+bmumiKb/wi+JMVXW0+IQ ySqeW8VgR5t6g+6UTo/h9XjFZfbwiNzI=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTPA id 2A58E2005D907; Wed, 4 Dec 2013 22:58:06 -0800 (PST)
Date: Thu, 05 Dec 2013 00:58:05 -0600
From: Nico Williams <nico@cryptonector.com>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <20131205065802.GM21240@localhost>
References: <C7707CE2-C43E-4171-AE96-9FAFDCE53317@cisco.com> <20131205044253.GH21240@localhost> <D4601105-6F83-4709-B309-298529E4B17E@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <D4601105-6F83-4709-B309-298529E4B17E@tzi.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable
Cc: JSON WG <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] Response to Statement from Ecma International TC39
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 05 Dec 2013 06:58:11 -0000
On Thu, Dec 05, 2013 at 07:43:52AM +0100, Carsten Bormann wrote: > On 05 Dec 2013, at 05:42, Nico Williams <nico@cryptonector.com> wrote: > > I don't think we ought to demand anything more than stability for > > normatively referencing ECMA-404. > > Whoa. > Actually, a major prerequisite is that any spec we rely on by > referencing it normatively is a good specification. OK, I grant that :) I was referring to process, however. We really want to demand the stability of non-Internet standards normatively referenced from Internet standards as we do of Internet standards normatively [...]. IIRC the IETF does occasionally permit some normative downrefs, but asking for a downref is asking for sturm und drang. > Saying that the process leading to ECMA-404 wasn’t open may also be a > veiled expression of dissatisfaction with the outcome. [...] Maybe so, but that's neither here nor there. If ECMA-404's quality is insufficient then we won't reference it normatively. If it is insufficiently stable then we won't reference it normatively. That ECMA is or is not as open as we'd like is irrelevant -- that was my point, in particular that we ought not make demands about their process (or at least not without having WG consensus for such a heavy-handed position, and preferably more than WG consensus). Nico --
- [Json] Response to Statement from Ecma Internatio… Matt Miller (mamille2)
- Re: [Json] Response to Statement from Ecma Intern… Nico Williams
- Re: [Json] Response to Statement from Ecma Intern… Tim Bray
- Re: [Json] Response to Statement from Ecma Intern… Nico Williams
- Re: [Json] Response to Statement from Ecma Intern… Martin J. Dürst
- Re: [Json] Response to Statement from Ecma Intern… Carsten Bormann
- Re: [Json] Response to Statement from Ecma Intern… Carsten Bormann
- Re: [Json] Response to Statement from Ecma Intern… Nico Williams
- Re: [Json] Response to Statement from Ecma Intern… Nico Williams
- Re: [Json] Response to Statement from Ecma Intern… Paul Hoffman
- Re: [Json] Response to Statement from Ecma Intern… Paul Hoffman
- Re: [Json] Response to Statement from Ecma Intern… Paul Hoffman
- Re: [Json] Response to Statement from Ecma Intern… R S
- Re: [Json] Response to Statement from Ecma Intern… Paul Hoffman
- Re: [Json] Response to Statement from Ecma Intern… R S
- Re: [Json] Response to Statement from Ecma Intern… Mark Nottingham
- Re: [Json] Response to Statement from Ecma Intern… Paul Hoffman
- Re: [Json] Response to Statement from Ecma Intern… Tim Bray
- Re: [Json] Response to Statement from Ecma Intern… Mark Nottingham
- Re: [Json] Response to Statement from Ecma Intern… R S
- Re: [Json] Response to Statement from Ecma Intern… R S
- Re: [Json] Response to Statement from Ecma Intern… R S
- Re: [Json] Response to Statement from Ecma Intern… Tim Bray
- Re: [Json] Response to Statement from Ecma Intern… John Levine
- Re: [Json] Response to Statement from Ecma Intern… R S
- Re: [Json] Response to Statement from Ecma Intern… Martin J. Dürst
- Re: [Json] Response to Statement from Ecma Intern… Pete Resnick