[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: xsl-list Digest 31 Jul 2007 05:10:00 -0000 Issue 1
Dear XSL List,
Michael's response (and David's, earlier) clarifies that my error was not realizing that if I apply <xsl:copy-of> to an element in one namespace in my source document it must emerge in the same namespace in my result document, and setting copy-namespaces="no" cannot prevent this from happening. Using <xsl:element name="{local-name()}"> will do what I want. I think I had mistaken assumed that the name of the element was actually its local name, that the namespace part of its expanded name lived separately in a namespace node, and that by copying the element but not copying the namespace node I could create an element with just the local name. This clarification raises a related naive question, though: What is the proper use of copy-namespaces="no"? What namespace nodes will not be copied as a result of using it, and in what sorts of situations would that be necessary or desirable? Thanks, David ---------------------------------------------------------------------- Date: Mon, 30 Jul 2007 09:01:01 +0100 To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> From: "Michael Kay" <mike@xxxxxxxxxxxx> Subject: RE: getting rid of namespaces Message-ID: <006e01c7d27f$c54e21a0$6401a8c0@turtle>
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|