IETF Logo Mail Archive

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

"Markus Lanthaler" <markus.lanthaler@gmx.net> Sun, 09 June 2013 22:54 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 E70D321F8EC6 for <json@ietfa.amsl.com>; Sun, 9 Jun 2013 15:54:36 -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 d5w-gkW958lK for <json@ietfa.amsl.com>; Sun, 9 Jun 2013 15:54:31 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id DF99321F8EBE for <json@ietf.org>; Sun, 9 Jun 2013 15:54:30 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.34]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M2rdY-1UTre61jL4-00sfP5 for <json@ietf.org>; Mon, 10 Jun 2013 00:54:28 +0200
Received: (qmail invoked by alias); 09 Jun 2013 22:54:28 -0000
Received: from 84-115-182-43.dynamic.surfer.at (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp034) with SMTP; 10 Jun 2013 00:54:28 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1+y8A100/6yGDyyeGwH3eoiTjpGdJPJ6SCTrZSVcH 0YSG/SfR375o9t
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: json@ietf.org
References: <A723FC6ECC552A4D8C8249D9E07425A70FC33B5B@xmb-rcd-x10.cisco.com> <51b23e6d.6196420a.0b15.4245SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SwrveU=fesF8VidDYWzeYMu2c1+=38+__BqHArxTiW5mg@mail.gmail.com> <51b4dbbe.64da440a.1fc2.6dd2SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6Sx_obmG+=sY100ySBLmevN0VJ_0Z9TjYGxcXKOx+UtnJA@mail.gmail.com> <51b4ec44.ea05420a.7c73.ffffa487SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxiZ2Yz6SiozQZpuYoGKSzWnUux6PukyWDkcvKsVyyRbQ@mail.gmail.com>
In-Reply-To: <CAChr6SxiZ2Yz6SiozQZpuYoGKSzWnUux6PukyWDkcvKsVyyRbQ@mail.gmail.com>
Date: Mon, 10 Jun 2013 00:54:18 +0200
Message-ID: <011e01ce6564$46ab75e0$d40261a0$@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: Ac5lVS9F2Zy3VGmoQZudbBaWNbD8ugADtZ3g
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: Sun, 09 Jun 2013 22:54:37 -0000

On Sunday, June 09, 2013 11:06 PM, R S wrote:
>> Why can't a separate media type, e.g., application/json-value,
>> be defined allowing this? 
>
> We could do that, but it might be a bit pointless. It won't change
> the fact that primitive values are already sent as application/json.

Who's doing that?


--
Markus Lanthaler
@markuslanthaler

v2.23.0 | Report a Bug | By Email