IETF Logo Mail Archive

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

Vinny A <jsontest@yahoo.com> Fri, 07 June 2013 13:38 UTC

Return-Path: <jsontest@yahoo.com>
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 01FDF21F92E3 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 06:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.264
X-Spam-Level:
X-Spam-Status: No, score=0.264 tagged_above=-999 required=5 tests=[AWL=-1.467, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396]
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 ab7O23RmlrnK for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 06:38:19 -0700 (PDT)
Received: from nm43.bullet.mail.gq1.yahoo.com (nm43.bullet.mail.gq1.yahoo.com [67.195.87.83]) by ietfa.amsl.com (Postfix) with ESMTP id 6B40621F91A3 for <json@ietf.org>; Fri, 7 Jun 2013 06:38:19 -0700 (PDT)
Received: from [98.137.12.189] by nm43.bullet.mail.gq1.yahoo.com with NNFMP; 07 Jun 2013 13:38:18 -0000
Received: from [208.71.42.209] by tm10.bullet.mail.gq1.yahoo.com with NNFMP; 07 Jun 2013 13:38:18 -0000
Received: from [127.0.0.1] by smtp220.mail.gq1.yahoo.com with NNFMP; 07 Jun 2013 13:38:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1370612298; bh=wLx3Ofr/rw2mMcKlYXLCKzjoUEU7+gH4UNJPR43rv8I=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:X-Rocket-Received:References:In-Reply-To:Mime-Version:Content-Type:Content-Transfer-Encoding:Message-Id:Cc:X-Mailer:From:Subject:Date:To; b=bq/Kq3P7G//190Ou0Er6bXS4x/j06NkQeMc4YlUxL2gdhYdNmluxq8srA2JTb6E+d3GdH291NW0P81rRkQiRO1/6ZQoYvY3AQmDZ/IoxJLOiujnJiP8Bt3UnWbzF2L2nhVP3aXHNN9v2TqhHXz1PAtqBvVSjlsTr5B8pjBMnHaE=
X-Yahoo-Newman-Id: 130656.68929.bm@smtp220.mail.gq1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: qyvGwpgVM1l66DL3qtrevuUkPOTZYT.K5EzxhsXOcEbeHvT CEBFiLO6z_YsrbBznKs7XyGdITUrPCpJB1t22tmdEnl01pcZ73Wzpp_lL0FD 4q3c.EW13ho.2rpL8Kbseeunc_aoWNjjmHzZ4vBIN9HAARg9eTyvqus874Er aC0xfchuIwUj3zuFnupCvy9QfmzJB0DfbmxS2SvXiSX95smKLf5bnelAvGNE VIMsWEbKKba6nTTI7k5zdzU18o2nI8JePrRswcinm42QaeUeC9mKAbWKhCQd WnyZSaELRXNgvXyJo6YEUT6ak_NJn3AjiLv_irDlcYHcTRnPausHCeGzTnNN b33kQdyiTm9rgyxYXvYNISvNRDrFPTt4SxdGii55.14ossQeVgk1JzbkQ7US Mo646YsixGsWbMEDBQyne72DHwlSbb85XSB6wW0iqWC8fK800ewqW1uiltgB 2o.FmOTnfvsNWIjQT8ygTGWvdy9aePCaSFwtYT2xDen5zM97kzs38O9kksB. Zc2VkuIGW2lYlEQl17MTBdnZr3A--
X-Yahoo-SMTP: indQcmSswBC8IKsm6t4aCAPskK3T
X-Rocket-Received: from [192.168.10.95] (jsontest@64.134.39.87 with ) by smtp220.mail.gq1.yahoo.com with SMTP; 07 Jun 2013 13:38:17 +0000 UTC
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <A2D3D8F3-1EB3-4CD6-A331-4EDCDB7F9798@tzi.org>
In-Reply-To: <A2D3D8F3-1EB3-4CD6-A331-4EDCDB7F9798@tzi.org>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <A00C1298-57BF-49DE-8486-D6EAB828F833@yahoo.com>
X-Mailer: iPod Mail (9B206)
From: Vinny A <jsontest@yahoo.com>
Date: Fri, 07 Jun 2013 08:38:15 -0500
To: Carsten Bormann <cabo@tzi.org>
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: Fri, 07 Jun 2013 13:38:25 -0000

On Jun 7, 2013, at 3:59 AM, Carsten Bormann <cabo@tzi.org> wrote:
> Apart from auto-detection, one other result is that JSON texts no longer stream.  RFC 4627 texts are self-delimiting, the new ones wouldn't always be.  Of course, if you want to stream sequences of JSON texts, you could always limit those back to arrays or maps

I'm +0 on this topic, partly for Carsten's reason, but also because this looks to be a breaking change.

Do commonly used parsers support top level JSON values?

-----------------
Vinny
www.jsontest.com

v2.23.0 | Report a Bug | By Email