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;
Message-ID: <50E5D4C5.8010800@alum.mit.edu>
Date: Thu, 03 Jan 2013 13:58:13 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
	rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: abnf-discuss@ietf.org
References: <20130103171755.20983.75939.idtracker@ietfa.amsl.com>
	<50E5BF59.9000207@alum.mit.edu>
In-Reply-To: <50E5BF59.9000207@alum.mit.edu>
Subject: Re: [abnf-discuss] A proposal for adding import and scopping to ABNF
Precedence: list
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: abnf-discuss-bounces@ietf.org
Errors-To: abnf-discuss-bounces@ietf.org

One thing I forgot to mention in this draft:

While <artwork type='abnf'> can serve as the means to extract the ABNF, 
that is only so if the xml format is available the referenced 
draft/rfc/etc. With drafts it will be available if submitted. But at the 
moment it isn't available for RFCs.

Of course it need not be xml. It could be some other format that also 
supports the tagging.

This keys into the rfc-interest discussion of document formats.

	Thanks,
	Paul

On 1/3/13 12:26 PM, Paul Kyzivat wrote:
> OK. Having sized up the current state of things, I will float a first
> cut proposal for adding import and scoping. Announcement of draft attached.
>
> This is very definitely just a strawman to stimulate discussion.
> There are many ways to skin this cat.
>
> This proposal will complicate identification of rule starts with the
> extension that Tony just proposed. But I think it is still possible -
> just requires more look-ahead.
>
>      Thanks,
>      Paul
>
>
> -------- Original Message --------
> Subject: New Version Notification for draft-kyzivat-abnf-import-00.txt
> Date: Thu, 03 Jan 2013 09:17:55 -0800
> From: internet-drafts@ietf.org
> To: pkyzivat@alum.mit.edu
>
>
> A new version of I-D, draft-kyzivat-abnf-import-00.txt
> has been successfully submitted by Paul Kyzivat and posted to the
> IETF repository.
>
> Filename:     draft-kyzivat-abnf-import
> Revision:     00
> Title:         ABNF Extensions for Importing and Scoping
> Creation date:     2013-01-03
> WG ID:         Individual Submission
> Number of pages: 5
> URL: http://www.ietf.org/internet-drafts/draft-kyzivat-abnf-import-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-kyzivat-abnf-import
> Htmlized:        http://tools.ietf.org/html/draft-kyzivat-abnf-import-00
>
>
> Abstract:
>     This document proposes extensions to the ABNF defined in [RFC5234] to
>     support importation of ABNF from other documents, and multiple naming
>     scopes for rulenames.
>
>
>
>
>
> The IETF Secretariat
>
>
>
>
> _______________________________________________
> abnf-discuss mailing list
> abnf-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/abnf-discuss
>

_______________________________________________
abnf-discuss mailing list
abnf-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/abnf-discuss