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

Re: WSDL and targetNamespace coercion ??

From: Prasad Yendluri <pyendluri@webmethods.com>
Date: Tue, 13 Aug 2002 16:43:18 -0700
Message-ID: <3D599995.435ECB2C@webmethods.com>
To: asirv@webmethods.com
CC: Martin Gudgin <mgudgin@microsoft.com>, "WS-Desc WG (Public)" <www-ws-desc@w3.org>

This seems to be an undesirable restriction to me. One should be able to
organize different entities in the namespace domain as appropriate and
import them into higher level WSDL as needed.

E.g. Section "2.1.2 Authoring Style" of  http://www.w3.org/TR/wsdl shows a
way for one to accomplish that. I think this would be useful when people
want to share the same set of definitions with related Web services or Web
services that offer more comprehensive functionality than an existing one
etc. E.g. a Buyer and a Seller service both may need to deal with Purchase
order and may want to share the type definition of the PO. Same PO schema
might be used with different types of Web services etc..

Regards, Prasad

-------- Original Message --------
Subject: RE: WSDL and targetNamespace coercion ??
Resent-Date: Tue, 13 Aug 2002 12:27:26 -0400 (EDT)
Resent-From: www-ws-desc@w3.org
Date: Tue, 13 Aug 2002 12:26:33 -0400
From: "Asir S Vedamuthu" <asirv@webmethods.com>
Reply-To: <asirv@webmethods.com>
To: "Martin Gudgin" <mgudgin@microsoft.com>,"WS-Desc WG \(Public\)"

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.


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


> Regards,
> Asir S Vedamuthu
> webMethods, Inc.
> 703-460-2513 or asirv@webmethods.com
> http://www.webmethods.com/
Received on Tuesday, 13 August 2002 19:37:32 GMT

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