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

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

From: "nico at cryptonector.com"
Date: Fri, 23 Jan 2015 17:04:47 -0600
Subject: [rfc-i] v3imp #8 Fragment tagging on sourcecode
In-Reply-To: <E378C876-5217-4274-86B6-1DBFB653DE24@vpnc.org>
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>
Message-ID: <20150123230443.GO2350@localhost>

On Fri, Jan 23, 2015 at 10:39:26AM -0800, Paul Hoffman wrote:
> By "work", I think of "is the solution understandable to a typical
> Internet Draft author", and here things fall apart. It is possible to
> mark artwork as a fragment; it may not be possible to sanely say what
> it is a fragment of. Many RFCs have multiple ABNF modules or ASN.1
> modules, so there would have to be some way to say "this is a fragment
> of that module" *and* say "and the whole goes in this particular
> order".

I'd be happy with a mechanism that collates multiple figures into a
synthetic appendix and which can extract the same.  I'd prefer the
reverse for authoring, but beggars can't be choosers.

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.

Nico
--