IETF Logo Mail Archive

Re: [Json] Encoding

Bjoern Hoehrmann <derhoermi@gmx.net> Thu, 06 June 2013 09:55 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 B9F8721F973A for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 02:55:59 -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 TpCkczEX2iIz for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 02:55:55 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 140AD21F96ED for <json@ietf.org>; Thu, 6 Jun 2013 02:55:49 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.31]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M7WSv-1UQVT13xfL-00xJ6C for <json@ietf.org>; Thu, 06 Jun 2013 11:55:48 +0200
Received: (qmail invoked by alias); 06 Jun 2013 09:55:48 -0000
Received: from p5B2318C1.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [91.35.24.193] by mail.gmx.net (mp031) with SMTP; 06 Jun 2013 11:55:48 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/S0JJy0xfSKBQY7hXv3R1t2GE2eyKvP81zE0t0K+ svufzsWxBM27v/
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Douglas Crockford <douglas@crockford.com>
Date: Thu, 06 Jun 2013 11:55:50 +0200
Message-ID: <lam0r8lpdq4grthrnp5p1tv9g4k6r0kd9n@hive.bjoern.hoehrmann.de>
References: <51AF8575.5060706@crockford.com>
In-Reply-To: <51AF8575.5060706@crockford.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
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Encoding
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: Thu, 06 Jun 2013 09:55:59 -0000

* Douglas Crockford wrote:
>I think the section on encoding is not saying anything useful and should 
>be completely removed.

The specification has to define how to handle resources such as

  <data:application/json,%00%5B%00%31%00%5D>

which RFC 4627 defines to be a properly formed application/json resource
consisting of an array with the number `1` as only element and there are
quite a number of implementations that treat it as such. Same goes for

  <data:application/json,%EF%BB%BF%5B%31%5D>

which RFC 4627 defines to be malformed junk, but many implementations do
treat it as an array with the number `1` as only element.

Removing the whole Encoding section without replacement would make it a
lot less clear how to handle cases like the two above, so that is not an
option.
-- 
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/

v2.23.0 | Report a Bug | By Email