IETF Logo Mail Archive

Re: [Json] Allow any JSON value at the top level

Carsten Bormann <cabo@tzi.org> Tue, 11 June 2013 09:25 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 BB34121F960D for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 02:25:55 -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 fKsFIYybzSkV for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 02:25:40 -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 A4E6D21F9619 for <json@ietf.org>; Tue, 11 Jun 2013 02:25:39 -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 r5B9PatC029676; Tue, 11 Jun 2013 11:25:36 +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 96CA13260; Tue, 11 Jun 2013 11:25:36 +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: <CAGrxA27z-tqgKWcyKNc7ojoUi3Z==hReETrddfYMVxTfVEAhhQ@mail.gmail.com>
Date: Tue, 11 Jun 2013 11:25:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA9A52D2-6956-4E6C-AE96-7F1C05AE3E57@tzi.org>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <A2D3D8F3-1EB3-4CD6-A331-4EDCDB7F9798@tzi.org> <CAGrxA27z-tqgKWcyKNc7ojoUi3Z==hReETrddfYMVxTfVEAhhQ@mail.gmail.com>
To: Tatu Saloranta <tsaloranta@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Allow any JSON value at the top level
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, 11 Jun 2013 09:25:56 -0000

On Jun 7, 2013, at 19:54, Tatu Saloranta <tsaloranta@gmail.com> wrote:

>> Apart from the (intellectually nicely challenging, but practically irrelevant) auto-detection thing,
> 
> Irrelevant based on what? I thought this is what any half-decent JSON parser did; unless platform does not expose byte sequence as input, case for some scripting languages.
> I have written multiple parsers (json, xml) that do just this, and know that others exist as well.

It is true that there are parsers that implement autodetection.
Lots of code is written that is then never exercised.

> I don't know what leads to assumption of irrelevancy here, and it should be fully spelled out.

This is irrelevant in practice as JSON is used with UTF-8 in practice.

The main job that the text in section 3 seems to do is to convince people not to send a BOM in front of their UTF-8 JSON.  Now that is a good thing...  Unfortunately, some JSON parsers have been "fixed" to accept BOMs.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email