Re: [Json] REMINDER - WGLC Ends 2013-10-11

"Jim Schaad" <ietf@augustcellars.com> Fri, 11 October 2013 21:08 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB6321F9BD0 for <json@ietfa.amsl.com>; Fri, 11 Oct 2013 14:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7fEhDLf7cXql for <json@ietfa.amsl.com>; Fri, 11 Oct 2013 14:08:12 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 825C221F9B86 for <json@ietf.org>; Fri, 11 Oct 2013 14:08:11 -0700 (PDT)
Received: from Philemon (173-12-183-193-oregon.hfc.comcastbusiness.net [173.12.183.193]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 4B71238F03 for <json@ietf.org>; Fri, 11 Oct 2013 14:08:11 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'JSON WG'" <json@ietf.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF4E2DB@xmb-aln-x11.cisco.com>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411EF4E2DB@xmb-aln-x11.cisco.com>
Date: Fri, 11 Oct 2013 14:06:38 -0700
Message-ID: <078c01cec6c5$d19fc990$74df5cb0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJeM09fUXFhQoCp/b4kH1REUE6vypjRHpHQ
Content-Language: en-us
Subject: Re: [Json] REMINDER - WGLC Ends 2013-10-11
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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, 11 Oct 2013 21:08:18 -0000

Nothing earth shattering, I think the document can progress.  A few small
comments that might duplicate others peoples comments.  I am not wedded to
any of the comments, ignore if you don't care for them.

Jim


1.  It seems odd in Section 1 that a value is defined for object, but it is
not for array.  It might be better to move the definition of value in the
paragraph of what JSON can represent so it does not appear to be special for
object.

2.  In section 1.2, My reading of the following text ||"Hello world!", "42",
and "true"|| is that there are three strings here, but I think it was
supposed to represent a string, an number and a Boolean.  I am not sure how
to make this clearer, but killing the quotes on the last two items might be
reasonable.

3.  It seems a bit odd to title section 2 "Grammar" when it does not have
the entire grammar.  It also seems odd that the introduction paragraph talks
about things which are not in this section, but are in the following
sections.

4.  The following is technically a change in the grammar, however is there a
reason why an integer cannot be 00, but 1E00 is legal?  Do we want to change
the definition of the exponent so that it matches that of integer?

5.  There has been mention that one reason for using ABNF is that it can be
machine consumable, does it make any sense to create an appendix which has
the full grammar in it for simplicity of reference?