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

Nico Williams <nico@cryptonector.com> Tue, 11 March 2014 23:49 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CB11A0886 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 16:49:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 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, IP_NOT_FRIENDLY=0.334] 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 Z316iay6LdBb for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 16:49:00 -0700 (PDT)
Received: from homiemail-a111.g.dreamhost.com (agjbgdcfdbfa.dreamhost.com [69.163.253.150]) by ietfa.amsl.com (Postfix) with ESMTP id A43211A0857 for <json@ietf.org>; Tue, 11 Mar 2014 16:49:00 -0700 (PDT)
Received: from homiemail-a111.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a111.g.dreamhost.com (Postfix) with ESMTP id E6EA52005D906 for <json@ietf.org>; Tue, 11 Mar 2014 16:48:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=V+FaKa32BwzvExWeTaTJ V7gyBdk=; b=Hh/vHJXkNLlkAR/E4PMszrIYFZfBSGcyroNnLrgcY8vGqGYL//hp qCnee9yvXd03SRXMGuu7o8JSjC1z+A74p4CxZYQ6ZiaV6ChhYT66kx7PHo97RxmH Xqt41S7g3/1ZsLEgzpZ5mrmXW8oPcvi9w1gHVJNlE/RCsLSA42G69dI=
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a111.g.dreamhost.com (Postfix) with ESMTPSA id 8E7AB2005D901 for <json@ietf.org>; Tue, 11 Mar 2014 16:48:53 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id hm4so1642729wib.7 for <json@ietf.org>; Tue, 11 Mar 2014 16:48:52 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vHMlzWZsp7dGgTZZVrVIpfbk5AsZ1tAHNz0BKfez71w=; b=Hw1MwJ/O04P0yGAz0exYM9LsjHnoV70OyU8VWVdGhUw0F7qn9T/gLTv5YoPkeUjfS7 S9TlhaSWeTBr0KXOdsg4AYy9D8YW598Fsg0MLAWKl4JadSbwIuCSf1UhJBZfGkJzyKWa 22RaQ9ZJWVhgi9vRNrXMDeHN/dzd2I6ozGJ/f7ZisqC/v5G/laiA6+2zKrm4ql6wwX3D cH98VEGoDG7eJey18ZFrElZViUXAxXrj9xueafFB5sU2LktYxCQZMJyyCsRXrH56NMbP iWdyTX6k9i/cog0RKApm6AsBxQ+8DEppMtMpTHSso5FU+Zxj8SGFseuXESnoBabPeE1y D/EA==
MIME-Version: 1.0
X-Received: by 10.180.163.206 with SMTP id yk14mr5178640wib.5.1394581732237; Tue, 11 Mar 2014 16:48:52 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Tue, 11 Mar 2014 16:48:52 -0700 (PDT)
In-Reply-To: <20140311230838.GA6812@mercury.ccil.org>
References: <CAK3OfOiNSdC1rAO57yWH5YXpQE6bu2x7T02ejgn0fA7UK99Vow@mail.gmail.com> <20140311230838.GA6812@mercury.ccil.org>
Date: Tue, 11 Mar 2014 18:48:52 -0500
Message-ID: <CAK3OfOicZq_2T3cB-8edsTrZntDw2frn6A9wzq2JR4hQTstz-w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/TalPbjc44StSwcL85Whvb6DeB_s
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [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 23:49:02 -0000

On Tue, Mar 11, 2014 at 6:08 PM, John Cowan <cowan@mercury.ccil.org> wrote:
> Nico Williams scripsit:
>
>> I propose a new Proposed Standard and MIME type describing a "JSON
>> text sequence" as: a sequence of JSON texts separated by newlines.
>
> Since a JSON text is bracketed by optional whitespace, it makes sense
> to me that a JSON text sequence should be also bracketed by optional
> whitespace, with the values separated by mandatory whitespace.
> This is very simple.

Yes, it is.  It has the benefit of ending the perennial debate over
ambiguities created by allowing any value type at the top-level.  In
fact, no ambiguity was created except when JSON texts are expected to
be followed by anything other than EOF (which was never contemplated
by the original, IIUC).  But since "JSON text sequence" is a useful
and _used_ concept, the ambiguity issue does come up, and this is the
best resolution (IMO).

Nico
--