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

Re: Issue 021: WSDL Extension for Addressing

From: Hugo Haas <hugo@w3.org>
Date: Fri, 5 Nov 2004 22:57:31 +0100
To: public-ws-addressing@w3.org
Message-ID: <20041105215731.GD20555@w3.org>
* 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

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.

b. Identify our SOAP 1.2 extension with a URI.

   Again, we are defining a SOAP 1.2 module for addressing, that ought
   to be identified by a URI.

   This SOAP 1.2 module will implement the addressing feature that we
   define in (a). Nothing fancy here, just making things clear.

This gives us the basis for addressing issue 021.

Option #1: consider addressing ubiquitous in SOAP 1.2 implementations

  -> talk with the WSDWG about saying that the SOAP 1.2 binding
  provides feature defined in (a) by using the module defined in (b).

Option #2: addressing is an extension like any other extension

  -> the use of addressing will be called out explicitely in WSDL 2.0
  by using wsoap:module with the URI defined in (b).



Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

Received on Friday, 5 November 2004 21:57:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:28:20 UTC