Re: [Json] Minimal edit proposal, second round

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 26 June 2013 16:36 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 9176621F9E0D for <json@ietfa.amsl.com>; Wed, 26 Jun 2013 09:36:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level:
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, 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 IRFZh7QEeNLY for <json@ietfa.amsl.com>; Wed, 26 Jun 2013 09:36:33 -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 2799A21F8FC4 for <json@ietf.org>; Wed, 26 Jun 2013 09:36:07 -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 r5QGa1Zf074278 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Jun 2013 09:36:02 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <021c01ce7289$d2a5f2a0$77f1d7e0$@lanthaler@gmx.net>
Date: Wed, 26 Jun 2013 09:36:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A544ACB-39F3-4C85-B5D9-85F3AE429BCD@vpnc.org>
References: <6E1C1EF7-3971-4FD4-8BCE-349ED5B0B598@vpnc.org> <021c01ce7289$d2a5f2a0$77f1d7e0$@lanthaler@gmx.net>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
X-Mailer: Apple Mail (2.1508)
Cc: json@ietf.org
Subject: Re: [Json] Minimal edit proposal, second round
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: Wed, 26 Jun 2013 16:36:33 -0000

<hat on>

On Jun 26, 2013, at 9:25 AM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote:

> On Wednesday, June 26, 2013 5:47 PM, Paul Hoffman wrote:
>> - ECMAScript implementations can generate and consume all code points
>>   in JSON strings, while there is disagreement about whether this
>>   document prohibits some specific code points in JSON strings.
> 
> I'm wondering what the point is of updating the document if things like
> these are not clarified. Why are we not just reclassifying RFC 4627 from
> Informational to Standard and be done then?

Because the WG's charter (<http://datatracker.ietf.org/wg/json/charter/>) requires us to do more:

All differences between RFC 4627 or the current ECMAScript specification will be documented in the new RFC.

--Paul Hoffman