IETF Logo Mail Archive

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

Stephan Beal <sgbeal@googlemail.com> Fri, 07 June 2013 13:06 UTC

Return-Path: <sgbeal@googlemail.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 A7D6721F85C3 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 06:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.546
X-Spam-Level:
X-Spam-Status: No, score=-1.546 tagged_above=-999 required=5 tests=[AWL=0.431, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 H9jPzP9qBxSQ for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 06:06:52 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 408BC21F859B for <json@ietf.org>; Fri, 7 Jun 2013 06:06:52 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id n12so1317060wgh.3 for <json@ietf.org>; Fri, 07 Jun 2013 06:06:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mUbJw5FbufStv8d2dokdaqyiMjmkR2WjWRPkhLA65C8=; b=HhhoJBVaVKzGK0+I2a0msp0ebgc4+uFkckZUKK2J8XxoaQT6p4lRST8E1+MhG88oPX ITkFYPWi5ydny36sEE7XMB9GKLfUnquVL6BMKxEZ/Kvd8qHuAWCsQ3/6Yw7wcNWnfRZw B76AZX2rQSkCXKqeDN0T3/daJ2L45i365uo88kEHC66e3C2OA41JJdk94HGaMx+iL0tg RwGCm4QYjwZGbPNEvka5UWgWNPdy78f7lLAGZi/YMsXfFrBGPOFJCx5+d7UitJKmKCk6 +slaPoZF84f0Dng9wu3wJcYtEa2Yfu8e/mMfC5ns7QK+pHrDBLzK6f41zb+38uPiMU2m lzPQ==
MIME-Version: 1.0
X-Received: by 10.194.179.102 with SMTP id df6mr35722545wjc.42.1370610411258; Fri, 07 Jun 2013 06:06:51 -0700 (PDT)
Received: by 10.194.42.230 with HTTP; Fri, 7 Jun 2013 06:06:51 -0700 (PDT)
In-Reply-To: <51b1a644.2988440a.183c.ffff9523SMTPIN_ADDED_BROKEN@mx.google.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <51b1a644.2988440a.183c.ffff9523SMTPIN_ADDED_BROKEN@mx.google.com>
Date: Fri, 07 Jun 2013 15:06:51 +0200
Message-ID: <CAKd4nAjTFa8bnYZRnZmpr=4AG_CbL58rwtjTusnkHu-ARM5ciQ@mail.gmail.com>
From: Stephan Beal <sgbeal@googlemail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: multipart/alternative; boundary="089e01493c34b049ef04de901a95"
Cc: "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:06:54 -0000

On Fri, Jun 7, 2013 at 11:20 AM, Markus Lanthaler
<markus.lanthaler@gmx.net>wrote:

> I'm strictly against this. Not only would it break many implementations but
> also specs build on top of JSON that rely on JSON-text = object / array.
>

+Inf

(even though JSON doesn't support it ;)

-- 
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal

v2.23.0 | Report a Bug | By Email