Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)

Nico Williams <> Thu, 13 March 2014 22:58 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id AF0621A0747 for <>; Thu, 13 Mar 2014 15:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.411
X-Spam-Level: *
X-Spam-Status: No, score=1.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FRT_ADOBE2=2.455, IP_NOT_FRIENDLY=0.334] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QfpA1Ogcgicr for <>; Thu, 13 Mar 2014 15:58:28 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A33B61A06EE for <>; Thu, 13 Mar 2014 15:58:28 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 2C58C674058 for <>; Thu, 13 Mar 2014 15:58:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed;; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type;; bh=b2Fuz2AvONG+Tb2aaN0P arXp4GA=; b=WLBjxu9E9zBopC4FG1IlnIUqQbHFdQ+u2Y3Q2EjF+HOuRNOp3mXm 8VWnYOj98OC8FZ444+MDCRobDiMAP7DSxouipzPsVtClRUVuzrZq+zI5b37XhO9/ q9sSwGiXjyfusDptufVmWophk6WRI6TV9/xSGQ/Nj+opxElvdyxvusA=
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id D4962674059 for <>; Thu, 13 Mar 2014 15:58:21 -0700 (PDT)
Received: by with SMTP id p61so1430349wes.25 for <>; Thu, 13 Mar 2014 15:58:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tqPnT8Hzm9vX89XB02m23IM5Jo2vQN6od+QoyTSzMxI=; b=Ec30bGLI+Jhro864aQYnrRWeVsKAMDrAuicT9M7o2Z33P4elfBt9yVWjZNLUI+ODVU wdr9xCkZk4Ll+jCi17uBwiLDdLJDDN+SE/N9pZvmMmaz9gBl3wnzdfexseT88is64a7S xClxgCbTTT+OU2ivLeyAwcjJj7NHQforvpRdTVoO2h69NPqqw24ewic0aAn1v9nEDI8h hC7BorETK4zpOUozS0ml3Vjh3HjMPMejwny0988tARLvKL1Qs06v1mIdkjaZmLgl4hTU RH31Rg8JIqIIAY7xfkwJ/IpGHFGX7TN+6n5CnYQVu3u0TVNB69OgFaigspKViu+RLW6v MaWA==
MIME-Version: 1.0
X-Received: by with SMTP id q10mr3532850wiw.39.1394751500523; Thu, 13 Mar 2014 15:58:20 -0700 (PDT)
Received: by with HTTP; Thu, 13 Mar 2014 15:58:20 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <>
Date: Thu, 13 Mar 2014 17:58:20 -0500
Message-ID: <>
From: Nico Williams <>
To: Larry Masinter <>
Content-Type: text/plain; charset=UTF-8
Cc: "" <>, Matthew Morley <>, Paul Hoffman <>
Subject: Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Mar 2014 22:58:29 -0000

On Thu, Mar 13, 2014 at 4:39 PM, Larry Masinter <> wrote:
>> Arguably JSON text sequences are a new format,
> yes

It seems we're getting consensus on that much.

>> 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.

A proprietary app I work could use this.  It's a database, queries
return results, as expected, specifically as a top-level array or
results -- each result being roughly like a SQL row.  Actually, it's
an app built out of Rails and Postgresql, of which there are many out
there.  Who knows, it might be trivial to deploy this new format type.