W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2003

Re: HTML version of operation name proposal

From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
Date: Fri, 31 Jan 2003 01:16:31 +0600
Message-ID: <009b01c2c894$1a544300$b300a8c0@lankabook2>
To: "Martin Gudgin" <mgudgin@microsoft.com>, <www-ws-desc@w3.org>

Hi Gudge,

I have some questions in trying to understand your proposal. They
are centered around how this works with inheritance and the other
on language binding.

Consider the following case (using pseudo syntax which I hope clear
enough to all):

WSDL document 1:
    namespace = nsuri-1;
    portType pt1 {
        operation o1;
        operation o2;
    }

WSDL document 2:
    namespace = nsuri-2;
    portType pt2 extends {nsuri-1}pt1 {
        operation o3;
    }

Now, what are the operations available in {nsuri-2}pt2? Can you
please indicate both the name and targetnamespace properties of
each of the operations?

Also consider another WSDL document:

WSDL document 3:
    namespace = nsuri-3;
    portType pt3 extends {nsuri-1}pt1 {
        operation o1;
    }
            
Is this legal? What are the constraints on what can be in the o1
definition in pt3 (if any)?

If legal, what are the values of the TNS and name properties of 
all the operations available via pt3?

Finally, how does all this look when bound to a language (like
Java)? I'd like to understand how the targetnamespace properties
of an operation name will be represented in the language binding.
Yes, I know we don't do language binding, but someone does.

Thanks,

Sanjiva.

----- Original Message ----- 
From: "Martin Gudgin" <mgudgin@microsoft.com>
To: <www-ws-desc@w3.org>
Sent: Thursday, January 30, 2003 11:45 PM
Subject: HTML version of operation name proposal


> 
> An HTML version of the operation name proposal can be found at[1]. It is
> exactly the same as the XML version at[2]. It differs from the link I
> previously sent out to the list in two respects:
> 
> 1. It contains the best practice note
> 2. The binding operation component now has a {target namespace}
> property to match the corresponding component in the port type
> 
> Gudge
> 
> [1]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.html?rev=
> 1.18.2.1&content-type=text/html
> [2]
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.xml?rev=1
> .37.2.3&content-type=text/xml
Received on Thursday, 30 January 2003 14:19:18 GMT

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