W3C home > Mailing lists > Public > public-ws-addressing-eds@w3.org > January to March 2007

2004/ws/addressing ws-addr-wsdl.xml,1.108,1.109

From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
Date: Sun, 14 Jan 2007 20:31:39 +0000
To: public-ws-addressing-eds@w3.org
Message-Id: <E1H6C0x-0005lr-LR@lionel-hutz.w3.org>

Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv22070

Modified Files:
	ws-addr-wsdl.xml 
Log Message:
removed UsingAddressing and SOAP module, updated conformance to suit, added None URI as acceptable

Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.108
retrieving revision 1.109
diff -C 2 -d -r1.108 -r1.109
*** ws-addr-wsdl.xml	10 Jan 2007 11:26:32 -0000	1.108
--- ws-addr-wsdl.xml	14 Jan 2007 20:31:36 -0000	1.109
***************
*** 305,430 ****
          <div1 id="indicatinguse">
              <head>Indicating Use of WS-Addressing</head>
!             <p>This specification supports two mechanisms for indicating, in a WSDL description,
!                 that the endpoint conforms to the WS-Addressing specification. </p>
!             <div2 id="uaee">
!                 <head><el>UsingAddressing</el> Extension Element</head>
!                 <p> WS-Addressing defines an empty global element, wsam:UsingAddressing, that can be
!                     used to indicate that an endpoint conforms to the WS-Addressing specification.
!                     The wsdl:required attribute MAY be used to indicate whether WS-Addressing
!                     Message Addressing Properties are required in messages received from service
!                     requesters. <specref ref="mappresence"/> outlines the requirements on messages
!                     sent from an endpoint based on the contents of any preceding input message and
!                     how the use of addressing is indicated in the WSDL. </p>
!                 <table border="1" id="mappresence">
!                     <caption>MAPs Present in output message when wsam:UsingAddressing is present</caption>
!                     <thead>
!                         <tr>
!                             <th>MAPs in Input message</th>
!                             <th>wsdl:required="true" {addressing}=required</th>
!                             <th>wsdl:required="false" {addressing}=optional</th>
!                         </tr>
!                     </thead>
!                     <tbody>
!                         <tr>
!                             <td>Yes</td>
!                             <td>REQUIRED</td>
!                             <td>REQUIRED</td>
!                         </tr>
!                         <tr>
!                             <td>No</td>
!                             <td>Fault</td>
!                             <td>OPTIONAL. If using SOAP, MAP headers MUST NOT have a
!                                 soap:mustUnderstand attribute with a value of "true"</td>
!                         </tr>
!                     </tbody>
!                 </table>
!                 <p>If WS-A is engaged, use of the message addressing properties MUST be fully
!                     compliant with this specification; in particular, senders MUST use all message
!                     addressing properties mandated by the &wsa-core.title;[<bibref
!                         ref="WSADDR-CORE"/>], applicable WS-Addressing protocol bindings (e.g.
!                         &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]), and this specification,
!                     and MUST follow all applicable WS-Addressing normative requirements. </p>
!                 <p>The wsam:UsingAddressing element SHOULD appear as a child of the wsdl:binding
!                     element. Alternatively, the wsam:UsingAddressing element MAY instead be included
!                     as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
!                     indicate compliance with WS-Addressing for a specific endpoint only.</p>
!                 <p>The inclusion of the wsam:UsingAddressing element indicates that the applicable
!                     WS-Addressing specifications are supported and allows use of anonymous or
!                     non-anonymous URIs as addresses in an EPR. Specifically, when included in a SOAP
!                     binding, the wsam:UsingAddressing marker identifies the use of Web Services
!                     Addressing 1.0 bound to SOAP as defined by &wsa-soap.title;[<bibref
!                         ref="WSADDR-SOAP"/>].The presence of this element can extend the semantics
!                     of the endpoint's WSDL binding. </p>
!                 <example>
!                     <head>Indicating use of WS-Addressing using wsam:UsingAddressing in WSDL 2.0</head>
!                     <eg xml:space="preserve">&lt;binding name="reservationSOAPBinding" 
!     interface="tns:reservationInterface"
!     type="&wsdl20nsuri;/soap"
!     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
!   &lt;wsam:UsingAddressing wsdl:required="true" /&gt;
!   &lt;operation ref="tns:opCheckAvailability"
!       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" /&gt;
!   &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
! &lt;/binding&gt;</eg>
!                 </example>
!                 <example>
!                     <head>Indicating use of WS-Addressing using wsam:UsingAddressing in WSDL 1.1</head>
!                     <eg xml:space="preserve">&lt;binding name="reservationSOAPBinding"
!                         type="tns:reservationInterface"&gt;
!   &lt;soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" /&gt;
!   &lt;wsam:UsingAddressing wsdl:required="true" /&gt;
!   &lt;operation name="opCheckAvailability"&gt;
!     &lt;soap:operation soapaction="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability" /&gt;
!     &lt;input&gt; 
!       &lt;soap:body use="literal" /&gt;
!     &lt;/input&gt; 
!     &lt;output&gt;
!       &lt;soap:body use="literal" /&gt;
!     &lt;/output&gt;
!   &lt;/operation&gt;
! &lt;/binding&gt;</eg>
!                 </example>
!                 <div3 id="wsdl20_usingaddressing">
!                     <head>WSDL 2.0 Component Model Changes</head>
!                     <p>Use of WS-Addressing adds the following property to the WSDL 2.0 component
!                         model:</p>
!                     <ulist>
!                         <item>
!                             <p>{addressing} OPTIONAL, of type <code>xs:token</code> with one of the
!                                 values <attval>required</attval> or <attval>optional</attval>, to
!                                 the Binding and Endpoint components. When present, the property
!                                 indicates that the use of addressing has been declared. </p>
!                         </item>
!                     </ulist>
!                     <p><specref ref="tab_addressing_Mapping"/> shows the mapping from the XML
!                         representation to the WSDL 2.0 component model.</p>
!                     <table border="1" id="tab_addressing_Mapping">
!                         <caption>Mapping from XML Representation to Binding and Endpoint components
!                             Extension Properties</caption>
!                         <tbody>
!                             <tr>
!                                 <th rowspan="1" colspan="1">Property</th>
!                                 <th rowspan="1" colspan="1">Value</th>
!                             </tr>
!                             <tr>
!                                 <td>{addressing}</td>
!                                 <td> If a <el>wsam:UsingAddresing</el> extension element is present: <ulist>
!                                         <item>
!                                             <p>if a <att>wsdl:required</att> &AII; is present
!                                                 and has a value of <attval>true</attval>, then
!                                                   <attval>required</attval></p>
!                                         </item>
!                                         <item>
!                                             <p>otherwise <attval>optional</attval></p>
!                                         </item>
!                                     </ulist>
!                                 </td>
!                             </tr>
!                         </tbody>
!                     </table>
!                     <p><specref ref="mappresence"/> summarizes the meaning of the property as
!                         detailed in section <specref ref="uaee"/>.</p>
!                 </div3>
!             </div2>
              <div2 id="wspolicyassertions">
                  <head>WS-Policy Assertions</head>
--- 305,311 ----
          <div1 id="indicatinguse">
              <head>Indicating Use of WS-Addressing</head>
!             <p>This specification supports a mechanism for indicating, in a WSDL description, that
!                 the endpoint conforms to the WS-Addressing specification. That mechanism uses
!                 WS-Policy Framework [<bibref ref="WSPolicy"/>].</p>
              <div2 id="wspolicyassertions">
                  <head>WS-Policy Assertions</head>
***************
*** 432,439 ****
                          <edtext>open issue on policy attachment options</edtext>
                  </ednote>
!                 <p>Another mechanism for indicating that a binding or endpoint  conforms to the WS-Addressing specification is through the use of the
!                     Web Services Policy - Framework [<bibref ref="WSPolicy"/>] and Web Services
!                     Policy - Attachment [<bibref ref="WSPolicyAttachment"/>] specifications. This
!                     specification defines three policy assertions.</p>
                  <p>For WSDL 1.1, these assertions may be attached to <code>wsdl11:port</code> or
                      <code>wsdl11:binding</code>. For WSDL 2.0, they may be attached to
--- 313,321 ----
                          <edtext>open issue on policy attachment options</edtext>
                  </ednote>
!                 <p>The mechanism for indicating that a binding or endpoint conforms to the
!                     WS-Addressing specification is through the use of the Web Services Policy -
!                     Framework [<bibref ref="WSPolicy"/>] and Web Services Policy - Attachment
!                         [<bibref ref="WSPolicyAttachment"/>] specifications. This specification
!                     defines three policy assertions.</p>
                  <p>For WSDL 1.1, these assertions may be attached to <code>wsdl11:port</code> or
                      <code>wsdl11:binding</code>. For WSDL 2.0, they may be attached to
***************
*** 442,451 ****
                      <head>Addressing Assertion</head>
                      <p>The wsam:Addressing policy assertion is a nested policy container assertion.
!                         The meaning of this assertion when present in a policy alternative is that
                          WS-Addressing is required to communicate with the subject. In order to
                          indicate that the subject supports WS-Addressing but does not require its
                          use, an additional policy alternative should be provided which does not
                          contain this assertion. This may be done in WS-Policy compact form by adding
!                         the attribute wsp:Optional="true" to the Addressing assertion. </p>
                  </div3>
                  <div3 id="wspolicyanonresponses">
--- 324,333 ----
                      <head>Addressing Assertion</head>
                      <p>The wsam:Addressing policy assertion is a nested policy container assertion.
!                         The meaning of this assertion, when present in a policy alternative, is that
                          WS-Addressing is required to communicate with the subject. In order to
                          indicate that the subject supports WS-Addressing but does not require its
                          use, an additional policy alternative should be provided which does not
                          contain this assertion. This may be done in WS-Policy compact form by adding
!                         the attribute wsp:Optional="true" to the wsam:Addressing assertion. </p>
                  </div3>
                  <div3 id="wspolicyanonresponses">
***************
*** 462,465 ****
--- 344,350 ----
                          anonymous URI as an address; it simply indicates the lack of any affirmation
                          of support for anonymous URIs. </p>
+                     <p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
+                         value of [address] in place of the anonymous URI; this value MUST be
+                         accepted.</p>
                  </div3>
                  <div3 id="wspolicynonanonresponses">
***************
*** 479,482 ****
--- 364,369 ----
                          endpoint will not accept request messages with response endpoint EPRs that
                          contain something other than the anonymous URI address. </p>
+                     <p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
+                         value of [address] in place of a non-anonymous address; this value MUST be accepted.</p>
                  </div3>
                  <div3>
***************
*** 683,712 ****
                  </div3>                
              </div2>
-             <div2 id="wsdlsoapmodule">
-                 <head>WSDL SOAP Module</head>
-                 <p> In WSDL 2.0, a SOAP Module component can be used to declare the use of the
-                     WS-Addressing 1.0 Module for the SOAP binding. The meaning of the use of such a
-                     SOAP Module component is semantically equivalent to the {addressing} property
-                     defined in section <specref ref="wsdl20_usingaddressing"/>. Note that this
-                     module is only meaningful when used on WSDL components where the {addressing}
-                     property is allowed, i.e. as a member of the {soap modules} property of a
-                     Binding component.</p>
-                 <p>The WS-Addressing 1.0 SOAP Module is described in &wsa-soap.title;[<bibref
-                         ref="WSADDR-SOAP"/>] and is identified with the following URI:
-                     &nsuri;/module</p>
-                 <example>
-                     <head>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</head>
-                     <eg xml:space="preserve">&lt;binding name="reservationSOAPBinding" 
-     interface="tns:reservationInterface"
-     type="&wsdl20nsuri;/soap"
-     wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP"&gt;
-   &lt;wsoap:module uri="&nsuri;/module" required="true" /&gt;
-   &lt;operation ref="tns:opCheckAvailability"
-       wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response"&gt;
-   &lt;/operation&gt;
-   &lt;fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" /&gt;
- &lt;/binding&gt;</eg>
-                 </example>
-             </div2>
          </div1>
          <div1 id="mapvaluesinwsdl">
--- 570,573 ----
***************
*** 1647,1654 ****
                  obeys the structural constraints defined in that section.</p>
              <p> A WSDL description conforms to this specification when it incorporates directly or
!                 indirectly one or more of the <specref ref="wspolicyassertions"/> or the <specref
!                     ref="wsdlsoapmodule"/> markers, and obeys the structural constraints defined in
!                 section <specref ref="indicatinguse"/> appropriate to that marker, and those defined
!                 in section <specref ref="actioninwsdl"/>. </p>
              <p> An endpoint conforms to this specification if it has a conformant WSDL description
                  associated with it, and receives and emits messages in accordance with the
--- 1508,1514 ----
                  obeys the structural constraints defined in that section.</p>
              <p> A WSDL description conforms to this specification when it incorporates directly or
!                 indirectly the <specref ref="wspolicyassertions"/> marker, and obeys the structural
!                 constraints defined in section <specref ref="indicatinguse"/> appropriate to that
!                 marker, and those defined in section <specref ref="actioninwsdl"/>. </p>
              <p> An endpoint conforms to this specification if it has a conformant WSDL description
                  associated with it, and receives and emits messages in accordance with the
Received on Sunday, 14 January 2007 20:32:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:19:41 GMT