This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: the problem with include and import
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Mon, 7 Jan 2002 12:36:51 GMT
- Subject: Re: [xsl] the problem with include and import
- References: <F33ODUNWUR584vovDLm00000385@hotmail.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> (such as overriding matches, if I'm not mistaken).
ues matches (and keys) I meant the whole point of xsl:import is to allow
the importing stylesheet to override the imported one.
The behaviour of variable definitions is just a consequence of that,
so I fail to see why it is seen as a problem rather than a feature.
> Anyhow, what I was proposing was
> an *option* to supply a namespace for the imported templates.
I don't see how that would work. Everywhere in xpath/xslt a namespace
is just an integral part of a name not some dynamic construct that can
be changed on the fly. Changing a qname from namespace a to namespace B
is no different from changing its local name. the "name" just consists
of a pair of strings, the uri and a local name.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list