Re: [Json] [apps-discuss] JSON mailing list and BoF

Bjoern Hoehrmann <derhoermi@gmx.net> Tue, 19 February 2013 00:26 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 9512621E804B for <json@ietfa.amsl.com>; Mon, 18 Feb 2013 16:26:38 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCop1cfHggup for <json@ietfa.amsl.com>; Mon, 18 Feb 2013 16:26:38 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id B2D7A21E8039 for <json@ietf.org>; Mon, 18 Feb 2013 16:26:37 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.27]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Mh7vz-1UTosv2ED3-00MHfp for <json@ietf.org>; Tue, 19 Feb 2013 01:26:36 +0100
Received: (qmail invoked by alias); 19 Feb 2013 00:26:36 -0000
Received: from p54B4E14B.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [84.180.225.75] by mail.gmx.net (mp027) with SMTP; 19 Feb 2013 01:26:36 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19YkEZcy7pYmF/kh176LU5qupG38vwm9DtFxPbiQu czS6uFbzJ6nWGL
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Date: Tue, 19 Feb 2013 01:26:37 +0100
Message-ID: <1ah5i81al3ug4qgmgjqgjnl5evf6jc1qnq@hive.bjoern.hoehrmann.de>
References: <A723FC6ECC552A4D8C8249D9E07425A70F8943CC@xmb-rcd-x10.cisco.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F8943CC@xmb-rcd-x10.cisco.com>
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
X-Mailman-Approved-At: Mon, 18 Feb 2013 21:42:26 -0800
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
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: Tue, 19 Feb 2013 00:26:38 -0000

* Joe Hildebrand (jhildebr) wrote:
>As a start, we know there are a couple of things we'd like to fix about
>RFC 4627:
>
>- move to standards track
>- an ABNF indentation typo in section 2.2
>- change SHOULD to MUST for the uniqueness of names in an object
>
>A *very* important goal would be to minimize change, and to ensure strict
>backward-compatibility.

A Working Group will also likely have to look at revising the rules to
detect the character encoding in application/json resources (there is a
lack of consensus whether to auto-detect UTF-32 and whether to honour a
Unicode signature, whether to support UTF-32 when it is detected, and so
on, partly due to how people load JSON resources; a generic "load text"
API for instance might detect and remove a Unicode signature before the
data is passed to a JSON parser; this used to be true for XMLHttpRequest
for instance, I haven't checked the current situation there though).
-- 
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/