Received-SPF: pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1890:126c::1:1e as permitted sender) client-ip=2001:1890:126c::1:1e;
Date: Wed, 2 Jan 2013 17:43:07 +0000
From: Tony Finch <dot@dotat.at>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
In-Reply-To: <50E4633B.4010604@alum.mit.edu>
Message-ID: <alpine.LSU.2.00.1301021739110.15409@hermes-1.csi.cam.ac.uk>
References: <50DCD850.3020106@alum.mit.edu>
	<alpine.LSU.2.00.1301021022570.15409@hermes-1.csi.cam.ac.uk>
	<50E4633B.4010604@alum.mit.edu>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Cc: abnf-discuss@ietf.org
Subject: Re: [abnf-discuss] Some thoughts about how to make ABNF more
 convenient to use
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: abnf-discuss-bounces@ietf.org
Errors-To: abnf-discuss-bounces@ietf.org

Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 1/2/13 5:29 AM, Tony Finch wrote:
> >
> > xml2rfc understands <artwork type="abnf"> - see section 6.2 of its README.
> > It performs ABNF syntax checks and colourizing, but I don't think it
> > checks for undefined rule names (though I haven't tried it recently).
>
> Wow! Is this documented anywhere?

Here's a link: http://xml.resource.org/authoring/README.html#rfc.section.6.2

If you use xml2rfc you should be aware there is more to it than RFC 2629.
As well as the README there is also a draft update to the base spec,
http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.
_______________________________________________
abnf-discuss mailing list
abnf-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/abnf-discuss