RE: WSDL and targetNamespace coercion ??

Works for me.

Christopher Ferris
Architect, Emerging e-business Industry Architecture
email: chrisfer@us.ibm.com
phone: +1 508 234 3624

www-ws-desc-request@w3.org wrote on 08/13/2002 12:26:33 PM:

> 
> Thank you.
> 
> "The actual value of the targetNamespace AII of the imported WSDL MUST
> match the actual value of the namespace AII on the import EII"
> 
> This is sufficient.
> 
> Asir
> 
> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On
> Behalf Of Martin Gudgin
> Sent: Tuesday, August 13, 2002 9:45 AM
> To: asirv@webmethods.com; WS-Desc WG (Public)
> Subject: RE: WSDL and targetNamespace coercion ??
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: Asir S Vedamuthu [mailto:asirv@webMethods.com] 
> > Sent: 13 August 2002 14:01
> > To: WS-Desc WG (Public)
> > Subject: WSDL and targetNamespace coercion ??
> > 
> > 
> > 
> > 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?
> 
> I believe it is the intention of the WSDWG that WSDL import work the
> same way as XML Schema import. So targetNamespace coercion is not
> allowed. I propose we add text to the spec along the lines of;
> 
> The actual value of the targetNamespace AII of the imported WSDL MUST
> match the actual value of the namespace AII on the import EII.
> 
> > 
> > [Q2] If WSDL allows target namespace coercion, what are the 
> > processing rules for coercing target namespaces?
> 
> Given answer to Q1, not relevant.
> 
> Hope this helps
> 
> Gudge
> 
> > 
> > Regards,
> > 
> > Asir S Vedamuthu
> > 
> > webMethods, Inc.
> > 703-460-2513 or asirv@webmethods.com
> > http://www.webmethods.com/
> > 
> > 
>