Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xsl] Forcing a namespace declaration

From: "Michael Kay" <mike@------------>
To:
Date: 5/1/2007 1:59:00 PM
> The problem is I need the http://purl.org/rss/1.0/ xmlns 
> declaration to appear on the root element instead of on the 
> channel element.

It would be nice if you explained why, since it seems a very strange
requirement.

When you do

exclude-result-prefixes="rss1"

you are asking for the namespace that rss1 refers to not to be copied to the
result tree. That's why it isn't being copied. This declaration applies at
the namespace URI level, that is, it affects all namespace bindings for this
namespace URI. 

> Can anyone propose a better solution to this problem than the 
> one I have come up with?

Try  

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
  <xsl:namespace name="">http://purl.org/rss/1.0/</xsl:namespace>
  <channel xmlns="http://purl.org/rss/1.0/">...</channel>
</rdf:RDF>

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: tom tom [mailto:tomxsllist@xxxxxxxxxxx] 
> Sent: 01 May 2007 14:37
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] Forcing a namespace declaration
> 
> Hi all,
> 
> The following XML:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <n xmlns="http://www.test.com" 
> xmlns:xhtml="http://www.w3.org/1999/xhtml"/>
> 
> uses the following XSLT:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet version="2.0" xmlns="http://purl.org/rss/1.0/" 
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
> xmlns:dc="http://purl.org/dc/elements/1.1/" 
> xmlns:rss1="http://purl.org/rss/1.0/" exclude-result-prefixes="rss1" 
> xpath-default-namespace="http://www.test.com">
> 
> 	<xsl:output indent="yes" method="xml"/>
> 
> 	<xsl:template match="n" >
> 		<rdf:RDF xmlns="http://purl.org/rss/1.0/" 
> xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
> 			<channel>fffffff</channel>
> 		</rdf:RDF>
> 	</xsl:template>
> 
> </xsl:stylesheet>
> 
> to generate the following XML:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
>          xmlns:dc="http://purl.org/dc/elements/1.1/">
>    <channel xmlns="http://purl.org/rss/1.0/">fffffff</channel>
> </rdf:RDF>
> 
> I'm using XSLT 2 in Saxon 8.
> 
> The problem is I need the http://purl.org/rss/1.0/ xmlns 
> declaration to appear on the root element instead of on the 
> channel element.
> 
> I believe it is appearing where it is due to the 
> xmlns:rss1="http://purl.org/rss/1.0/" declaration, as when I 
> remove this it works in the way I want it to. The 
> xmlns:rss1="http://purl.org/rss/1.0/" 
> declaration is needed on the root element as elsewhere in the 
> stylesheet I need to process an external document with 
> elements belonging to this namespace.
> 
> The only way I can see to fix this is to have 
> xpath-default-namespace attributes scattered at appropriate 
> points in the stylesheet. As the templates do not separate 
> easily into sections determined by which XML document they 
> are working on i believe this will lead to code that is 
> difficult to read.
> 
> Can anyone explain why http://purl.org/rss/1.0/ is being 
> declared on channel instead of the root element?
> 
> Can anyone propose a better solution to this problem than the 
> one I have come up with?
> 
> Thanks
> 
> Tom
> 
> _________________________________________________________________
> Get Hotmail, News, Sport and Entertainment from MSN on your mobile.  
> http://www.msn.txt4content.com/


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