This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: xsl self-documentation - ideas
- To: xsl-list at mulberrytech dot com
- Subject: Re: xsl self-documentation - ideas
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Mon, 26 Jun 2000 17:00:18 +0100 (BST)
- References: <39B19660C174D311BB9000A0C9E01C3F317E90@corfu.rnib.org.uk>
- Reply-To: xsl-list at mulberrytech dot com
OK so I'm completely confused as to the goals!!!
Outline: Design goals.
To be able to extract stylesheet documentation
readily from within a stylesheet.
To be able to use the stylesheet without the documentation
'getting in the way'.
I thought that this was describing a "weave" system that would extract
documentation from a documented source file.
Ie would, in this case, presumably be an XSL stylesheet that takes (just)
the stylesheet being documented as input, and outputs a documented
version of the stylesheet (eg as an html file with lots of links between
the code and documentation)
but starting from that point you then sketched out a process using
xsl:message or extensions to xt:document/saxon:output that would
document/trace the run of the stylesheet when processing a particular
input file.
Both sorts of information are useful, but they are quite distinct
processes aren't they?
David
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list