Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Theoretical question about namespaces

From: "Anthony Jones" <Ant@------------.--->
To: NULL
Date: 5/9/2006 2:33:00 PM


"Y. Sforza" <sforza@s...> wrote in message
news:1147175994.416089.14750@g......
> According to xslt specs it is an error when you produce xml element
> which name has unknown prefix (i.e. no namespace is bound to that
> prefix).
> Well, let's imagine some legacy application (created before namespaces
> were introduced) which uses xml in namespace-unaware fashion but uses
> prefixed names. For example smth like
> <x:dummy/>
> Is it possible to generate such a xml (with prefixed name, but no
> namespace) using xslt 1.0?
> Afaik, the only way to do this is to use <xsl:text> with disabled
> output escaping.
> Are there more ellegant workarounds or tricks?
>

Invent a namespace for x, perhaps?
Hopefully the non-conformant app will simply ignore the
xmlns:x="urn:tempuri.org:imadethisup"  in the xml.
If not it would better to simple post-process the output xml to strip it
off.

Anthony.




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