[Json] Update to proposed charter to cover listing changes

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 14 March 2013 16:03 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 1D4E511E825F for <json@ietfa.amsl.com>; Thu, 14 Mar 2013 09:03:30 -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 NNNeLyCI4M4o for <json@ietfa.amsl.com>; Thu, 14 Mar 2013 09:03: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 81C0211E825B for <json@ietf.org>; Thu, 14 Mar 2013 09:03:29 -0700 (PDT)
Received: from dhcp-6061.meeting.ietf.org (dhcp-6061.meeting.ietf.org [130.129.96.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r2EG3Rrr097711 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Thu, 14 Mar 2013 09:03:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <5379220D-65A8-4D5B-9502-43DB71417364@vpnc.org>
Date: Thu, 14 Mar 2013 12:03:25 -0400
To: "json@ietf.org" <json@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [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: Thu, 14 Mar 2013 16:03:30 -0000

Greetings again. I have made the following change in the proposed charter (http://trac.tools.ietf.org/wg/appsawg/trac/wiki/JSON):

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.

==>

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?

--Paul Hoffman