[rfc-i] v3imp #8 Fragment tagging on sourcecode

nico at cryptonector.com (Nico Williams) Fri, 23 January 2015 23:19 UTC

From: "nico at cryptonector.com"
Date: Fri, 23 Jan 2015 17:19:03 -0600
Subject: [rfc-i] v3imp #8 Fragment tagging on sourcecode
In-Reply-To: <54C2D5F7.30200@alum.mit.edu>
References: <54C20F92.4090400@seantek.com> <54C232FC.1000604@gmx.de> <54C275BC.1040905@alum.mit.edu> <20150123175511.GI2350@localhost> <54C28E3F.4040901@alum.mit.edu> <E378C876-5217-4274-86B6-1DBFB653DE24@vpnc.org> <20150123230443.GO2350@localhost> <54C2D5F7.30200@alum.mit.edu>
Message-ID: <20150123231859.GQ2350@localhost>

On Fri, Jan 23, 2015 at 06:15:03PM -0500, Paul Kyzivat wrote:
> >A mechanism that collates artwork wouldn't be difficult to implement in
> >XSLT...  Just provide an attribute for naming the file/module/appendix/
> >whatever, and an optional attribute for specifying collation order; the
> >XSLT to collate that almost writes itself.
> 
> For ABNF the order doesn't matter, as long as breaks are between
> rules. And in any case, I don't think presenting in the desired
> order is such a burden. But allowing optional sequence numbers on
> fragments might be helpful occasionally.

That's not really generic enough.  What if you have a large rule that
needs to be broken up for discussion?

Anyways, you agree on sequence numbers being optional, which would be my
proposal for this approach.

Nico
--