Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: removing spurious namespace declarations on XSLT output

From: "Andy Fish" <ajfish@----------.--.-->
To: NULL
Date: 5/4/2007 9:59:00 AM

the issue is that I don't know what namespace prefix might have been used in 
the source document. in the output document I want to use the same namespace 
I'm using in the stylesheet

I did investigate <xsl:namespace-alias> but I can't see how this would help.


"Joe Kesselman" <keshlam-nospam@c...> wrote in message 
news:kd-dnd6IwcfBf6jbnZ2dnUVZ_rylnZ2d@c......
> Andy Fish wrote:
>> I have used something similar to this technique. unfortunately yours 
>> creates a namespace node on the copied node of the result tree and I 
>> wanted to just use the prefix.
>
> XSLT is namespace-aware. When you copy a node, you copy it with its 
> namespace context, because that's part of the meaning of the node.
>
> If you really want to break namespace-aware behavior, then yes, 
> hand-constructing a new node is one solution. But I strongly suspect that 
> what you're really looking for is
> http://www.w3.org/TR/1999/REC-xslt-19991116#element-namespace-alias
>
>
> -- 
> () ASCII Ribbon Campaign  | Joe Kesselman
> /\ Stamp out HTML e-mail! | System architexture and kinetic poetry 




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent