Re: [Json] serializing sequences of JSON values

Phillip Hallam-Baker <hallam@gmail.com> Mon, 10 March 2014 20:39 UTC

Return-Path: <hallam@gmail.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 694E11A049C for <json@ietfa.amsl.com>; Mon, 10 Mar 2014 13:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 c-XVLHqPwvZk for <json@ietfa.amsl.com>; Mon, 10 Mar 2014 13:39:33 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 339901A024B for <json@ietf.org>; Mon, 10 Mar 2014 13:39:32 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id c11so4947154lbj.40 for <json@ietf.org>; Mon, 10 Mar 2014 13:39:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bb+zAa1NBqxx+A+NiTZaCfN3Vu+Tdq9yzMCHkdj0cnk=; b=k5MhGQ0qypnWN5tMYoBRXnWXXIoUq86X5eKBdxHf+NHrGnJJrJRU0OPdJp0te0Em04 94dH5xa0txMQhDoIMKcaLA0KqeR7jkw1phgrOa5c1zyn007xwBNfZNwMW0dPnrokn+Lg dj9/HtHCfcRq+UslrooWkWNF0bDrXQaSb5fYkH7S6diF5/Gv+GBBez7uX9vV1KvNeOuE /FxxtaIOUD8fKQy/c5nZViqUo1xcN3a2rusOV1WVQIbflFE15v2ik86XuF5g2tHMh830 H+o5TmZLZOY9xfle3vHKtTK2M8kFut3cGhLoYqWhpHB14pUoMhppbb1i6n8qxz4A4Pcu G6xg==
MIME-Version: 1.0
X-Received: by 10.152.2.225 with SMTP id 1mr2772647lax.37.1394483966787; Mon, 10 Mar 2014 13:39:26 -0700 (PDT)
Received: by 10.112.37.168 with HTTP; Mon, 10 Mar 2014 13:39:26 -0700 (PDT)
In-Reply-To: <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org>
References: <em2c025504-6532-4513-a339-3d71c4cdfbda@helsinki> <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org>
Date: Mon, 10 Mar 2014 16:39:26 -0400
Message-ID: <CAMm+LwjmBEj3Le7mSuydOV4kKMQm5yF32EiVGp4CyZN_b_h8AQ@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=089e013c61a07c47b904f446996c
Archived-At: http://mailarchive.ietf.org/arch/msg/json/SN7Mqdpl9ZxjGBi6wbbqb1Dwf4A
Cc: "json@ietf.org" <json@ietf.org>
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: Mon, 10 Mar 2014 20:39:35 -0000

On Mon, Mar 10, 2014 at 4:19 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> [ Cutting off the silly Cc list... ]
>
> [ No hat ]
>
> On Mar 10, 2014, at 7:35 PM, Paul E. Jones <paulej@packetizer.com> wrote:
>
> > Why would sequences of objects not be preferred for logging.
>
> Because the log is always open for appending, so the sequence never
> terminates.
>
> This, and many other related topics, were discussed at length earlier on
> the mailing list and the rough consensus was that the current wording was
> sufficient.
>

But the current wording does not support our use case.

I suggest changing the grammar for array as follows,

OLD:

array = begin-array [ value *( value-separator value ) ] end-array


New:

array = begin-array [ array-values ] end-array

array-values = value *( value-separator value )



This makes it easy for a specification that requires a log file to specify
that the contents of the log are a JSON array-values production. A message
oriented protocol would specify that the message contained a value or an
object production as desired.


-- 
Website: http://hallambaker.com/