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

Allen Wirfs-Brock <allen@wirfs-brock.com> Fri, 11 October 2013 23:21 UTC

Return-Path: <allen@wirfs-brock.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 22C8F11E8194 for <json@ietfa.amsl.com>; Fri, 11 Oct 2013 16:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.638
X-Spam-Level:
X-Spam-Status: No, score=-0.638 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 VnHx64QDHCiU for <json@ietfa.amsl.com>; Fri, 11 Oct 2013 16:21:35 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id C876F11E819A for <json@ietf.org>; Fri, 11 Oct 2013 16:21:33 -0700 (PDT)
Received: from 234.sub-70-210-129.myvzw.com ([70.210.129.234] helo=[10.185.65.103]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.72) (envelope-from <allen@wirfs-brock.com>) id 1VUm1T-000OCc-CS; Fri, 11 Oct 2013 23:21:32 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 70.210.129.234
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18eWYQxLFjgwSm5lZF/lzi2hB1k2LfUASw=
Date: Fri, 11 Oct 2013 16:21:25 -0700
Message-ID: <lkf1yx0p824ir3w7kxdttde9.1381533395741@email.android.com>
From: Allen Wirfs-Brock <allen@wirfs-brock.com>
To: Tim Bray <tbray@textuality.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_1015786545825720"
Cc: JSON WG <json@ietf.org>, Matt Miller <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 23:21:40 -0000

I didn't suggest removing the ABNF. I suggested relabeling it as informative. 



Tim Bray <tbray@textuality.com> wrote:

>Since the normative definitions are isomorphic, there is no benefit to the reader in making them go somewhere else to discover what is already present in this document, and that would be the only effect of removing the syntax specification, especially since there is no intention anywhere that the syntax ever change.  -T
>
>
>
>On Fri, Oct 11, 2013 at 4:00 PM, Allen Wirfs-Brock <allen@wirfs-brock.com> wrote:
>
>We really should avoid having two (Ecma-404 and rfc4627bis) normative syntax specifications for JSON text.  Since it is claimed that the 4627bis ABNF recognizes the same language as that described by the Ecma-404 syntax diagrams it would seem more appropriate for 4627bis to narratively reference Ecma-404 and say that the 4627bis ABNF is an informative restatement of the Ecma-404 syntax specification.
>
>Notational preference really isn't a very good reason to have  two different normative definitions of the same thing.
>
>Allen Wirfs-Brock
>
>_______________________________________________
>json mailing list
>json@ietf.org
>https://www.ietf.org/mailman/listinfo/json
>
>