W3C home > Mailing lists > Public > public-ws-addressing@w3.org > December 2004

Re: Issue i020 - Addressing and WSDL

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Mon, 20 Dec 2004 00:11:00 -0800
Message-ID: <41C68914.20505@oracle.com>
To: David Orchard <dorchard@bea.com>
CC: public-ws-addressing@w3.org

David Orchard wrote:
> 
> 
>>-----Original Message-----
>>From: public-ws-addressing-request@w3.org
> 
> [mailto:public-ws-addressing-
> 
>>request@w3.org] On Behalf Of Anish Karmarkar
> 
>  
> 
>>Specifically, I would like to understand why the wsdl service element
>>cannot be used here instead of wsa:EndpointReference ?
> 
> 
> Is this what WS-MessageDelivery does? 

Yes, WS-MD reuses existing WSDL elements/types where it can and 
leverages WSDL attribute/element extensibility where necessary.

> Does your question effectively
> argue that the relevant portions of WS-MessageDelivery should be used as
> the basis for the relevant portions of the WS-Addressing specification?
> 

No.
This is specific to whether we need new syntactic structures for 
addressing OR whether existing WSDL elements/types can be repurposed for 
addressing (if they serve the same purpose).

For example, WS-MD also defines mappings to WSDL MEPs/operations. 
WS-Addressing is also defining those mappings. I'm not suggesting that 
WS-Addressing should define such mappings in the same/similar way as WS-MD.

A bonus from such a reuse is, stacks that already understand WSDL 
elements/types don't have to do a whole lot more.

At the very least I would like to understand the rationale for/thinking 
behind inventing new syntactic structures.

HTH.

-Anish
--
Received on Monday, 20 December 2004 08:11:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:00 GMT