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

RE: Issue 021: WSDL Extension for Addressing

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Mon, 15 Nov 2004 11:38:05 -0800
Message-ID: <7DA77BF2392448449D094BCEF67569A505A50CD7@RED-MSG-30.redmond.corp.microsoft.com>
To: "Hugo Haas" <hugo@w3.org>, <public-ws-addressing@w3.org>

WSDL 2.0 provides two appropriate mechanisms, WSDL 1.1 provides one.  I
think it's up to us to design the mechanism (or mechanisms in the worst
case) that is appropriate for us, not to ask the WSDL WG to do it for
us.

I don't believe we can make any useful progress (e.g. defining URIs for
message information properties) until we've made this big decision.  It
is equally true that we can "cover out bases" with a preliminary
proposal based on element extension.

Designing a single extension that works across WSDL 1.1 and WSDL 2.0 is
very attractive to me, and element extension therefore seems like a
natural fit.

> -----Original Message-----
> From: public-ws-addressing-request@w3.org
[mailto:public-ws-addressing-
> request@w3.org] On Behalf Of Hugo Haas
> Sent: Saturday, November 06, 2004 1:54 AM
> To: public-ws-addressing@w3.org
> Subject: Re: Issue 021: WSDL Extension for Addressing
> 
> * 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 Monday, 15 November 2004 19:53:57 GMT

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