Re: [Json] Minimal edit proposal, second round

Bjoern Hoehrmann <derhoermi@gmx.net> Wed, 26 June 2013 17:00 UTC

Return-Path: <derhoermi@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 1C33E21E8122 for <json@ietfa.amsl.com>; Wed, 26 Jun 2013 10:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JE715aF1dQGk for <json@ietfa.amsl.com>; Wed, 26 Jun 2013 09:59:59 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 542E921E8131 for <json@ietf.org>; Wed, 26 Jun 2013 09:59:41 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.4]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MSFoz-1Ug9rj1WrT-00TSnj for <json@ietf.org>; Wed, 26 Jun 2013 18:59:40 +0200
Received: (qmail invoked by alias); 26 Jun 2013 16:59:39 -0000
Received: from p54B4E304.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [84.180.227.4] by mail.gmx.net (mp004) with SMTP; 26 Jun 2013 18:59:39 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18zKQwcVq4zyTPZ75DmJFzDXJhGbsZKS25mg7Crpn C2+zi7Gq1fJVCt
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Date: Wed, 26 Jun 2013 18:59:40 +0200
Message-ID: <1o4ms891gp7n3c28gl19a5djachnlucjeg@hive.bjoern.hoehrmann.de>
References: <6E1C1EF7-3971-4FD4-8BCE-349ED5B0B598@vpnc.org>
In-Reply-To: <6E1C1EF7-3971-4FD4-8BCE-349ED5B0B598@vpnc.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "json@ietf.org WG" <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 17:00:03 -0000

* Paul Hoffman wrote:
>[...]

I think the Working Group should attempt to standardize JSON in one
document that obsoletes RFC 4627. That requires finding a consensus
around issues like whether to allow strings at the top level and if
Unicode signatures are permitted in application/json entities. It'd
be quite unfortunate for the group to decide not to try to do so. I
think the only problem so far was the choice of process that mainly
lead to editorial discussions without providing much insight on the
running code and rough consensus side of the substantive issues.

I think it would be helpful, for instance, to conduct an off-list
straw poll collecting data on where people stand on issues like if
UTF-8 encoded application/json entities may start with `EF BB BF`,
whether `["\uDFFF"]` is ("should be defined as valid") JSON and so
on. Ideally with some data on what implementations and JSON forks
do and corresponding rationale available beforehand. When we have
that, we might find that there is no rough consensus on the issues,
and might decide to do only a minimal bugfix revision, but we are
not there yet.

In http://www.ietf.org/mail-archive/web/json/current/msg00193.html
I said pretty much the same during the chartering discussions.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/