IETF Logo Mail Archive

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

"Markus Lanthaler" <markus.lanthaler@gmx.net> Fri, 07 June 2013 09:21 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 852E421F9702 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 02:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 5fWFn8cwrcxF for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 02:21:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 29E2E21F965B for <json@ietf.org>; Fri, 7 Jun 2013 02:21:09 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.24]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M7WX3-1UQCiE1wCF-00xKda for <json@ietf.org>; Fri, 07 Jun 2013 11:21:05 +0200
Received: (qmail invoked by alias); 07 Jun 2013 09:21:05 -0000
Received: from 84-115-182-43.dynamic.surfer.at (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp024) with SMTP; 07 Jun 2013 11:21:05 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX18E3uhvlEIEbvfWHiL87V8Bc1Rh+UiRW2VuprqQNn 91D+4EedugQlzv
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: json@ietf.org
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com>
Date: Fri, 07 Jun 2013 11:20:58 +0200
Message-ID: <00d601ce6360$52acce30$f8066a90$@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: Ac5jMj7wK5i9s5prS+2npykXIGILbgALg8dA
Content-Language: de
X-Y-GMX-Trusted: 0
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 09:21:39 -0000

On Friday, June 07, 2013 5:51 AM, Manger, James H wrote:
> I propose allowing a JSON text to be any JSON value.
> 
>    A JSON text is a serialization of any JSON value.
> 
>    JSON-text = value
> 
>    value = false / null / true / object / array / number / string

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.


--
Markus Lanthaler
@markuslanthaler

v2.23.0 | Report a Bug | By Email