Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
"Manger, James" <James.H.Manger@team.telstra.com> Thu, 13 March 2014 23:28 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F791A0795 for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 16:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.202
X-Spam-Level:
X-Spam-Status: No, score=-0.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RELAY_IS_203=0.994] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BG0Fuzrt2B71 for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 16:28:03 -0700 (PDT)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by ietfa.amsl.com (Postfix) with ESMTP id C98321A0798 for <json@ietf.org>; Thu, 13 Mar 2014 16:28:02 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.97,650,1389704400"; d="scan'208";a="188682165"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipoavi.tcif.telstra.com.au with ESMTP; 14 Mar 2014 10:27:56 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,7376"; a="260482220"
Received: from wsmsg3752.srv.dir.telstra.com ([172.49.40.173]) by ipcavi.tcif.telstra.com.au with ESMTP; 14 Mar 2014 10:27:55 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3752.srv.dir.telstra.com ([172.49.40.173]) with mapi; Fri, 14 Mar 2014 10:27:55 +1100
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Larry Masinter <masinter@adobe.com>
Date: Fri, 14 Mar 2014 10:27:54 +1100
Thread-Topic: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
Thread-Index: Ac8/D7+DcUOOggBKShuVa/3mAi4zUwAAU/qg
Message-ID: <255B9BB34FB7D647A506DC292726F6E115402F019B@WSMSG3153V.srv.dir.telstra.com>
References: <CAK3OfOj_XQJq-JKAjNdH-GuH0_UwZfeWntgyyizMpTLmSaWQoA@mail.gmail.com> <CAK3OfOio58+1yuxQOcvWep1CADMfE1PVC48XDid0dWvd8=SVjA@mail.gmail.com> <CAOXDeqoYb=NXz4ikMxAg3EHFA+903bFgdpR_BL-K18U2oYriXQ@mail.gmail.com> <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com> <3416a6327a8a4cd3b49bee3c2e548870@BL2PR02MB307.namprd02.prod.outlook.com> <CAK3OfOifggWiLMiTLt8_9rDVd0anrpp+1P2bwvUSJWbaUsVKNQ@mail.gmail.com>
In-Reply-To: <CAK3OfOifggWiLMiTLt8_9rDVd0anrpp+1P2bwvUSJWbaUsVKNQ@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
Archived-At: http://mailarchive.ietf.org/arch/msg/json/F8EZ0JiufwRxG5VrMTBIkpsuiGo
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 13 Mar 2014 23:28:05 -0000
> >> deserving of its own MIME type and so on. > > > > no, not all formats need MIME types. There are infinitely many > formats. > > MIME is one way of noting a file format and distinguishing it from > others, but most applications don't NEED to name the types they accept > and in general, they can't. > > The same argument leads to not needing application/json either. And > yet there it is. > > For HTTP applications an application/json-text-sequence type might > mean that a server could generate N objects one at a time instead of > generating them all into a top-level array then sending that once > built. Sure, it's not hard to build a top-level array in an online > manner, but if you've ever run into an application that doesn't, you > know that there is value in this. > > > I think to justify a new MIME type, you need to provide a concrete > use case that would actually use it and need it. In most of the > content-negotiation scenarios, MIME types are far too course-grained to > express content-features. Media types are cheap aren’t they? I cannot see any reason not to define one while specifying a sequence of JSON values. How about application/jsons it is a bit shorter than application/json-text-sequence; and we can use +jsons as a media type extension if required. -- James Manger
- [Json] Regarding JSON text sequence ambiguities (… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… John Cowan
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… John Cowan
- Re: [Json] Regarding JSON text sequence ambiguiti… Tatu Saloranta
- Re: [Json] Regarding JSON text sequence ambiguiti… Matthew Morley
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Phillip Hallam-Baker
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Matthew Morley
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Phillip Hallam-Baker
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Martin J. Dürst
- Re: [Json] Regarding JSON text sequence ambiguiti… Phillip Hallam-Baker
- Re: [Json] Regarding JSON text sequence ambiguiti… Larry Masinter
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Larry Masinter
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Manger, James
- Re: [Json] Regarding JSON text sequence ambiguiti… Bjoern Hoehrmann
- Re: [Json] Regarding JSON text sequence ambiguiti… Manger, James
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Martin J. Dürst
- Re: [Json] Regarding JSON text sequence ambiguiti… John Cowan
- Re: [Json] Regarding JSON text sequence ambiguiti… Martin J. Dürst
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams