Re: [abnf-discuss] Core Rules and References for ABNF: draft-seantek-abnf-more-core-rules-07.txt

"John Levine" <johnl@taugh.com> Thu, 29 September 2016 18:50 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2611B12B129 for <abnf-discuss@ietfa.amsl.com>; Thu, 29 Sep 2016 11:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 veHVULpi0NQ6 for <abnf-discuss@ietfa.amsl.com>; Thu, 29 Sep 2016 11:50:06 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8543012B0CE for <abnf-discuss@ietf.org>; Thu, 29 Sep 2016 11:50:05 -0700 (PDT)
Received: (qmail 93362 invoked from network); 29 Sep 2016 18:50:02 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 29 Sep 2016 18:50:02 -0000
Date: Thu, 29 Sep 2016 18:49:42 -0000
Message-ID: <20160929184942.13162.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: abnf-discuss@ietf.org
In-Reply-To: <0946bd36-29a4-0787-8b3f-663549fa2406@seantek.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/m_BJ7EvkrJIA_v2tXSnKFKREzy4>
Cc: dev+ietf@seantek.com
Subject: Re: [abnf-discuss] Core Rules and References for ABNF: draft-seantek-abnf-more-core-rules-07.txt
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "General discussion about tools, activities and capabilities involving the ABNF meta-language" <abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abnf-discuss/>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2016 18:50:09 -0000

>In this draft-07 (and draft-06, which had some typos and unclear parts 
>that have since been addressed), the syntax for a "referenced rule" is 
>rulename@RULEREF, where RULEREF can be a document such as
>
>   URI@[RFC3986]
>
>or a path such as
>
>name-part@<https://raw.githubusercontent.com/antlr/grammars-v4/master/abnf/examples/postal.abnf>

Yuck.  I agree it would be nice to make it easier to automatically collect, syntax check,
and use ABNF, but please don't glop up the text with it.

The IETF has already decided that the RFC format is going to be XML, so put the cross
references in the XML where parsing is trivial (given that it's already parsing the
rest of the XML) and you don't need to invent squidgy text kludges to identify
the various things you want to include.

R's,
John