W3C home > Mailing lists > Public > www-ws-desc@w3.org > August 2002

Re: WSDL and targetNamespace coercion ??

From: Jacek Kopecky <jacek@systinet.com>
Date: Wed, 21 Aug 2002 00:24:03 +0200 (CEST)
To: Asir S Vedamuthu <asirv@webMethods.com>
cc: "WS-Desc WG (Public)" <www-ws-desc@w3.org>
Message-ID: <Pine.LNX.4.44.0208210018050.26384-100000@mail.idoox.com>

 Hi all,

 I believe the intention of the second import is to import the
XML Schema schema contained in the target WSDL file. So the
meaning of import as understood by authors of the interop WSDL
files is as follows:

 <import namespace="a" location="b"> means that if you encounter 
something in the namespace 'a' and you don't have its definition, 
you can go looking into 'b' and you should find it.

 I don't believe we need allow such "deep import" (importing
something from inside the target document); so then the interop
WSDL set would have to be rewritten to put the schemata in
separate files as well as the definitions.

 Best regards,

                   Jacek Kopecky

                   Senior Architect, Systinet Corporation
                   http://www.systinet.com/



On Tue, 13 Aug 2002, Asir S Vedamuthu wrote:

 > 
 > Hi,
 > 
 > I have two questions that relate to targetNamespace coercion. I will greatly
 > appreciate any input from this group. Let me use an example,
 > 
 > <definitions name="InteropTest" targetNamespace="http://soapinterop.org/"
 >  xmlns="http://schemas.xmlsoap.org/wsdl/"
 >  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
 >  xmlns:tns="http://soapinterop.org/">
 > 
 > 	...
 > 
 >   <!-- IMPORT [1] -->
 >   <import location="http://www.whitemesa.com/interop/InteropTest.wsdl"
 >     namespace="http://soapinterop.org/" />
 > 
 >   <!-- IMPORT [2] -->
 >   <import location="http://www.whitemesa.com/interop/InteropTest.wsdl"
 >     namespace="http://soapinterop.org/xsd" />
 > 
 >   <service name="interopLab">
 >     <port name="interopTestPort" binding="tns:InteropTestSoapBinding">
 >       <soap:address location="http://www.whitemesa.net/interop/std" />
 >     </port>
 >   </service>
 > </definitions>
 > 
 > IMPORT [1] and [2] statements import 2 namespaces into this web service
 > description. However, these 2 statements point to the same location. At a
 > glance, it appears that IMPORT [2] attempts to coerce the namespace from
 > 'http://soapinterop.org/' to 'http://soapinterop.org/xsd'
 > 
 > My two question are,
 > 
 > [Q1] In general, does WSDL allow target namespace coercion?
 > 
 > [Q2] If WSDL allows target namespace coercion, what are the processing rules
 > for coercing target namespaces?
 > 
 > Regards,
 > 
 > Asir S Vedamuthu
 > 
 > webMethods, Inc.
 > 703-460-2513 or asirv@webmethods.com
 > http://www.webmethods.com/
 > 
Received on Tuesday, 20 August 2002 18:24:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:21 GMT