IETF Logo Mail Archive

Re: [Json] Proposal: the minimal edit

Carsten Bormann <cabo@tzi.org> Tue, 25 June 2013 10:19 UTC

Return-Path: <cabo@tzi.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 EC8DF21E8082 for <json@ietfa.amsl.com>; Tue, 25 Jun 2013 03:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, 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 ZRV+mCI-aG8f for <json@ietfa.amsl.com>; Tue, 25 Jun 2013 03:19:25 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id D604621F9EF5 for <json@ietf.org>; Tue, 25 Jun 2013 03:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r5PAJLaK017127; Tue, 25 Jun 2013 12:19:21 +0200 (CEST)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 318B035CA; Tue, 25 Jun 2013 12:19:21 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAChr6SxF694dJJx0DfgZMVCCApJiLreDoqjPTc7yWrTeDOLcUA@mail.gmail.com>
Date: Tue, 25 Jun 2013 12:19:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8411EF3-A79B-489B-8147-3B3EEAB266CE@tzi.org>
References: <20130625032014.GF14060@mercury.ccil.org> <ECAD5568-05F1-44C0-A8E1-6A38DAFAF6D4@vpnc.org> <C75D5BC5-6D5F-4CC0-8ACA-9717E7607DE4@tzi.org> <CAHBU6itPYpcof20YOAhgT82VnMAfgtpH2TaSDX+OHpu__WYjGg@mail.gmail.com> <CFD38719-3EB9-448C-A712-9B0E0B592D30@tzi.org> <CAChr6SxF694dJJx0DfgZMVCCApJiLreDoqjPTc7yWrTeDOLcUA@mail.gmail.com>
To: R S <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Tim Bray <tbray@textuality.com>, John Cowan <cowan@mercury.ccil.org>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposal: the minimal edit
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: Tue, 25 Jun 2013 10:19:31 -0000

On Jun 25, 2013, at 08:36, R S <sayrer@gmail.com> wrote:

>  The crux of the matter is that the JavaScript implementations will not change, and they are material to the success of JSON and this Working Group, so they need to be documented.

I completely agree with the need for documenting the JSON usage that has developed in that community.
We seem to have painted ourselves into a corner a bit by distinguishing the "standard" from a "best practices document", which is likely to cause endless debate which community usage gets documented where.

(The context of my message, however, was the interpretation that there is an ambiguity in RFC 4627 with respect to its Unicode usage, and I was trying to imagine how that interpretation might have been coming to life.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email