IETF Logo Mail Archive

Re: [Json] Update to proposed charter to cover listing changes

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 16 March 2013 16:43 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 3F5F221F89BA for <json@ietfa.amsl.com>; Sat, 16 Mar 2013 09:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 o9cDH4zM+NDi for <json@ietfa.amsl.com>; Sat, 16 Mar 2013 09:43:31 -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 A5D6221F89A5 for <json@ietf.org>; Sat, 16 Mar 2013 09:43:31 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r2GGhL7w093464 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 16 Mar 2013 09:43:22 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <343B12E966B7596EC5808648@cyrus.local>
Date: Sat, 16 Mar 2013 09:43:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DDE81A65-6B0E-457B-B250-5857AC213E3B@vpnc.org>
References: <5379220D-65A8-4D5B-9502-43DB71417364@vpnc.org> <343B12E966B7596EC5808648@cyrus.local>
To: Cyrus Daboo <cyrus@daboo.name>
X-Mailer: Apple Mail (2.1503)
Cc: json@ietf.org
Subject: Re: [Json] Update to proposed charter to cover listing changes
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: Sat, 16 Mar 2013 16:43:32 -0000

On Mar 15, 2013, at 7:05 AM, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi Paul,
> 
> --On March 14, 2013 12:03:25 PM -0400 Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> 
>> It is acknowledged that there are differences between RFC 4627 and the
>> ECMAScript specification in the rules for parsing JSON. Any changes that
>> break compatibility with existing implementations of either RFC 4627 or
>> the ECMAScript specification will need to have very strong justification
>> and broad support. All differences between RFC 4627 or the current
>> ECMAScript specification will be documented in the new RFC. This
>> documentation will include both the WG consensus for the rationale of the
>> changes and the expected impact of the changes.
>> 
>> Does anyone have a problem with this change?
> 
> This mentions "current ECMAScript specification", yet there was also talk about the "in-progress" v6 ECMAScript spec. Do we have a timeline for when v6 work will be complete? It seems like we would want to base or diffs on that if it is available in a timely fashion.

Yes, I would assume that we would want to have 4627bis detail diffs from v6, even if we have to wait "a reasonable amount of time" for it. If it looks like v6 is going to take more time than that, the WG can decide to make the diffs against v5.1.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email