W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2005

Proposed resolution for issues 24 (metadata) and 26 (multiple ports)

From: Vinoski, Stephen <Steve.Vinoski@iona.com>
Date: Mon, 31 Jan 2005 13:30:45 -0500
Message-ID: <13AC4E67178F4D4EA31BB1BA645303132DC19B@amereast-ems2.boston.amer.iona.com>
To: <public-ws-addressing@w3.org>
Cc: "Paco Curbera, Francisco" <curbera@us.ibm.com>, "Bergersen, Rebecca" <Rebecca.Bergersen@iona.com>, "Yalcinalp, Umit" <umit.yalcinalp@sap.com>, "Greg Truty" <gtruty@us.ibm.com>

We (IBM, IONA, SAP) propose the following as a resolution to issues 24
(metadata) and 26 (multiple ports).  The representation of multiple ports
may be considered metadata and hence can be resolved within the metadata

1. There should be a metadata bucket in an EPR:

   <!-- other stuff-->

2. The contents of the metadata bucket are represented by value or by
reference. Examples of content would be the WSDL Service definition; lists
of QNames and ports, policies; etc. See below.

3. The semantics and usage of the contents of the metadata bucket are explained
in the WSDL binding section when the metadata section includes WSDL.  If
wsp-policy are found in the metadata section, then its use is clarified by
the WS-Policy spec.  In other words, the various kinds of information found
in the metadata section are clarified by the relevant specs and binding

3A. A corollary is that the ws-addressing policy section is removed and
replaced by the metadata section.

4. Data included in the metadata bucket follows the precedence definition in
the resolution to issue 14.

Example usage:

   [<wsdl11:service> | <wsdl20:service> ] <extensibility>* </wsa:metadata>

- This allows partially reusing the wsdl11 and wsdl20 schema definitions for
service element that includes the port/endpoints. It also allows other
metadata, even the full wsdl definitions to be included if desired.

- WSDL 2.0 service element is defined by wsdl 2.0. See [1].

- By using the wsdlLocation attribute one may be able to obtain portions
of wsdl by reference and use it, such as bindings etc. The example below
illustrates this.

- we propose the use of the WSDL 1.1 service element defined by WS-I BP 1.1
profile which allows element and attribute extensibility. (It is currently
missing from the website that is why it is not included as a reference in
this email).

WSDL 2.0 example: 

      <wsdl20:service name="myservice" 
         <wsdl20:endpoint name="e1" binding="abc:soap-http-binding" 
         <wsdl20:endpoint name="alternate1" binding="abc:iiop" 
         <wsdl20:endpoint name="alternate2" 

WSDL 1.1 example: 

      <wsdl11:service name="myservice" 
         <wsdl11:port name="e1" binding="abc:soap-http-binding"> 
                 <soap:address location="http://foo.com"/>
         <wsdl11:port name="alternate1" binding="abc:iiop"> 
                 <iiop:address location="..."/>




Rebecca Bergersen (IONA)
Paco Curbera (IBM)
Greg Truty (IBM)
Steve Vinoski (IONA)
Umit Yalcinalp (SAP)
Received on Monday, 31 January 2005 18:30:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:08 UTC