IETF Logo Mail Archive

Re: [Json] First two characters

Carsten Bormann <cabo@tzi.org> Tue, 26 November 2013 14:37 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5418B1AE218 for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 06:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qT-G4kuUJNBP for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 06:37:30 -0800 (PST)
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 E1C301AE211 for <json@ietf.org>; Tue, 26 Nov 2013 06:37:29 -0800 (PST)
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.5/8.14.5) with ESMTP id rAQEbRox015366; Tue, 26 Nov 2013 15:37:27 +0100 (CET)
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 E61395ED; Tue, 26 Nov 2013 15:37:26 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <027801ceeab3$066a5300$133ef900$@lanthaler@gmx.net>
Date: Tue, 26 Nov 2013 15:37:25 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <112F2DBE-7950-4F8E-B585-1024480125B2@tzi.org>
References: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de> <20131122221940.GD3655@localhost> <00a401cee853$777307c0$66591740$@lanthaler@gmx.net> <b8d199h3gr6q4ktihofpqqjguk06rudr59@hive.bjoern.hoehrmann.de> <027801ceeab3$066a5300$133ef900$@lanthaler@gmx.net>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
X-Mailer: Apple Mail (2.1822)
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] First two characters
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Nov 2013 14:37:31 -0000

On 26 Nov 2013, at 15:23, Markus Lanthaler <markus.lanthaler@gmx.net> wrote:

> Could someone please explain how this doesn't break
> existing implementations relying on the fact that valid application/json
> documents are always objects or arrays at the top-level?

No, you can’t.

But given that this was unilaterally changed in the ECMA world already, this breaking change may still be the right thing to do.  (I don’t have a strong opinion either way, but the chairs have found WG consensus to do this.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email