Re: [Json] Comments on proposed charter for JSON
Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 04 March 2013 19:12 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 17B4E21F8D53 for <json@ietfa.amsl.com>; Mon, 4 Mar 2013 11:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_45=0.6]
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 IgeI7uZgRERI for <json@ietfa.amsl.com>; Mon, 4 Mar 2013 11:12:12 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 420E921F8D73 for <json@ietf.org>; Mon, 4 Mar 2013 11:12:11 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MhgAH-1UQWvR34Hz-00Muls for <json@ietf.org>; Mon, 04 Mar 2013 20:12:10 +0100
Received: (qmail invoked by alias); 04 Mar 2013 19:12:09 -0000
Received: from p5B233557.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [91.35.53.87] by mail.gmx.net (mp028) with SMTP; 04 Mar 2013 20:12:09 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+Wef8TPOSWoQZ38+gSoK0wN2JSRJRORHZeVT3o6/ ZP66kOj3dS/Cs/
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Date: Mon, 04 Mar 2013 20:12:08 +0100
Message-ID: <qrr9j8p8a9ge5tfm2lvn12hg0kn8giq3np@hive.bjoern.hoehrmann.de>
References: <4F511CA8-1FC1-46AF-BC22-C64F2C63C052@vpnc.org> <A723FC6ECC552A4D8C8249D9E07425A70F8AF2FE@xmb-rcd-x10.cisco.com> <CAChr6SxPfxi2r--zKcF2WHPPqSyJ0b01jK2gauE=pHJ4_ZdTCw@mail.gmail.com> <0FD44EC8-2656-4F7B-B5F4-534131061E8B@vpnc.org>
In-Reply-To: <0FD44EC8-2656-4F7B-B5F4-534131061E8B@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
Subject: Re: [Json] Comments on proposed charter for JSON
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: Mon, 04 Mar 2013 19:12:17 -0000
* Paul Hoffman wrote: >I *do* want to see browser folks familiar with the ECMAscript spec to >start working on a specific list of differences between it and RFC 4627. >If y'all can do that before the BoF meeting next week, it will help the >charter discussion. That's already been done in the ecmascript specification: 15.12 The JSON Object The JSON object is a single object that contains two functions, parse and stringify, that are used to parse and construct JSON texts. The JSON Data Interchange Format is described in RFC 4627 <http://www.ietf.org/rfc/rfc4627.txt>. The JSON interchange format used in this specification is exactly that described by RFC 4627 with two exceptions: * The top level JSONText production of the ECMAScript JSON grammar may consist of any JSONValue rather than being restricted to being a JSONObject or a JSONArray as specified by RFC 4627. * Conforming implementations of JSON.parse and JSON.stringify must support the exact interchange format described in this specification without any deletions or extensions to the format. This differs from RFC 4627 which permits a JSON parser to accept non-JSON forms and extensions. See e.g. <http://www.ecma-international.org/ecma-262/5.1/#sec-15.12>. Again, the ecmascript specification defines JSON to explain the behavior of the API, it does not define an on-the-wire format; accordingly issues like those around character encodings are not addressed there. -- 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/
- Re: [Json] Comments on proposed charter for JSON Paul Hoffman
- [Json] Comments on proposed charter for JSON SM
- Re: [Json] Comments on proposed charter for JSON Barry Leiba
- Re: [Json] Comments on proposed charter for JSON Barry Leiba
- Re: [Json] Comments on proposed charter for JSON Peter Saint-Andre
- Re: [Json] Comments on proposed charter for JSON Barry Leiba
- Re: [Json] Comments on proposed charter for JSON Matt Miller (mamille2)
- Re: [Json] Comments on proposed charter for JSON SM
- Re: [Json] Comments on proposed charter for JSON Paul Hoffman
- Re: [Json] Comments on proposed charter for JSON Peter Saint-Andre
- Re: [Json] Comments on proposed charter for JSON Matt Miller (mamille2)
- Re: [Json] Comments on proposed charter for JSON Markus Lanthaler
- Re: [Json] Comments on proposed charter for JSON Joe Hildebrand (jhildebr)
- Re: [Json] Comments on proposed charter for JSON Bjoern Hoehrmann
- Re: [Json] Comments on proposed charter for JSON Robert Sayre
- Re: [Json] Comments on proposed charter for JSON Paul Hoffman
- Re: [Json] Comments on proposed charter for JSON Bjoern Hoehrmann
- Re: [Json] Comments on proposed charter for JSON Paul Hoffman
- Re: [Json] Comments on proposed charter for JSON Bjoern Hoehrmann
- Re: [Json] Comments on proposed charter for JSON Paul Hoffman