IETF Logo Mail Archive

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

"Manger, James H" <James.H.Manger@team.telstra.com> Sat, 08 June 2013 13:25 UTC

Return-Path: <James.H.Manger@team.telstra.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 6F31721F96B1 for <json@ietfa.amsl.com>; Sat, 8 Jun 2013 06:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.579
X-Spam-Level:
X-Spam-Status: No, score=-0.579 tagged_above=-999 required=5 tests=[AWL=0.322, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 8+dIUG3vAQqd for <json@ietfa.amsl.com>; Sat, 8 Jun 2013 06:25:06 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by ietfa.amsl.com (Postfix) with ESMTP id 0409521F9643 for <json@ietf.org>; Sat, 8 Jun 2013 06:25:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,827,1363093200"; d="scan'208";a="133110946"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipobni.tcif.telstra.com.au with ESMTP; 08 Jun 2013 23:25:05 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7099"; a="138672031"
Received: from wsmsg3703.srv.dir.telstra.com ([172.49.40.171]) by ipcbni.tcif.telstra.com.au with ESMTP; 08 Jun 2013 23:25:05 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3703.srv.dir.telstra.com ([172.49.40.171]) with mapi; Sat, 8 Jun 2013 23:25:04 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Tim Bray <tbray@textuality.com>
Date: Sat, 08 Jun 2013 23:25:03 +1000
Thread-Topic: [Json] Allow any JSON value at the top level
Thread-Index: Ac5jl7EksTMOj9LdR/KAilE/VKtNzQAsJuOA
Message-ID: <255B9BB34FB7D647A506DC292726F6E1151B21FF62@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <CAHBU6isXinTGstEDtagsvTufaQDQ=W1K06sn5EFSAzkNuQrZAg@mail.gmail.com>
In-Reply-To: <CAHBU6isXinTGstEDtagsvTufaQDQ=W1K06sn5EFSAzkNuQrZAg@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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: Sat, 08 Jun 2013 13:25:12 -0000

>> I propose allowing a JSON text to be any JSON value.

Tim Bray said:
> 2. This is a bad idea in general and a terrible idea for network
> protocols, which is where JSON is most valuable.


Tim, could you expand on why this is bad and terrible?

I would have thought an HTTP request like this would be a reasonable design, and shouldn't require a new media type to be minted:

-> GET /path/to/resource.json?part=json-pointer

<- Content-Type: application/json
   <JSON value selected by JSON pointer in request>

--
James Manger

v2.23.0 | Report a Bug | By Email