IETF Logo Mail Archive

Re: [Json] Proposal: the minimal edit

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 22 June 2013 17:51 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 E577921F998D for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 10:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level:
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.080, 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 1pRuiZNNlx0H for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 10:51:29 -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 799FC21F9980 for <json@ietf.org>; Sat, 22 Jun 2013 10:51:29 -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 r5MHpRq9084247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Sat, 22 Jun 2013 10:51:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAHBU6ivSG_jYEAzQLnNr+JJXPfMnt9qvhtKyo=HK+38iG_Z3xQ@mail.gmail.com>
Date: Sat, 22 Jun 2013 10:51:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <35B486DC-C401-44A7-8D28-A3A1042B5B20@vpnc.org>
References: <CAChr6SyN4Z3Hh8OFGHkK+AJN0+S09wMfjeobZ51GjKNL+GhPsw@mail.gmail.com> <CAHBU6ivSG_jYEAzQLnNr+JJXPfMnt9qvhtKyo=HK+38iG_Z3xQ@mail.gmail.com>
To: json@ietf.org
X-Mailer: Apple Mail (2.1508)
Subject: Re: [Json] Proposal: the minimal edit
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: Sat, 22 Jun 2013 17:51:30 -0000

<no hat>

On Jun 22, 2013, at 10:48 AM, Tim Bray <tbray@textuality.com> wrote:

> BTW I should say that I have some sympathy with Rob’s viewpoint here.  It looks like it might be hard to get consensus about the nits we want to pick here on 4627, and JSON in the wild works just fine, and the real de facto irritant is that ECMAScript does some non-4627-blessed things.  I’m willing to put some more work into the struggle for consensus, but if we just decided to give up, just add a “Stupid ECMAScript Tricks” section then declare victory, that wouldn’t be a terrible outcome. -T

Certainly +1 to being willing to do the struggle for consensus, but also +1 to a reconsideration of paying more attention to the part of the charter that says "essentially a reclassification in place, with minimal changes".

--Paul Hoffman

v2.46.0 | Report a Bug | By Email | System Status