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

"John Levine" <johnl@taugh.com> Fri, 11 October 2013 01:42 UTC

Return-Path: <johnl@iecc.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 F252B21E8181 for <json@ietfa.amsl.com>; Thu, 10 Oct 2013 18:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.293
X-Spam-Level:
X-Spam-Status: No, score=-102.293 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 JOMGmMx3+w3v for <json@ietfa.amsl.com>; Thu, 10 Oct 2013 18:42:06 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA4121E8176 for <json@ietf.org>; Thu, 10 Oct 2013 18:42:05 -0700 (PDT)
Received: (qmail 75006 invoked from network); 11 Oct 2013 01:42:04 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Oct 2013 01:42:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5257576c.xn--i8sz2z.k1309; i=johnl@user.iecc.com; bh=X6dOVlZBAsXuwIlozee4l53UPJLpqWQC4W+JIpBaKlA=; b=BNdk0Gc1oSF9Qkp1L9Ur5tLOlyDgerLuWivJ97kOLqzSQPfOCCOZr3eqSvs0O0zgLc2zx6DMsqlLYZJwoG5xEzgqFkCzGUxy5PmzsNdT+cLPoyK6sR3Alu4wViaJxPXqZ+LazuQc+MdQgbSAGd0Zh1QxOMQQOM8qtwQ5jo8j0Zm8qNDrffhpA3Xh7zwZKe6fRCFLZL2Z0BAowkdRc8BWEzTqZbaYOhcChgEBS6KQuwjVAvwwQ4gLXbaGXxuywkQU
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5257576c.xn--i8sz2z.k1309; olt=johnl@user.iecc.com; bh=X6dOVlZBAsXuwIlozee4l53UPJLpqWQC4W+JIpBaKlA=; b=PX/aRF9BXdm04mnsnIG7RK5LI90kf5irNNE48aai0QcOC8eNcTATbgztjKiFdkJlqDvBd84nuh7IAaKBQbJqOV0zxvjuho/hJ5IqgK0KHIimbQi1qI77R8ktTSRO6PMJnC/dh/b61T7Rkx9y5Vx23GQE5vp9wC207pfTflRF5vua0d62RSidQo6LxuMwDLe//dOoYXuDDfd413bRTg6o+09/mkG30EbLTcX0QWXehqIoC+stELiiVQCsmmOXznEn
Date: 11 Oct 2013 01:41:41 -0000
Message-ID: <20131011014141.15895.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: json@ietf.org
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411EF4E2DB@xmb-aln-x11.cisco.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: mamille2@cisco.com
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 01:42:11 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This draft is ready to publish.  I have a few editorial comments,
none of which I think would be contentious.

Section 1.2 says:

   Object; thus, for example, "Hello world!", "42", and "true" would all
   be valid JSON texts in the ECMAScript 5.1 context.

My guess is that the quotes are intended to be part of "Hello world!"
but not part of 42 or true.  Dunno how to fix that other than perhaps
to display them, e.g.

   Object; thus, for example, these would all
   be valid JSON texts in the ECMAScript 5.1 context:

	"Hello world!"
	42
	true

Please move section 1.4, the list of changes, to the end.  I think
that most people will be more interested in the JSON spec rather
than the minutiae of what's changed.

Section 9 has some upper case MAY and some lower case.  It should
probably be consistent one way or the other.  I realize this is
currently unchanged from 4627.

In section 11, the Published specification should be this document,
not RFC 4627.  Since this is standards track, shouldn't the change
controller now be the IETF?

R's,
John
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.21 (FreeBSD)

iEYEARECAAYFAlJXV2oACgkQkEiFRdeC/kVapgCeIERm3QfwTBxFq5AxTmUpPKQT
85gAniYwpILyl3iYeppy1KW9VhmxINJR
=8rQb
-----END PGP SIGNATURE-----