- From: Richard Tobin <richard@inf.ed.ac.uk>
- Date: Tue, 9 May 2006 13:48:02 +0100 (BST)
- To: Jeni Tennison <jeni@jenitennison.com>, public-xml-processing-model-wg@w3.org
> I don't quite follow what you mean here: When I wrote that message I had been thinking about XSLT's document function, where you can use an XSLT variable to specify the URL, and I forgot that you can't do the same for xsl:import. Norm noticed my mistake on the phone call. Of course there are plenty of other example where the language doesn't allow any kind of variable - Henry's XInclude example is one. So we would need something like > Or perhaps you're suggesting that stylesheet A be generated by another > step that takes the URI for stylesheet B as an input or an XSLT > parameter. [...] > which seems quite laborious. Yes, it is quite laborious. As Henry again pointed out, it would be very useful to have a simple component whose purpose is just to make trivial replacements on documents - something much lighter-weight than XSLT. It's still a bit unwieldy. -- Richard
Received on Tuesday, 9 May 2006 12:48:11 UTC