Re: [Json] Counterproposal on work items
Peter Saint-Andre <stpeter@stpeter.im> Thu, 21 February 2013 01:44 UTC
Return-Path: <stpeter@stpeter.im>
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 CAA4521F8558 for <json@ietfa.amsl.com>; Wed, 20 Feb 2013 17:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level:
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+xcQtOy+wng for <json@ietfa.amsl.com>; Wed, 20 Feb 2013 17:44:24 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B740221F854D for <json@ietf.org>; Wed, 20 Feb 2013 17:44:24 -0800 (PST)
Received: from [192.168.1.7] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 201AC403CD; Wed, 20 Feb 2013 18:51:53 -0700 (MST)
Message-ID: <51257BF6.2060408@stpeter.im>
Date: Wed, 20 Feb 2013 18:44:22 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <CAHBU6ityBeA+M-PEme09gO_jVySr33-X308i1UttxrQwSgYmGQ@mail.gmail.com> <0F513426-F26D-48F4-A7A8-88F3D3DA881B@vpnc.org> <CAK3OfOjFCnR8k1csVOkSKTDpA8exDvYdAijn80HKD5zwNzzeSw@mail.gmail.com> <4514F5D7-4A7E-476F-987D-C4C617F2BCBD@vpnc.org> <4D80AE86-4DBA-4236-9E2A-A06F2F9C30F7@mnot.net>
In-Reply-To: <4D80AE86-4DBA-4236-9E2A-A06F2F9C30F7@mnot.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Counterproposal on work items
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: Thu, 21 Feb 2013 01:44:25 -0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/20/13 3:30 PM, Mark Nottingham wrote: > On 21/02/2013, at 6:02 AM, Paul Hoffman <paul.hoffman@vpnc.org> > wrote: > >> On Feb 20, 2013, at 10:43 AM, Nico Williams >> <nico@cryptonector.com> wrote: >> >>> On Wed, Feb 20, 2013 at 11:38 AM, Paul Hoffman >>> <paul.hoffman@vpnc.org> wrote: >>>> On Feb 20, 2013, at 9:27 AM, Tim Bray <tbray@textuality.com> >>>> wrote: >>>>> My proposal is: do nothing. >>>> >>>> -1. >>>> >>>> There are places where RFC 4627 has SHOULDs where some >>>> processors do one thing and others do something different. >>>> That should be cleaned up in a standards-track RFC, and it >>>> should be done with lots of JSON developers and users having >>>> a discussion that comes to rough consensus. >>> >>> One I-D as simple as this hardly justifies a WG. >> >> Getting broad consensus on changing a standard that is >> implemented widely outside the IETF justifies the effort to have >> the time and space for consensus. This is *not* just IETF work. > > > I don't know. I think I'd be fine if we just asked Crockford > (perhaps helped by a willing editor) to do 4627bis and then have > the AD sponsor it on Standards Track. That does seem reasonable, and it carefully sidesteps the all-too-common desire to "improve" a spec... Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRJXv1AAoJEOoGpJErxa2pnSQP/jUuvKCmuXzmPvCWDUlV9wYu 1eyyxjvTxxaXrbL3GCIA8QBTt+LOYn3PMHRg1+hERgMsLC8IQ1Nhb365Zxjhu/xL opCbsRigY9v2JOo/sahI6M4fFs+MFEFAy1lj+cNCIWZN/NpI5PJt3wYmojSeJ2S0 GJG+/afWSxyWPTkCScgr52HEmiNikpTMGRws0fdE0KVWo99pGReI+sAe7BDiVGo5 upVrX8fK4rFclJE6SvZxBYTFKvJzlX6gj5fqEoBfH8DoQhMUQKi7NpjuokITkO2P G+wr3qEGHveMPmAF6wmEI0N+oDw7L+zobzHR62iOUwtRRdJGJtRYOwCkuuObufTI T339IZyPmXAIR2uOiaPBEDG+KvMD8DG778B4pf+E74+tfIZU7lw+GHTQ1fgDX18n vHt7SN3/ggK6NjjrPx3BDoR5cgnJfpGSKyU2jWgloaUsmZqkft1Tq/iQPHdsMiNC 2EHyt+9Q97GIuFgnN67tQfkaSUCbVHTGCjsLJeVwX8h+zbbptOjF6DrIAIx5HVDL jnjG7rgzZhJIc7A7CFD/Rxcn67hx4YZ3TjsrcIFZabcoLPLVAXMVIP5HncVjdroC xu1AjitNv+7gvM9O5JLwZE91gCGro3fkp6W+YMk48Zne8cTtQ3YGC9gPrMqhq5yT 3qFbXKKCJIYQ4pmk0RE5 =0aub -----END PGP SIGNATURE-----
- [Json] Counterproposal on work items Tim Bray
- Re: [Json] Counterproposal on work items Paul Hoffman
- Re: [Json] Counterproposal on work items Matt Miller (mamille2)
- Re: [Json] Counterproposal on work items Gonzalo Salgueiro
- Re: [Json] Counterproposal on work items Mike Jones
- Re: [Json] Counterproposal on work items Tatu Saloranta
- Re: [Json] Counterproposal on work items Nico Williams
- Re: [Json] Counterproposal on work items Tony Hansen
- Re: [Json] Counterproposal on work items Paul Hoffman
- Re: [Json] Counterproposal on work items Joe Hildebrand (jhildebr)
- Re: [Json] Counterproposal on work items Mark Nottingham
- Re: [Json] Counterproposal on work items Tim Bray
- Re: [Json] Counterproposal on work items Peter Saint-Andre
- Re: [Json] Counterproposal on work items Robert Sayre
- Re: [Json] Counterproposal on work items Paul E. Jones
- Re: [Json] Counterproposal on work items Barry Leiba
- Re: [Json] Counterproposal on work items Francis Galiegue
- Re: [Json] Counterproposal on work items Peter Saint-Andre
- Re: [Json] Counterproposal on work items Paul E. Jones
- Re: [Json] Counterproposal on work items Francis Galiegue
- Re: [Json] Counterproposal on work items Carsten Bormann
- Re: [Json] Counterproposal on work items Francis Galiegue
- Re: [Json] Counterproposal on work items Markus Lanthaler
- [Json] What does "break compatibility" mean? Paul Hoffman
- Re: [Json] What does "break compatibility" mean? Tim Bray
- Re: [Json] What does "break compatibility" mean? Paul Hoffman
- Re: [Json] What does "break compatibility" mean? Nico Williams
- Re: [Json] What does "break compatibility" mean? Barry Leiba
- Re: [Json] What does "break compatibility" mean? Paul Hoffman
- Re: [Json] What does "break compatibility" mean? Tim Bray
- Re: [Json] What does "break compatibility" mean? Nico Williams
- Re: [Json] What does "break compatibility" mean? Tatu Saloranta
- Re: [Json] What does "break compatibility" mean? Martin J. Dürst
- Re: [Json] What does "break compatibility" mean? Paul Hoffman