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

Nico Williams <nico@cryptonector.com> Tue, 11 March 2014 19:42 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 2A0FD1A07D7 for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 12:42:29 -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 nTGe2b3mT-Iq for <json@ietfa.amsl.com>; Tue, 11 Mar 2014 12:42:28 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (agjbgdcfdbhd.dreamhost.com [69.163.253.173]) by ietfa.amsl.com (Postfix) with ESMTP id 699041A07D4 for <json@ietf.org>; Tue, 11 Mar 2014 12:42:28 -0700 (PDT)
Received: from homiemail-a67.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTP id C188927BC07B for <json@ietf.org>; Tue, 11 Mar 2014 12:42:22 -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=ROr/U99ZgcUup1UZmlqW 1nHlhdo=; b=G8prDJYH/yaodzI8hQVHtkss5BEyglwECmI1Tzh2YC648AhQyd2a Dd39cTlCits1PSKTAtqTHYsUeoxcZ2VCHAhGXk5qmrH8Qd5A3gwgIPxCOI9s4f28 DB6iO2tyGB/9ooVJXxAlubsLdtdzGRqHx5vlw/MtEaW5r72NFeUaGPM=
Received: from mail-wg0-f41.google.com (mail-wg0-f41.google.com [74.125.82.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a67.g.dreamhost.com (Postfix) with ESMTPSA id 724C827BC06F for <json@ietf.org>; Tue, 11 Mar 2014 12:42:22 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id n12so10668553wgh.12 for <json@ietf.org>; Tue, 11 Mar 2014 12:42:21 -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=FVErEmZVqOKEhlQZXtri1MNpnHm5WzYHC0lcBgMgEjw=; b=V5bV8e+dUoVzX3BSL2BBwL59bNYdAnxClDarzdOV2htZuxheKKk29VQ1NkNteCy2+C HEx7RA+z9tr1p1kalINScEqgG5YTBZH0WRjAs3MFRyPLIsBPuYfCDBJx5c24cccN7ny1 RCYa5D0aoLCitbZAb2mzeEagJr+G0qTt5aylRNRvM8iJwRZxZKUHE2zjec0wIh+HtcXR 2BiCNdXRKfSTqv2A3zLWfjExAJH+XfatcLIg0jWnXy5E2aGwY1UHe1ljHCy5+68S1dwa Pg5+JBT2DXQ2aX3Y20B71kXp4T1OeLAgR6iVEv7xwcMJimHei4Uh1BYv0hydcWIlnEbX VpZQ==
MIME-Version: 1.0
X-Received: by 10.194.84.240 with SMTP id c16mr702wjz.95.1394566941256; Tue, 11 Mar 2014 12:42:21 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Tue, 11 Mar 2014 12:42:21 -0700 (PDT)
In-Reply-To: <CAMm+LwhGbo2twsvhPy2Dde+y8shDcm=ysxL_XtRT53oiC8g7ug@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> <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com> <CAHBU6iuRyRd95Wa_omGS1_T52t+s0AKjWPUW21EAh2ySHuFp=A@mail.gmail.com> <CAMm+LwjRA8x0=zXGRVDy0BqYvyOcEp7=gnUiG4vYOb1RScoyrA@mail.gmail.com> <CAK3OfOj1g_sbnhw9FBCCZtLWsFS5F+aoPX0d5AMkRxQ2fHQi0A@mail.gmail.com> <CAMm+LwhGbo2twsvhPy2Dde+y8shDcm=ysxL_XtRT53oiC8g7ug@mail.gmail.com>
Date: Tue, 11 Mar 2014 14:42:21 -0500
Message-ID: <CAK3OfOiwxebfvtQtbJS6rq-c-RtS=frOWAZ3-6yO5oU1aNysew@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/os6PmsK7u_IAwpX3iw-bim5oYbE
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, Matthew Morley <matt@mpcm.com>, "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 19:42:29 -0000

On Tue, Mar 11, 2014 at 2:19 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> On Tue, Mar 11, 2014 at 2:08 PM, Nico Williams <nico@cryptonector.com>
> wrote:
> The constraint that the objects can't have newlines inside the object will
> require rather more retooling than a requirement that objects be separated
> by commas which is the existing JSON approach.

Actually, that isn't a constraint.  It does help when you have parsers
that don't work incrementally, but you can make do even if the
objects/arrays have embedded newlines.  See my reply to Tim about
that.

Nico
--