Re: [Json] Comments on proposed charter for JSON

Robert Sayre <sayrer@gmail.com> Fri, 01 March 2013 20:47 UTC

Return-Path: <sayrer@gmail.com>
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 453E221F8E6C for <json@ietfa.amsl.com>; Fri, 1 Mar 2013 12:47:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 SysArNkLchug for <json@ietfa.amsl.com>; Fri, 1 Mar 2013 12:47:47 -0800 (PST)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by ietfa.amsl.com (Postfix) with ESMTP id 49FEA21F8E69 for <json@ietf.org>; Fri, 1 Mar 2013 12:47:47 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id e12so2829713wge.22 for <json@ietf.org>; Fri, 01 Mar 2013 12:47:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1J3iJR1UaHIcAOavH3sX3A61pLw+f3U0VECMJjj43Gk=; b=hZvCH5EH8lQ2wYQGA+CaddfAPe1CDCLUBqbYgeOuArANVb4fPXHZUa4F2tyHL9uZ/R agaDwejZr0knRmXfSgukVz9vIYwKCnXKoJFmqjq91Wj8TwRxlM71XTZW+ahu+8aMqcj1 9jqeEDO5bqjxP+6UEntB+dNteHwlXyV4deyr4NO0FFJA5z/wf746goM5yZKyFJgYueJ3 Olp89U2ZfXSb3t+2mo/fZrpx/Xjx0QLnuYC7r7LfH+Bz8DxASj36+l4EhWUht3Sk1RYB jhu04hbDKVyDpH+BcZznx1byGD+ZGRoyQ5jHf+EEG0xGhb5FLVywMzIeQptH8xFV4nsh mbQQ==
MIME-Version: 1.0
X-Received: by 10.194.21.233 with SMTP id y9mr13038311wje.47.1362170866402; Fri, 01 Mar 2013 12:47:46 -0800 (PST)
Received: by 10.194.138.170 with HTTP; Fri, 1 Mar 2013 12:47:46 -0800 (PST)
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F8AF2FE@xmb-rcd-x10.cisco.com>
References: <4F511CA8-1FC1-46AF-BC22-C64F2C63C052@vpnc.org> <A723FC6ECC552A4D8C8249D9E07425A70F8AF2FE@xmb-rcd-x10.cisco.com>
Date: Fri, 1 Mar 2013 14:47:46 -0600
Message-ID: <CAChr6SxPfxi2r--zKcF2WHPPqSyJ0b01jK2gauE=pHJ4_ZdTCw@mail.gmail.com>
From: Robert Sayre <sayrer@gmail.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b5d27749d8d6a04d6e31ed5
Cc: Barry Leiba <barryleiba@computer.org>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Comments on proposed charter for JSON
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: Fri, 01 Mar 2013 20:47:48 -0000

On Friday, March 1, 2013, Joe Hildebrand (jhildebr) wrote:

> (individual)
> I'm fine with the text as it currently sits.
>
> (chair)
> Does the current text give anyone heartburn?  I'll start another thread
> mid-next week to make sure.
>
>

I agree with Bjoern that the charter isn't specific enough wrt the delta
between ES5 and the RFC. Adopting the changes in ES5 would seem to be the
best way get consistency.

However, it sounds like some folks on this list would rather standardize a
narrow RFC4267-derived update. I do not think that work would be valuable.

- Rob




>
> On 3/1/13 10:31 AM, "Paul Hoffman" <paul.hoffman@vpnc.org <javascript:;>>
> wrote:
>
> >I made two more small changes to the proposed charter; comments are
> >welcome.
> >
> >- Changed the community review sentence to say "There are also a number
> >of other JSON-related proposals for Standards Track that would benefit
> >from review from both the IETF and the larger JSON-using communities
> >created by a working group focused on JSON" to indicate that we would
> >benefit from JSON-using developers who are currently not active in the
> >IETF.
> >
> >- Changed the "breaking compatibility" sentence to say "Any changes that
> >break compatibility with existing implementations will need to have very
> >strong justification and broad support, and will have to be documented in
> >the new RFC" to make it clear that the resulting RFC should make any
> >changes clear.
> >
> >--Paul Hoffman
> >_______________________________________________
> >json mailing list
> >json@ietf.org <javascript:;>
> >https://www.ietf.org/mailman/listinfo/json
> >
>
>
>
> --
> Joe Hildebrand
>
>
>
> _______________________________________________
> json mailing list
> json@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/json
>