[Json] Proposal: JSON text sequence MIME type and Proposed Standard

Nico Williams <nico@cryptonector.com> Tue, 11 March 2014 18:20 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 401771A07A2 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 11:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.944
X-Spam-Status: No, score=-0.944 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, FROM_12LTRDOM=0.1, IP_NOT_FRIENDLY=0.334] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id H14Bhkau1y1O for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 11:20:33 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (agjbgdcfdbfd.dreamhost.com []) by ietfa.amsl.com (Postfix) with ESMTP id 95C7F1A078F for <json@ietf.org>; Tue, 11 Mar 2014 11:20:27 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (localhost []) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTP id 00AE2508084 for <json@ietf.org>; Tue, 11 Mar 2014 11:20:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:date:message-id:subject:from:to:content-type; s= cryptonector.com; bh=zkgJ4QijSBAdu8oxmpZPUpVvs78=; b=SbQShz3kUmc GXtJ+BksS0IRiuToc+aLg5jg12zz9XEZ8Z/Iz0mlI5Bwt7EPc7GRo36R7KXFzvAb fDW5ASfAEaayAwkfzFXOyZA+0X52lIM8bVK1WpoKalR47NYUfpi3hSuZlbSiAcsb QrkKMweZQ4efstlyvVodkdB1P32WRiH4=
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTPSA id A44CE50805F for <json@ietf.org>; Tue, 11 Mar 2014 11:20:21 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi5so1320698wib.11 for <json@ietf.org>; Tue, 11 Mar 2014 11:20:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=fEkJX3GmqeMVe4zWOaRikwyr0t/53xN8NnvsJUsPz3Y=; b=iH7dNJGMtbrtIAHh3S53yruKX+yhwy/QY2gLzOj0y9nXPFbScfh8hfR5JdO+C8WCUP Kmjjqr/Raifnx1hz/3zB96IuCuKd3ozLv/IX40T7N2ee+NApL4ip/+F4LwFMrFyD+4y9 FNLaMb4wphe2JY+FW7ydpbRmSWP9JVsF35g78Fz21jAi5I1s2rn8i7s3USCoKYYmkDmE TAypzM3LVg9pn0H/tfAizwEE8aJasm/AlWkoxZ1OcyTEDoe68XrIUuA27KZIqlebvH+4 2UV7FeK7xQcrfgSaV1u63eOAYrH5osdhTzGwU57jJ4VcJY/s0TgtBb8TiAeek/FyVjFb uk7A==
MIME-Version: 1.0
X-Received: by with SMTP id z13mr2470321wjw.64.1394562020434; Tue, 11 Mar 2014 11:20:20 -0700 (PDT)
Received: by with HTTP; Tue, 11 Mar 2014 11:20:20 -0700 (PDT)
Date: Tue, 11 Mar 2014 13:20:20 -0500
Message-ID: <CAK3OfOiNSdC1rAO57yWH5YXpQE6bu2x7T02ejgn0fA7UK99Vow@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/PpPBNgANxKsmg0nT7qRtF1hBVnI
Subject: [Json] Proposal: JSON text sequence MIME type and Proposed Standard
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: Tue, 11 Mar 2014 18:20:34 -0000

I propose a new Proposed Standard and MIME type describing a "JSON
text sequence" as: a sequence of JSON texts separated by newlines.


 - the newline is REQUIRED when following any of "true", "false",
"null", or any numeric value, otherwise it is RECOMMENDED (but

 - it will be RECOMMENDED that JSON texts written to JSON text
sequences be encoded with no newlines in the encoding.

The need for a newline (or other, but here newline) separator will be
explained (namely: it's needed to disambiguate some cases).

Perhaps (if folks demand it) an option for specifying an alternate
separator in the MIME type will be provided.

That's it.

Given existing use of this, I propose that the WG take this as a work
item, updating the charter to permit it if need be.  I'd volunteer to
edit the I-D.