RE: [xsl] exclude-result-prefixes issue

["Matt Frank" <mfrank@xxxxxxxxxxx>]

Actually it is critical to declare the other xmlns attributes.  Now
whether I do it at the element or the stylesheet level  does not really
matter to me if there is a way to do it.  I have been toying with
several scenarios but have been unsuccessful getting the exact output I
need.  Right now I am the removal of one namespace away from my desired
result.   

I just need the namespace tied to the <SOAP-ENV:Body xmlns:SOAP-ENV =
"http://schemas.xmlsoap.org/soap/envelope"/> removed.

Regards,

Matt Frank




-----Original Message-----
From: jimr@xxxxxxxxxxxxxxxxxxxxx [mailto:jimr@xxxxxxxxxxxxxxxxxxxxx] 
Sent: Thursday, May 27, 2004 9:30 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] exclude-result-prefixes issue 


On Thu, 27 May 2004 07:22:34 -0700 I wrote:
< 
< > Please disregard my last question.  I have managed to make it a
little < > further.  My problem now is my output looks like < 
< The way I normally generate XHTML is to declare all the important <
namespaces in the xsl:stylesheet, and then just let processor handle <
setting the namespaces in the top element. I don't use <xsl:element>

I'm sorry, I just realized I probably misunderstood your note, thinking
you wanted to drop the xmlns on the individual elements under the root.
But you don't, you want to mix and match, choosing which ones have xmlns
attributes and which don't?  May I ask if it's actually critical for you
to be declaring the other xmlns attributes later on down the line? If
declaring them all at the root somehow won't work for your application?


Jim
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
James A. Robinson                       jim.robinson@xxxxxxxxxxxx
Stanford University HighWire Press      http://highwire.stanford.edu/
650-723-7294 (W) 650-725-9335 (F)