Re: [xsl] multiple documents, namespaces and the same structure

Subject: Re: [xsl] multiple documents, namespaces and the same structure
From: David Carlisle <davidc@xxxxxxxxx>
Date: Wed, 10 Jan 2001 19:13:47 GMT
Equivalent to what you said you had would be


	<xsl:value-of select="."/>
	<xsl:value-of select="@address.type"/>
	<!-- see below <xsl:value-of select="*[local-name(.)='street']"/>-->
	<xsl:value-of select="street"/>


which would work for any namespace as long as the local names were as

but that would seem to produce a strange output.

          <us.address address.type="street"> 
		<street>222 Kearney St.</street> 
		<street>Suite 500</street> 
		<city>San Francisco</city> 
		<state>CA</state><zip main="94108" sub="1234"/> 

your template

<xsl:template name="format.address">
<xsl:param name="address.node"/>
	<xsl:value-of select="$address.node"/>
	<xsl:value-of select="$address.node/@address.type"/>
	<xsl:value-of select="$address.node/street"/>

surely produces

222 Kearney St.Suite 500San FranciscoCAstreet222 Kearney St.Suite 500

As you can see, you can use local-name() to make a template apply to any
namespace, but if these address constructs mean the same thing in
different files why are they in different namespaces? It would be more
in the spirit of the game if you placed common elements in a common

Oh actually you don't get the street name twice, as 
<xsl:value-of select="$address.node/street"/>
presumably never selects anything as there isn't an element street in
the null namespace. it's always in the namespace attatched to (for
example) commercial: 

so your example produces

222 Kearney St.Suite 500San FranciscoCAstreet



This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit

 XSL-List info and archive:

Current Thread