IETF Logo Mail Archive

Re: [Json] First two characters

"Markus Lanthaler" <markus.lanthaler@gmx.net> Tue, 26 November 2013 14:23 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 A544D1AE20B for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 06:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, MSGID_MULTIPLE_AT=1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_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 QqjafjTCmp7y for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 06:23:10 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 033F61AE201 for <json@ietf.org>; Tue, 26 Nov 2013 06:23:10 -0800 (PST)
Received: from Vostro3500 ([37.116.127.110]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0M86PB-1VPXVF3RZ3-00vhZm for <json@ietf.org>; Tue, 26 Nov 2013 15:23:09 +0100
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: json@ietf.org
References: <v8av89128j49csd5bb5ba2rqrgschs4c79@hive.bjoern.hoehrmann.de> <20131122221940.GD3655@localhost> <00a401cee853$777307c0$66591740$@lanthaler@gmx.net> <b8d199h3gr6q4ktihofpqqjguk06rudr59@hive.bjoern.hoehrmann.de>
In-Reply-To: <b8d199h3gr6q4ktihofpqqjguk06rudr59@hive.bjoern.hoehrmann.de>
Date: Tue, 26 Nov 2013 15:23:05 +0100
Message-ID: <027801ceeab3$066a5300$133ef900$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac7oVGzDV3JWtdTcT8y6W93pPQgDCgCXmnIQ
Content-Language: de
X-Provags-ID: V03:K0:HjBxg3vMK/3PsvViHyGTObOkTGlzl3zSH5f6M8KJbR7lYkhtC4f 8kAlpZm3o2tfpEcNGRaYcC2zFQ+x9cYkMEpV17B2vQgLHnxqSCHQ9SZdUlQDQl++zaX5Y+K sIN0FDSrcPIwQDLEogCGeXeRcafCQ8SsJI4pMgmnMw4znTmpceXRaG4f5U3fjY5aLEBTsP8 ktwP7hJRhkaxlmHgTL4mQ==
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:23:11 -0000

On Saturday, November 23, 2013 3:01 PM, Bjoern Hoehrmann wrote:
> * Markus Lanthaler wrote:
> >On Fri, Nov 22, 2013 at 07:59:36PM +0100, Bjoern Hoehrmann wrote:
> >>   Now that string literals can occur at the top level, ...
> >
> >Can they? When did we decide that?
> 
> http://www.ietf.org/mail-archive/web/json/current/msg02040.html

Thanks, I missed that. 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?


--
Markus Lanthaler
@markuslanthaler

v2.23.0 | Report a Bug | By Email