Re: [Json] New JSON Text Sequence I-D submitted

Nico Williams <nico@cryptonector.com> Tue, 29 April 2014 04:29 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 C67271A08AE for <json@ietfa.amsl.com>; Mon, 28 Apr 2014 21:29:22 -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 DV0uM9SoZlWF for <json@ietfa.amsl.com>; Mon, 28 Apr 2014 21:29:22 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 072371A08AD for <json@ietf.org>; Mon, 28 Apr 2014 21:29:22 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id 346F3594059 for <json@ietf.org>; Mon, 28 Apr 2014 21:29:21 -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:content-transfer-encoding; s= cryptonector.com; bh=2FlNARO1KZHQiUeyF19y0qA9/ow=; b=u1ZVYRvYo4T ryka5wcNDd8t5RD/tkjsWagiMaA+/hOJluFXq6S76UqTmv2kCdfG4lExKURrrjGe STdco3vhzXTvq2vVq3PvCLDIek5jGvbtR5NjwmrCU1iK6q9g7VDObz4/czjI9DBb Yt107lE8uFwin/DxVhsqUGZYpph42Cyk=
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPSA id DD4DA594058 for <json@ietf.org>; Mon, 28 Apr 2014 21:29:20 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id cc10so6704907wib.16 for <json@ietf.org>; Mon, 28 Apr 2014 21:29:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.188.41 with SMTP id fx9mr253485wjc.56.1398745759885; Mon, 28 Apr 2014 21:29:19 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Mon, 28 Apr 2014 21:29:19 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E115456D2132@WSMSG3153V.srv.dir.telstra.com>
References: <CAK3OfOgLJDEFK_K16WhX9dm21a25r7Wr4EmZcqbGa7CLdqYWGw@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E115456D2132@WSMSG3153V.srv.dir.telstra.com>
Date: Mon, 28 Apr 2014 23:29:19 -0500
Message-ID: <CAK3OfOgcN1riVTw6SN-OjgH4WntnCOVXC7pEf3K+NLGHBh4KTw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Manger, James" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/eJUgGwxzl_dzoh2mIogH27l7paU
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] New JSON Text Sequence I-D submitted
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, 29 Apr 2014 04:29:23 -0000

On Mon, Apr 28, 2014 at 7:41 PM, Manger, James
<James.H.Manger@team.telstra.com> wrote:
>> https://datatracker.ietf.org/doc/draft-ietf-json-text-sequence/
>
> Short & simple — looks good.

Thanks.

> 1.
> One missing feature is that a file containing only whitespace should be a valid JSON text sequence. Suggested changes:

I think that's implied, but I'll make that explicit.

> FROM:  JSON-sequence = *(JSON-text 1*(ws))
> TO  :  JSON-sequence = *(ws) *(JSON-text 1*(ws))

OK.

> P.S. Do you need the brackets in *(ws)?

No, I didn't.

> FROM:  A JSON text sequence is a sequence of JSON texts
> TO  :  A JSON text sequence is a sequence of zero, one, or more JSON texts

Sure.

> 2.
> We can't have a <ws> ABNF production that is different from RFC7159 JSON. ws in JSON is unfortunate, but we have to live with it.
> json-seq:  ws =    %x20 / %x09 / %x0A / %x0D
> json    :  ws = *( %x20 / %x09 / %x0A / %x0D )
>
> I would be tempted to write the ABNF using <value>, instead of <JSON-text>.
>
>   JSON-sequence = *whitespace *(value 1*whitespace)
>   whitespace = %x20 / %x09 / %x0A / %x0D
>   value = <given by RFC7159>

Good point.  Though to be fair I don't think the RFC7159 ABNF should
be commingled with this one...

Nico
--