Re: [Json] Minimal edit proposal, second round

"Markus Lanthaler" <markus.lanthaler@gmx.net> Wed, 26 June 2013 16:26 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 DAFFE21E80C0 for <json@ietfa.amsl.com>; Wed, 26 Jun 2013 09:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 SYqBQqniJiYq for <json@ietfa.amsl.com>; Wed, 26 Jun 2013 09:25:55 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 685B121E80BB for <json@ietf.org>; Wed, 26 Jun 2013 09:25:53 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.12]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MSoaR-1Uk0L40A57-00Roc1 for <json@ietf.org>; Wed, 26 Jun 2013 18:25:51 +0200
Received: (qmail invoked by alias); 26 Jun 2013 16:25:50 -0000
Received: from 84-115-182-43.dynamic.surfer.at (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp012) with SMTP; 26 Jun 2013 18:25:50 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1+jIEEQxQejZBZM3QE86OXEShz8eUS0+KlP4ng5mY Mg5XQIpKnxlB/h
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: json@ietf.org
References: <6E1C1EF7-3971-4FD4-8BCE-349ED5B0B598@vpnc.org>
In-Reply-To: <6E1C1EF7-3971-4FD4-8BCE-349ED5B0B598@vpnc.org>
Date: Wed, 26 Jun 2013 18:25:50 +0200
Message-ID: <021c01ce7289$d2a5f2a0$77f1d7e0$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac5yhHjn84y6iY8ZT1aEcOAOVH9BIwABIcaQ
Content-Language: de
X-Y-GMX-Trusted: 0
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:26:09 -0000

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? Apparently the RFC has been good
enough to make JSON one of the most widely adopted data formats.



--
Markus Lanthaler
@markuslanthaler