> Thus, in the following document, there is, to my knowledge (such as it is), no
> way to differentiate the two 'spam' elements from different namespaces
> (at least without including enough of the ancestors to get back to a
> qualified global) in an XSL stylesheet.  Am I missing something?

they are not spam from different namespaces. they are both spam elements
that are not in any namespace. If you want to specify a rule for this
spam element when it appears as a child of the test1 namespace, then
something like

<xsl:template match="t1:*//spam">

may surfice, or if you need to protect against t2 elements being nested
in t1 elements, then a slightly more complicated expression involving
namespace-uri(). 

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