- From: Hugo Haas <hugo@w3.org>
- Date: Sat, 6 Nov 2004 10:54:06 +0100
- To: public-ws-addressing@w3.org
- Message-ID: <20041106095406.GH20555@w3.org>
* Hugo Haas <hugo@w3.org> [2004-11-05 22:57+0100] > * Hugo Haas <hugo@w3.org> [2004-11-03 19:36+0100] > > This is to start discussion about issue 021: > > > > Does there need to be an extension for WSDL to explicitly call out > > the use of Addressing? > > > > http://www.w3.org/2002/ws/addr/wd-issues/#i021 > [..] > > Here is a concrete proposal for resolving this issue. Motivation pour > such a solution was detailed in my previous email and on this week's > call. > > As it was unclear after last call what the WG wants to do about > incorporating addressing into the WSDL 2.0 SOAP binding or not — or at > least suggest it to the WS Description WG —, I will be proposing two > options at the end. > > Preliminary proposals: > > a. Identify the core specification with a URI. > > That will allow to refer to our addressing mechanism in different > bindings and at the interface level in WSDL, as a feature. [..] To be complete about a WSDL description of addressing, I forgot to mention that the message information properties should be given a URI and flagged as properties of this feature. Some of those will be set at run time while others (e.g. reference properties, if I understand them correctly) will be described in the WSDL. Please note that this is not a WSDL 2.0 F&P versus content model discussion that I want to start here, which is a topic that belongs to the Web Services Description Working Group. Giving URIs to those properties just identifies them so that they can be easily described and talked about. I believe that this solution covers our bases for whatever the Web Services Description Working Group ends up with in this space. Regards, Hugo -- Hugo Haas - W3C mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Saturday, 6 November 2004 09:54:07 UTC