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

Nico Williams <nico@cryptonector.com> Tue, 11 March 2014 16:45 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 97E971A0763 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 09:45:20 -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 3hGT43k6hqZ8 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 09:45:19 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (agjbgdcfdbfd.dreamhost.com [69.163.253.153]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD6D1A0747 for <json@ietf.org>; Tue, 11 Mar 2014 09:45:19 -0700 (PDT)
Received: from homiemail-a16.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a16.g.dreamhost.com (Postfix) with ESMTP id 011DF50808F for <json@ietf.org>; Tue, 11 Mar 2014 09:45:14 -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=6CJlYqFl7cwez0kewv+m q0V02Rg=; b=Nj8ozPbbNeWe5a1Fnd+yj0pj4Sfe/CmnU/0A8TwLIQ8c0clH7uTM NI9N2b6m95R0qydHk2g+ZvbFLq9m/EYk1pPEIaYuezp1VFtvvzZGIl9OLaL1y7Qo yivexU7ZOHskKHqXUhtJ5jPW6jV5mhGGe6iF3AdyicWIw7MC6fWZWzc=
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (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 A4C7D50805F for <json@ietf.org>; Tue, 11 Mar 2014 09:45:13 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id x13so10362344wgg.33 for <json@ietf.org>; Tue, 11 Mar 2014 09:45:12 -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=S/yOZZS+hdNDCze8a59tW/rX51un7SZ4Jbi+aKgQetY=; b=S8Nbzgj/eVGWygkd8L5H5MlV+DJHo7Bek0bw4dpXMvvjG2T2u7q5frHU2KjSnAY3TH uHjfQwbNoP1DadHs4hsJLOPxXnTs5z/w5dfUjPK4koU+/MyqEIYRgvHuhZGCl+/dUf4b lPLV7oFZftsU/cKUg+RhVCnjVX1YRdp+WDVv0sNEElPwK6k6GxndAYbXond7cSSFPYUM 82Fpk6aAPjLj0DbQd6eOBkYz3/2aeBKWajGQQU0oJrbU2l/fl2NzFxkJ1UhzkhpvuweP EHFmugn3CgNCP8YFYLO8TnmR6QZxEOVJ1JL602Tu55UTx53f/jDyDm5mPO+pY/eEXmAp 558Q==
MIME-Version: 1.0
X-Received: by 10.194.57.140 with SMTP id i12mr37192865wjq.20.1394556312551; Tue, 11 Mar 2014 09:45:12 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Tue, 11 Mar 2014 09:45:12 -0700 (PDT)
In-Reply-To: <CAOXDeqoYb=NXz4ikMxAg3EHFA+903bFgdpR_BL-K18U2oYriXQ@mail.gmail.com>
References: <CAK3OfOj_XQJq-JKAjNdH-GuH0_UwZfeWntgyyizMpTLmSaWQoA@mail.gmail.com> <CAK3OfOio58+1yuxQOcvWep1CADMfE1PVC48XDid0dWvd8=SVjA@mail.gmail.com> <CAOXDeqoYb=NXz4ikMxAg3EHFA+903bFgdpR_BL-K18U2oYriXQ@mail.gmail.com>
Date: Tue, 11 Mar 2014 11:45:12 -0500
Message-ID: <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Matthew Morley <matt@mpcm.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/gi8zfFszJ3pBg_wv15C8JkCELUs
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "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: Tue, 11 Mar 2014 16:45:20 -0000

On Tue, Mar 11, 2014 at 10:31 AM, Matthew Morley <matt@mpcm.com> wrote:
> This issue came up with json-rpc structures and streaming json, which while
> not directly related in that we expect to encounter only objects at the top
> level... having guidance on handling top-level streaming is important for
> json.

Arguably JSON text sequences are a new format, deserving of its own
MIME type and so on.  The change in JSON top-level value syntax didn't
really break JSON text sequencing as a) there were plenty of encoders
and parsers that handled non-array/object top-level values anyways, so
b) the ambiguity already existed.

Maybe we should publish an RFC on JSON text sequences?

Nico
--