Re: [Json] serializing sequences of JSON values

Nico Williams <nico@cryptonector.com> Fri, 14 March 2014 17:04 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 C74F01A018B for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 10:04:57 -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 u8P6RslNhflZ for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 10:04:57 -0700 (PDT)
Received: from homiemail-a102.g.dreamhost.com (mysql.benrbradley.com [69.163.253.146]) by ietfa.amsl.com (Postfix) with ESMTP id 7F1591A01A7 for <json@ietf.org>; Fri, 14 Mar 2014 10:04:48 -0700 (PDT)
Received: from homiemail-a102.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTP id ABC092005D111 for <json@ietf.org>; Fri, 14 Mar 2014 10:04:41 -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=tpws8wKh6Gqv7SN49Hol kmxUZmw=; b=evWdYxWr48se12e5zw2cd5SBp24xq1exaPIX8SPFkG2Mt14Minsc LvAUTpVGtdWRrz4cw32aOp7Yk6I7QnqIiwIZ9N9xaDVgB/ldxxBI2g4X+bD/ModM moAGAgBa5Nn54+NOuiRKwkZDNNPbpkjJkSf0Ib0BZWj7iG9pdyy6WeE=
Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTPSA id 600D02005D10F for <json@ietf.org>; Fri, 14 Mar 2014 10:04:41 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id k14so2421688wgh.35 for <json@ietf.org>; Fri, 14 Mar 2014 10:04:40 -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=7QslmPT8SFGYwiWC0ggUbB7ev2oyvPO3eLitVqM6Ryg=; b=QlLC1tyAtq2fZV1NByQGr94d7trZOI0IUbe+FwBTFxXaJ0it4hQHtC3UgQou7iQHD3 zRm5ml5Nt2D1gdBBpVt3KV9dC7HpIOyklysgw25dWzV+3f0pnkZ3NdoRshWW3hRexyFd jwdA9/GzF8+HBn7J6nRfsqQZrdR4YGTI/g+3ztjlB4Il7O1ATZ/7aVRAUajBbMbBwlfx C4tq/ucqrjyRvtTgeXDzKw1QjFr96vDk7vLLF2IjCIg+w0I2psudz/w6hr9AYN0h5y5t qSrOv/50n6+UDMyW4XfoKQtYwuHLQlq6mkaCw6UI365T6+qkIU3XI5akNWvnSX6HG6uq Qrcw==
MIME-Version: 1.0
X-Received: by 10.194.57.239 with SMTP id l15mr7545571wjq.40.1394816680372; Fri, 14 Mar 2014 10:04:40 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Fri, 14 Mar 2014 10:04:40 -0700 (PDT)
In-Reply-To: <4EDB6664-434E-46B3-9B15-BE1508C3EE2C@tzi.org>
References: <em2c025504-6532-4513-a339-3d71c4cdfbda@helsinki> <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org> <58a4b20f768b484c94a850c4eba71ec5@BL2PR02MB307.namprd02.prod.outlook.com> <53222FFC.8070204@cisco.com> <5322714F.6080508@it.aoyama.ac.jp> <CAGrxA26HRqa+R580qfEMXU_JGid-UDzwwmQigOkOW0OWuA9mpg@mail.gmail.com> <CAK3OfOier6uQ4nVuuCP+uWV+eRbYh8qqAi4FVdWqNLHOh94L+A@mail.gmail.com> <CAGrxA275TwvbUkAT7tp9NtgTDN1WwPNP33aKmAZdB7QJkSY0CA@mail.gmail.com> <CAK3OfOj3e7pqj5R-ggHhXfaN5p1CG+6djiLizaRE2nJnF1ivGA@mail.gmail.com> <CAK3OfOhYxRR1ii3=eezXAmUR1ArpZDmAzbjRdHL2ASQ7Y1deDw@mail.gmail.com> <4EDB6664-434E-46B3-9B15-BE1508C3EE2C@tzi.org>
Date: Fri, 14 Mar 2014 12:04:40 -0500
Message-ID: <CAK3OfOjKobGz_JHLxTgGbCR=Dyg7jbAj9YMZ+OQX8BKHCE+VGw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/uoFMvhc70oB7bPU5rFMuGoEmDUo
Cc: "json@ietf.org" <json@ietf.org>, Tatu Saloranta <tsaloranta@gmail.com>, Matt Miller <mamille2@cisco.com>
Subject: Re: [Json] 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: Fri, 14 Mar 2014 17:04:58 -0000

On Fri, Mar 14, 2014 at 11:48 AM, Carsten Bormann <cabo@tzi.org> wrote:
>> The most interoperable form of JSON text sequence would be this:
>> encoders MUST not use newlines in their JSON text encodings and MUST
>> follow each JSON text with a newline.
>
> +1, and if there is any point in writing this up, we should only write up this most interoperable variant.

Alright, I'll submit an I-D tonight.  As for MIME types, for all those
apps that expose JSON HTTP APIs but which also deal in HTML, using a
client's Accept (and Content-Type) header to distinguish formats...
we'll need a MIME type for JSON text sequences.

Nico
--