[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: exclude-result-prefixes issue

Subject: RE: exclude-result-prefixes issue
From: "Matt Frank" <mfrank@xxxxxxxxxxx>
Date: Thu, 27 May 2004 14:29:44 -0500
exclude result prefixes
Jim,

I hope my last reply did not come over as being abrasive.  My apologies
if it did.  Let me give a little more detailed explanation.  I work for
an Electronic Marketplace and I am in the process of building an xCBL
document wrapped in a SOAP envelope.  The SOAP envelope I am building is
based off criteria provided by one of our trading partners and
essentially has to be built to their specifications.  So I do not have
much leeway with the namespaces.

Regards,

Matt Frank




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



> 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.

Hi,

I probably didn't phrase myself clearly enough. I think everyone trying
to help has the same understanding that it is critical that the
namespace prefixes get declared somewhere in your output.  The question
is, do you care where in the output other namespaces are declared? If
not, then I think the example I sent earlier ought to work with any
standard XML processor.

> 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 
> =3D "http://schemas.xmlsoap.org/soap/envelope"/> removed.

Would you clarify if you mean the removal of the xmlns:SOAP-ENV
attribute, or if you actually mean the removal of the namespace?  If you
mean the former, and you're using normal XML processors, then I believe
what I posted earlier should do the trick.

If you actually mean 'removal of the namespace' then that would indicate
you don't want to declare the namespace for SOAP-ENV anywhere at all.

The reason for all this confusion, at least on my part, is that I don't
see any reason to declare

<SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body/>
    <MCF-ENV:MCFSOAPHeader
xmlns:MCF-ENV="http://www.MCFmarket.com/soap/"/>
</SOEAP-ENV:Envelope>

instead of


<SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:MCF-ENV="http://www.MCFmarket.com/soap/">
    <SOAP-ENV:Body/>
    <MCF-ENV:MCFSOAPHeader/>
</SOEAP-ENV:Envelope>

because both are supposed to mean the exact same thing to a namespace
aware XML processor.


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

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.