- From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 28 Apr 2006 13:44:31 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv14392
Modified Files:
ws-addr-wsdl.html
Log Message:
Updated with the results of LC124, LC129, and LC131
Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.44
retrieving revision 1.45
diff -C2 -d -r1.44 -r1.45
*** ws-addr-wsdl.html 17 Apr 2006 10:33:04 -0000 1.44
--- ws-addr-wsdl.html 28 Apr 2006 13:44:29 -0000 1.45
***************
*** 70,75 ****
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br> 1.1 <a href="#notation"> Notational Conventions</a><br> 1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br> 2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br> 2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br> 3.1 <a href="#uaee">UsingAddressing Extension Element</a><br> 3.1.1 <a href="#wsdl20_usingaddressing">WSDL 2.0 Component Model Changes</a><br> 3.1.2 <a href="#N10304">Other Uses of UsingAddressing Extension Element</a><br> 3.2 <a href="#anonelement"> Anonymous Element </a><br> &nsp; 3.2.1 <a href="#wsdl20_anonymous">WSDL 2.0 Component Model Changes</a><br> 3.3 <a href="#wsdlsoapmodule">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br> 4.1 <a href="#destinwsdl">Destination</a><br> 4.2 <a href="#actioninwsdl">Action</a><br> 4.2.1 <a href="#explicitaction">Explicit Association</a><br> 4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.2.3 <a href="#N104F3">WSDL 2.0 Component Model Changes</a><br> 4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br> 4.3 <a href="#refpinwsdl">Reference Parameters</a><br> 4.3.1 <a href="#refpiwsdlcm">WSDL 2.0 Component Model Changes</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br> 5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br> 5.1.1 <a href="#wsdl11oneway">One-way</a><br> 5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br> 5.1.3 <a href="#wsdl11notification">Notification</a><br> 5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br> 5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br> 5.2.1 <a href="#wsdl20inonly">In-only</a><br> 5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br> 5.2.3 <a href="#wsdl20inout">In-out</a><br>&nsp; 5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br> 5.2.5 <a href="#wsdl20outonly">Out-only</a><br> 5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br> 5.2.7 <a href="#wsdl20outin">Out-in</a><br> 5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br> C.1 <a href="#N10D5E">Changes Since Third Working Draft</a><br> C.2 <a href="#N10D68">Changes Since Second Working Draft</a><br> C.3 <a href="#N10D72">Changes Since First Working Draft</a><br> C.4 <a href="#N10D7C">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
--- 70,75 ----
no official standing.</strong></p><p></p></div>
<hr><div class="toc">
! <h2><a name="contents">Table of Contents</a></h2><p class="toc">1. <a href="#tocRange"> Introduction</a><br> 1.1 <a href="#notation"> Notational Conventions</a><br> 1.2 <a href="#namespaces"> Namespaces</a><br>2. <a href="#metadatinepr">Including WSDL Metadata in EPRs</a><br> 2.1 <a href="#refmetadatfromepr">Referencing WSDL Metadata from an EPR</a><br> 2.2 <a href="#embedmetadataepr">Embedding WSDL Metadata in an EPR</a><br>3. <a href="#indicatinguse">Indicating Use of WS-Addressing</a><br> 3.1 <a href="#uaee">UsingAddressing Extension Element</a><br> 3.1.1 <a href="#wsdl20_usingaddressing">WSDL 2.0 Component Model Changes</a><br> 3.1.2 <a href="#N102D5">Other Uses of UsingAddressing Extension Element</a><br> 3.2 <a href="#anonelement"> Anonymous Element </a><br> &nsp; 3.2.1 <a href="#wsdl20_anonymous">WSDL 2.0 Component Model Changes</a><br> 3.3 <a href="#wsdlsoapmodule">WSDL SOAP Module</a><br>4. <a href="#mapvaluesinwsdl">Specifying Message Addressing Properties in WSDL</a><br> 4.1 <a href="#destinwsdl">Destination</a><br> 4.2 <a href="#actioninwsdl">Action</a><br> 4.2.1 <a href="#explicitaction">Explicit Association</a><br> 4.2.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.2.3 <a href="#N104BE">WSDL 2.0 Component Model Changes</a><br> 4.2.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</a><br> 4.3 <a href="#refpinwsdl">Reference Parameters</a><br> 4.3.1 <a href="#refpiwsdlcm">WSDL 2.0 Component Model Changes</a><br>5. <a href="#WSDLMEPS">WS-Addressing and WSDL Message Exchange Patterns</a><br> 5.1 <a href="#WSDL11MEPS">WSDL 1.1 Message Exchange Patterns</a><br> 5.1.1 <a href="#wsdl11oneway">One-way</a><br> 5.1.2 <a href="#wsdl11requestresponse">Request-Response</a><br> 5.1.3 <a href="#wsdl11notification">Notification</a><br> 5.1.4 <a href="#wsdl11solicitresponse">Solicit-response</a><br> 5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message Exchange Patterns</a><br> 5.2.1 <a href="#wsdl20inonly">In-only</a><br> 5.2.2 <a href="#wsdl20robustinonly">Robust In-only</a><br> 5.2.3 <a href="#wsdl20inout">In-out</a><br>&nsp; 5.2.4 <a href="#wsdl20inoptionalout">In-optional-out</a><br> 5.2.5 <a href="#wsdl20outonly">Out-only</a><br> 5.2.6 <a href="#wsdl20robustoutonly">Robust Out-only</a><br> 5.2.7 <a href="#wsdl20outin">Out-in</a><br> 5.2.8 <a href="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#conformance">Conformance</a><br>7. <a href="#references"> References</a><br></p>
! <h3><a id="appendix" name="appendix">Appendices</a></h3><p class="toc">A. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)<br>B. <a href="#actioncompatibility">Compatibility of [action] with previous versions of WS-Addressing</a> (Non-Normative)<br>C. <a href="#changelog">Change Log</a> (Non-Normative)<br> C.1 <a href="#N10D4E">Changes Since Third Working Draft</a><br> C.2 <a href="#N10D58">Changes Since Second Working Draft</a><br> C.3 <a href="#N10D62">Changes Since First Working Draft</a><br> C.4 <a href="#N10D6C">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 180,184 ****
<dl>
! <dt class="label"> wsaw:InterfaceName</dt>
<dd>
<p>A QName identifying a description of the sequences of messages that a
--- 180,184 ----
<dl>
! <dt class="label"> wsaw:InterfaceName (0..1)</dt>
<dd>
<p>A QName identifying a description of the sequences of messages that a
***************
*** 190,194 ****
! <dt class="label"> wsaw:ServiceName</dt>
<dd>
<p>A QName that identifies the set of endpoints at which a particular
--- 190,194 ----
! <dt class="label"> wsaw:ServiceName (0..1)</dt>
<dd>
<p>A QName that identifies the set of endpoints at which a particular
***************
*** 199,203 ****
! <dt class="label"> wsaw:ServiceName/@EndpointName</dt>
<dd>
<p>An NCName that identifies one endpoint amongst the set identified by
--- 199,203 ----
! <dt class="label"> wsaw:ServiceName/@EndpointName (0..1)</dt>
<dd>
<p>An NCName that identifies one endpoint amongst the set identified by
***************
*** 211,216 ****
<p>The element information items defined above are used in an EPR's metadata section.
The following shows an example endpoint reference. This references the interface
! named "fabrikam:Inventory" at the endpoint IRI
! "http://example.com/fabrikam/acct". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
--- 211,216 ----
<p>The element information items defined above are used in an EPR's metadata section.
The following shows an example endpoint reference. This references the interface
! named "ghns:reservationInterface" at the endpoint IRI
! "http://greath.example.com/2004/reservation". Note the use of the WSDL[<cite><a href="#WSDL20">WSDL 2.0</a></cite>] wsdlLocation attribute.</p>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
***************
*** 218,227 ****
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing"
! xmlns:fabrikam="http://example.com/fabrikam">
! <wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
<wsa:Metadata
xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
! wsdli:wsdlLocation="http://example.com/fabrikam http://example.com/fabrikam.wsdl">
! <wsaw:InterfaceName>fabrikam:Inventory</wsaw:InterfaceName>
</wsa:Metadata>
</wsa:EndpointReference></pre></div>
--- 218,227 ----
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing"
! xmlns:ghns="http://greath.example.com/2004/wsdl/resSvc">
! <wsa:Address>http://greath.example.com/2004/reservation</wsa:Address>
<wsa:Metadata
xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
! wsdli:wsdlLocation="http://greath.example.com/2004/wsdl/resSvc http://greath.example.com/2004/reservation.wsdl">
! <wsaw:InterfaceName>ghns:reservationInterface</wsaw:InterfaceName>
</wsa:Metadata>
</wsa:EndpointReference></pre></div>
***************
*** 258,283 ****
xmlns:wsa="http://www.w3.org/2005/08/addressing">
! <wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
<wsa:Metadata
xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
! wsdli:wsdlLocation="http://example.com/fabrikam http://example.com/fabrikam.wsdl">
<wsdl20:description
! targetNamespace="http://example.com/fabrikam"
! xmlns:fabrikam="http://example.com/fabrikam"
! xmlns:abc="http://www.abccorp.com/"
xmlns:wsdl20="http://www.w3.org/2006/01/wsdl">
! <wsdl20:import namespace="http://example.com/fabrikam/"
! location="http://example.com/fabrikam/fabrikam.wsdl/"/>
! <wsdl20:import namespace="http://www.abccorp.com/"
! location="http://www.abccorp.com/abc.wsdl"/>
! <wsdl20:service name="InventoryService"
! interface="fabrikam:Inventory">
! <wsdl20:endpoint name="ep1" binding="abc:soap-http-binding"
! address="http://example.com/fabrikam/acct"/>
! <wsdl20:endpoint name="ep2" binding="abc:iiop"
! address="..."/>
! <wsdl20:endpoint name="ep3"
! binding="abc:soap-http-binding"
! address="http://alt.example.com/fabrikam/acct"/>
</wsdl20:service>
</wsdl20:description>
--- 258,277 ----
xmlns:wsa="http://www.w3.org/2005/08/addressing">
! <wsa:Address>http://greath.example.com/2004/reservation</wsa:Address>
<wsa:Metadata
xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
! wsdli:wsdlLocation="http://greath.example.com/2004/wsdl/resSvc http://greath.example.com/2004/reservation.wsdl">
<wsdl20:description
! targetNamespace="http://greath.example.com/2004/wsdl/resSvc"
! xmlns:tns="http://greath.example.com/2004/wsdl/resSvc"
! xmlns:ghns="http://greath.example.com/2004/wsdl/resSvc"
xmlns:wsdl20="http://www.w3.org/2006/01/wsdl">
! <wsdl20:import namespace="http://greath.example.com/2004/wsdl/resSvc"
! location="http://greath.example.com/2004/reservation.wsdl"/>
! <wsdl20:service name="reservationService"
! interface="tns:reservationInterface">
! <wsdl20:endpoint name="reservationEndpoint"
! binding="tns:reservationSOAPBinding"
! address ="http://greath.example.com/2004/reservation"/>
</wsdl20:service>
</wsdl20:description>
***************
*** 291,312 ****
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing">
! <wsa:Address>http://example.com/fabrikam/acct</wsa:Address>
<wsa:Metadata>
! <wsdl11:definitions targetNamespace="http://example.com/fabrikam"
! xmlns:fabrikam="http://example.com/fabrikam"
! xmlns:abc="http://www.abccorp.com/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
- xmlns:iiop="http://www.iiop.org/"
xmlns:wsdl11="http://schemas.xmlsoap.org/wsdl/">
! <wsdl11:import namespace="http://example.com/fabrikam"
! location="http://example.com/fabrikam/fabrikam.wsdl"/>
! <wsdl11:import namespace="http://www.abccorp.com/"
! location="http://www.abccorp.com/abc.wsdl"/>
! <wsdl11:service name="InventoryService">
! <wsdl11:port name="ep1" binding="abc:soap-http-binding">
! <soap:address location="http://example.com/fabrikam/acct"/>
! </wsdl11:port>
! <wsdl11:port name="ep2" binding="abc:iiop">
! <iiop:address location="..."/>
</wsdl11:port>
</wsdl11:service>
--- 285,299 ----
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing">
! <wsa:Address>http://greath.example.com/2004/reservation</wsa:Address>
<wsa:Metadata>
! <wsdl11:definitions targetNamespace="http://greath.example.com/2004/wsdl/resSvc"
! xmlns:ghns="http://greath.example.com/2004/wsdl/resSvc"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:wsdl11="http://schemas.xmlsoap.org/wsdl/">
! <wsdl11:import namespace="http://greath.example.com/2004/wsdl/resSvc"
! location="http://greath.example.com/2004/reservation.wsdl"/>
! <wsdl11:service name="reservationService">
! <wsdl11:port name="ep1" binding="ghns:reservationSOAPBinding">
! <soap:address location="http://greath.example.com/2004/reservation"/>
</wsdl11:port>
</wsdl11:service>
***************
*** 339,350 ****
</p>
<a name="mappresence"></a><table border="1">
! <caption>Table 3-1. MAPs Present in output message</caption>
<thead>
<tr>
! <th rowspan="2" colspan="1">MAPs in Input message</th>
! <th colspan="2" align="center" rowspan="1">UsingAddressing / {addressing} Present</th>
! <th rowspan="2" colspan="1">UsingAddressing / {addressing} Not Present</th>
! </tr>
! <tr>
<th rowspan="1" colspan="1">wsdl:required="true" {addressing}=required</th>
<th rowspan="1" colspan="1">wsdl:required="false" {addressing}=optional</th>
--- 326,333 ----
</p>
<a name="mappresence"></a><table border="1">
! <caption>Table 3-1. MAPs Present in output message when wsaw:UsingAddressing is present</caption>
<thead>
<tr>
! <th rowspan="1" colspan="1">MAPs in Input message</th>
<th rowspan="1" colspan="1">wsdl:required="true" {addressing}=required</th>
<th rowspan="1" colspan="1">wsdl:required="false" {addressing}=optional</th>
***************
*** 353,375 ****
<tbody>
<tr>
! <td rowspan="1" colspan="1">Yes, using SOAP headers with a soap:mustUnderstand value of "true"</td>
! <td rowspan="1" colspan="1">REQUIRED</td>
! <td rowspan="1" colspan="1">REQUIRED</td>
! <td rowspan="1" colspan="1">REQUIRED or fault</td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Yes, using another protocol or using SOAP headers with a
! soap:mustUnderstand value of "false"</td>
<td rowspan="1" colspan="1">REQUIRED</td>
<td rowspan="1" colspan="1">REQUIRED</td>
- <td rowspan="1" colspan="1">OPTIONAL</td>
</tr>
! <tr>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">Fault</td>
<td rowspan="1" colspan="1">OPTIONAL. If using SOAP, MAP headers MUST NOT have a
soap:mustUnderstand attribute with a value of "true"</td>
- <td rowspan="1" colspan="1">OPTIONAL. If using SOAP, MAP headers MUST NOT have a
- soap:mustUnderstand attribute with a value of "true"</td>
</tr>
</tbody>
--- 336,348 ----
<tbody>
<tr>
! <td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">REQUIRED</td>
<td rowspan="1" colspan="1">REQUIRED</td>
</tr>
! <tr>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">Fault</td>
<td rowspan="1" colspan="1">OPTIONAL. If using SOAP, MAP headers MUST NOT have a
soap:mustUnderstand attribute with a value of "true"</td>
</tr>
</tbody>
***************
*** 416,424 ****
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
! <div class="exampleInner"><pre><binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsaw:UsingAddressing wsdl:required="true" />
! <operation name="GetLastTradePrice">
! <soap:operation soapaction="http://example.com/GetLastTradePrice" />
<input>
<soap:body use="literal" />
--- 389,398 ----
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 1.1</i></p>
! <div class="exampleInner"><pre><binding name="reservationSOAPBinding"
! type="tns:reservationInterface">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsaw:UsingAddressing wsdl:required="true" />
! <operation name="opCheckAvailability">
! <soap:operation soapaction="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability" />
<input>
<soap:body use="literal" />
***************
*** 486,490 ****
<div class="div3">
! <h4><a name="N10304"></a>3.1.2 Other Uses of UsingAddressing Extension Element</h4>
<p>The wsaw:UsingAddressing element MAY also be used in other contexts
(e.g., as a policy assertion in a policy framework). Its use
--- 460,464 ----
<div class="div3">
! <h4><a name="N102D5"></a>3.1.2 Other Uses of UsingAddressing Extension Element</h4>
<p>The wsaw:UsingAddressing element MAY also be used in other contexts
(e.g., as a policy assertion in a policy framework). Its use
***************
*** 501,572 ****
<h3><a name="anonelement"></a>3.2 Anonymous Element </h3>
! <p>
! WS-Addressing defines a wsaw:Anonymous element that
! is only used in conjunction with
! wsaw:UsingAddressing (or its equivalent wsoap:module)
! element. The usage of wsaw:Anonymous element is
! associated with the usage constraints specified for
! the wsaw:UsingAddressing element. Hence, it MUST NOT
! contain the wsdl:required attribute.
! </p>
! <p>The inclusion of wsaw:Anonymous without inclusion
! of wsaw:UsingAddressing has no normative meaning and is
! only informational. In other words, the inclusion of
! wsaw:Anonymous element in WSDL alone does not imply a
! requirement on clients to use Message Addressing
! Properties in messages it sends to the service. A
! client, however, MAY include Message Addressing
! Properties in the messages it sends, either on its own
! initiative or as described by other elements of the
! service contract, regardless of the presence or
! absence of a wsaw:UsingAddressing element.
! </p>
! <p>The wsaw:Anonymous element MUST have one of three distinct
! values that indicate three different levels of support
! for handling anonymous addresses in EPRs. In the
! following text, the term response endpoint EPR refers
! to the [reply endpoint] and [fault endpoint] message
! addressing properties collectively.
! </p>
<ul>
<li>
! <p>"optional": This value indicates that
! a response endpoint EPR in a request message
! MAY contain an anonymous URI as an address.
! </p>
! <p>This is the default value, omission of a wsaw:Anonymous element is equivalent to inclusion with this value.</p>
</li>
<li>
! <p>"required":This value indicates that all
! response endpoint EPRs in a request message
! MUST always use anonymous URI as an address.
! </p>
! <p>If a response endpoint EPR does not contain
! the anonymous URI as an address value, then a
! predefined InvalidAddressingHeader fault
! defined in Web Services Addressing 1.0 - SOAP Binding [<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] MUST be generated. </p>
</li>
! <li>
! <p>"prohibited":This value indicates that any
! response EPRs in a request message MUST NOT
! use anonymous URI as an address.</p>
! <p>If a response endpoint EPR contains the
! anonymous URI as an address value, then a
! predefined InvalidAddressingHeader fault
! defined in Web Services Addressing 1.0 - SOAP
! Binding [<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] MUST be
! generated. </p>
</li>
! </ul>
! <p>This element MAY appear as a child of an operation
! element in a binding element in WSDL 1.1, or as a
! binding operation extension element in WSDL 2.0.</p>
! <div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span> Indicating use of anonymous addresses using wsaw:Anonymous. </i></p>
! <div class="exampleInner"><pre><binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsaw:UsingAddressing wsdl:required="true" />
! <operation name="GetLastTradePrice">
! <soap:operation soapaction="http://example.com/GetLastTradePrice" />
<input>
<soap:body use="literal" />
--- 475,529 ----
<h3><a name="anonelement"></a>3.2 Anonymous Element </h3>
! <p> WS-Addressing defines a wsaw:Anonymous element that is only used in conjunction
! with wsaw:UsingAddressing (or its equivalent wsoap:module) element. The usage of
! wsaw:Anonymous element is associated with the usage constraints specified for
! the wsaw:UsingAddressing element. Hence, it MUST NOT contain the wsdl:required
! attribute. </p>
! <p>A WSDL or policy based service description that includes the wsaw:UsingAddressing
! but no wsaw:Anonymous marker makes no assertion regarding a requirement or a
! constraint in the use of the anonymous URI in EPRs contained in messages sent to
! the endpoint. In this cases, endpoint service descriptions have to rely on
! additional metadata, such as WSDL bindings or additional policy assertions, to
! indicate any requirements or restrictions on the use of the anonymous URI by
! clients. However, in the absence of additional metadata, clients of the endpoint
! MAY assume that the service endpoint follows the behavior indicated by the
! 'optional' value of the wsaw:Anonymous marker. An endpoint SHOULD send a
! wsa:OnlyAnonymousAddressSupported or a wsa:OnlyNonAnonymousAddressSupported
! fault back to the client if a message received includes a response epr with an
! [address] that is unsupported by the endpoint. </p>
! <p>The wsaw:Anonymous element, if present, MUST have one of three distinct values that indicate
! three different levels of support for handling anonymous addresses in EPRs. In
! the following text, the term response endpoint EPR refers to the [reply
! endpoint] and [fault endpoint] message addressing properties collectively. </p>
<ul>
<li>
! <p>"optional": This value indicates that a response endpoint EPR in a
! request message MAY contain an anonymous URI as an address. </p>
</li>
<li>
! <p>"required":This value indicates that all response endpoint EPRs in a
! request message MUST always use anonymous URI as an address. </p>
! <p>If a response endpoint EPR does not contain the anonymous URI as an
! address value, then a predefined InvalidAddressingHeader fault defined
! in Web Services Addressing 1.0 - SOAP Binding [<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] MUST be generated. </p>
</li>
! <li>
! <p>"prohibited":This value indicates that any response EPRs in a request
! message MUST NOT use anonymous URI as an address.</p>
! <p>If a response endpoint EPR contains the anonymous URI as an address
! value, then a predefined InvalidAddressingHeader fault defined in Web
! Services Addressing 1.0 - SOAP Binding [<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]
! MUST be generated. </p>
</li>
! </ul>
! <p>This element MAY appear as a child of an operation element in a binding element
! in WSDL 1.1, or as a binding operation extension element in WSDL 2.0.</p>
! <div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span> Indicating use of anonymous addresses using wsaw:Anonymous. </i></p>
! <div class="exampleInner"><pre><binding name="reservationSOAPBinding" type="tns:reservationInterface">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsaw:UsingAddressing wsdl:required="true" />
! <operation name="opCheckAvailability">
! <soap:operation soapaction="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability" />
<input>
<soap:body use="literal" />
***************
*** 577,616 ****
<wsaw:Anonymous>required</wsaw:Anonymous>
</operation>
- <operation name="someOther">...</operation>
</binding>
</pre></div>
! </div>
! <div class="div3">
!
<h4><a name="wsdl20_anonymous"></a>3.2.1 WSDL 2.0 Component Model Changes</h4>
!
! <p>Use of the Anonymous element adds the following property to the WSDL 2.0 component model: </p>
! <ul>
! <li>
! <p>{anonymous addresses} REQUIRED, of type xs:string, to the Binding Operation component.</p>
! </li>
! </ul>
!
! <p><a href="#tab_anonymous_Mapping">Table 3-3</a> shows the
! mapping from the XML representation to the WSDL
! 2.0 component model.</p>
!
! <a name="tab_anonymous_Mapping"></a><table border="1">
! <caption>Table 3-3. Mapping from XML Representation to Binding Operation component Extension Properties</caption>
! <tbody>
! <tr>
! <th rowspan="1" colspan="1">Property</th>
! <th rowspan="1" colspan="1">Value</th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">{anonymous addresses}</td>
! <td rowspan="1" colspan="1">
! The value of the <code>wsaw:Anonymous</code> <em>element information item</em>, if present.
! Otherwise, "optional".
! </td>
! </tr>
! </tbody>
! </table><br>
!
</div>
</div>
--- 534,568 ----
<wsaw:Anonymous>required</wsaw:Anonymous>
</operation>
</binding>
</pre></div>
! </div>
! <div class="div3">
!
<h4><a name="wsdl20_anonymous"></a>3.2.1 WSDL 2.0 Component Model Changes</h4>
! <p>Use of the Anonymous element adds the following property to the WSDL 2.0
! component model: </p>
! <ul>
! <li>
! <p>{anonymous addresses} OPTIONAL, of type xs:string, to the Binding
! Operation component.</p>
! </li>
! </ul>
! <p><a href="#tab_anonymous_Mapping">Table 3-3</a> shows the mapping from the XML
! representation to the WSDL 2.0 component model.</p>
! <a name="tab_anonymous_Mapping"></a><table border="1">
! <caption>Table 3-3. Mapping from XML Representation to Binding Operation component
! Extension Properties</caption>
! <tbody>
! <tr>
! <th rowspan="1" colspan="1">Property</th>
! <th rowspan="1" colspan="1">Value</th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">{anonymous addresses}</td>
! <td rowspan="1" colspan="1"> The value of the <code>wsaw:Anonymous</code> <em>element information item</em>, if present.
! Otherwise, it is not present. </td>
! </tr>
! </tbody>
! </table><br>
</div>
</div>
***************
*** 701,712 ****
<p class="exampleHead" style="text-align: left"><i><span>Example 4-1. </span>Explicit specification of wsa:Action value in a WSDL 2.0 description.</i></p>
<div class="exampleInner"><pre>
! <description targetNamespace="http://example.com/stockquote" ...>
...
! <interface name="StockQuoteInterface">
! <operation name="GetLastTradePrice" pattern="http://www.w3.org/2006/01/wsdl/in-out">
! <input element="tns:GetTradePricesInput" messageLabel="In"
! wsaw:Action="http://example.com/GetQuote"/>
! <output element="tns:GetTradePricesOutput" messageLabel="Out"
! wsaw:Action="http://example.com/Quote"/>
</operation>
</interface>
--- 653,664 ----
<p class="exampleHead" style="text-align: left"><i><span>Example 4-1. </span>Explicit specification of wsa:Action value in a WSDL 2.0 description.</i></p>
<div class="exampleInner"><pre>
! <description targetNamespace="http://greath.example.com/2004/schemas/resSvc" ...>
...
! <interface name="reservationInterface">
! <operation name="opCheckAvailability" pattern="http://www.w3.org/2006/01/wsdl/in-out">
! <input element="tns:checkAvailability" messageLabel="In"
! wsaw:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability"/>
! <output element="tns:checkAvailabilityResponse" messageLabel="Out"
! wsaw:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse"/>
</operation>
</interface>
***************
*** 714,732 ****
</description></pre></div>
</div>
! <p>The action for the input of the GetLastTradePrice operation within the
! StockQuoteInterface is explicitly defined to be http://example.com/GetQuote.
The action for the output of this same operation is
! http://example.com/Quote.</p>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://example.com/stockquote" ...>
...
! <portType name="StockQuotePortType">
! <operation name="GetLastTradePrice">
! <input message="tns:GetTradePricesInput"
! wsaw:Action="http://example.com/GetQuote"/>
! <output message="tns:GetTradePricesOutput"
! wsaw:Action="http://example.com/Quote"/>
</operation>
</portType>
--- 666,684 ----
</description></pre></div>
</div>
! <p>The action for the input of the opCheckAvailability operation within the
! SreservationInterface is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability.
The action for the output of this same operation is
! http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 4-2. </span>Explicit specification of wsa:Action value in a WSDL 1.1 description.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://greath.example.com/2004/schemas/resSvc" ...>
...
! <portType name="reservationInterface">
! <operation name="opCheckAvailability">
! <input message="tns:checkAvailability"
! wsaw:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability"/>
! <output message="tns:checkAvailabilityResponse"
! wsaw:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse"/>
</operation>
</portType>
***************
*** 735,742 ****
</pre></div>
</div>
! <p>The action for the input of the GetLastTradePrice operation within the
! StockQuotePortType is explicitly defined to be http://example.com/GetQuote.
The action for the output of this same operation is
! http://example.com/Quote.</p>
</div>
<div class="div3">
--- 687,694 ----
</pre></div>
</div>
! <p>The action for the input of the opCheckAvailability operation within the
! reservationInterface port type is explicitly defined to be http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability.
The action for the output of this same operation is
! http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
</div>
<div class="div3">
***************
*** 846,875 ****
names.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://example.com/stockquote" ...>
...
! <interface name="StockQuoteInterface">
! <operation name="GetLastTradePrice" pattern="http://www.w3.org/2006/01/wsdl/in-out">
! <input element="tns:GetTradePricesInput" messageLabel="in" name="GetQuote"/>
! <output element="tns:GetTradePricesOutput" messageLabel="out" name="Quote"/>
</operation>
! </portType>
...
</definitions>
</pre></div>
! <p> [targetNamespace] = http://example.com/stockquote</p>
! <p> [interface name] = StockQuoteInterface</p>
! <p> [operation name] = GetLastTradePrice</p>
<p> [direction token] for input is Request </p>
<p> [direction token] for output is Response</p>
<p>Applying the pattern above with these values we have:</p>
<p>input action =
! http://example.com/stockquote/StockQuoteInterface/GetLastTradePriceRequest</p>
<p>output action =
! http://example.com/stockquote/StockQuoteInterface/GetLastTradePriceResponse</p>
</div>
</div>
<div class="div3">
! <h4><a name="N104F3"></a>4.2.3 WSDL 2.0 Component Model Changes</h4>
<p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
component model:</p>
--- 798,827 ----
names.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://greath.example.com/2004/wsdl/resSvc" ...>
...
! <interface name="reservationInterface">
! <operation name="opCheckAvailability" pattern="http://www.w3.org/2006/01/wsdl/in-out">
! <input element="tns:checkAvailability" messageLabel="in" name="CheckAvailability"/>
! <output element="tns:checkAvailabilityResponse" messageLabel="out" name="Availability"/>
</operation>
! </interface>
...
</definitions>
</pre></div>
! <p> [targetNamespace] = http://greath.example.com/2004/wsdl/resSvc</p>
! <p> [interface name] = reservationInterface</p>
! <p> [operation name] = opCheckAvailability</p>
<p> [direction token] for input is Request </p>
<p> [direction token] for output is Response</p>
<p>Applying the pattern above with these values we have:</p>
<p>input action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityRequest</p>
<p>output action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityResponse</p>
</div>
</div>
<div class="div3">
! <h4><a name="N104BE"></a>4.2.3 WSDL 2.0 Component Model Changes</h4>
<p>Use of WS-Addressing adds the following REQUIRED properties to the WSDL 2.0
component model:</p>
***************
*** 958,968 ****
names.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://example.com/stockquote" ...>
...
! <portType name="StockQuotePortType">
! <operation name="GetLastTradePrice">
! <input message="tns:GetTradePricesInput" name="GetQuote"/>
! <output message="tns:GetTradePricesOutput" name="Quote"/>
! <fault message="tns:ErrorMessage" name="Error"/>
</operation>
</portType>
--- 910,920 ----
names.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://greath.example.com/2004/wsdl/resSvc" ...>
...
! <portType name="reservationInterface">
! <operation name="opCheckAvailability">
! <input message="tns:checkAvailability" name="CheckAvailability"/>
! <output message="tns:checkAvailabilityResponse" name="Availability"/>
! <fault message="tns:InvalidDate" name="InvalidDate"/>
</operation>
</portType>
***************
*** 970,983 ****
</definitions>
</pre></div>
! <p> [targetNamespace] = http://example.com/stockquote</p>
! <p> [port type name] = StockQuotePortType</p>
! <p> [input name] = GetQuote</p>
! <p> [output name] = Quote</p>
! <p> [fault name] = Error</p>
<p>Applying the pattern above with these values we have:</p>
! <p>input action = http://example.com/stockquote/StockQuotePortType/GetQuote</p>
! <p>output action = http://example.com/stockquote/StockQuotePortType/Quote</p>
<p>fault action =
! http://example.com/stockquote/StockQuotePortType/GetLastTradePrice/Fault/Error</p>
</div>
<p>WSDL defines rules for a default input or output name if the name attribute
--- 922,935 ----
</definitions>
</pre></div>
! <p> [targetNamespace] = http://greath.example.com/2004/wsdl/resSvc</p>
! <p> [port type name] = reservationInterface</p>
! <p> [input name] = CheckAvailability</p>
! <p> [output name] = CheckAvailabilityResponse</p>
! <p> [fault name] = InvalidDate</p>
<p>Applying the pattern above with these values we have:</p>
! <p>input action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/CheckAvailability</p>
! <p>output action = http://greath.example.com/2004/wsdl/resSvc/reservationInterface/Availability</p>
<p>fault action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailability/Fault/InvalidDate</p>
</div>
<p>WSDL defines rules for a default input or output name if the name attribute
***************
*** 987,996 ****
names.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://example.com/stockquote" ...>
...
! <portType name="StockQuotePortType">
! <operation name="GetLastTradePrice">
! <input message="tns:GetTradePricesInput"/>
! <output message="tns:GetTradePricesOutput"/>
</operation>
</portType>
--- 939,948 ----
names.</i></p>
<div class="exampleInner"><pre>
! <definitions targetNamespace="http://greath.example.com/2004/wsdl/resSvc" ...>
...
! <portType name="reservationInterface">
! <operation name="opCheckAvailability">
! <input message="tns:checkAvailability"/>
! <output message="tns:checkAvailabilityResponse"/>
</operation>
</portType>
***************
*** 998,1016 ****
</definitions>
</pre></div>
! <p> [targetNamespace] = http://example.com/stockquote</p>
! <p> [port type name] = StockQuotePortType</p>
<p>According to the rules defined in <a href="http://www.w3.org/TR/wsdl#_names">Section 2.4.5</a> of
WSDL 1.1, if the name attribute is absent for the input of a request
response operation the default value is the name of the operation with
"Request" appended.</p>
! <p> [input name] = GetLastTradePriceRequest</p>
<p>Likewise, the output defaults to the operation name with "Response"
appended.</p>
! <p> [output name] = GetLastTradePriceResponse</p>
<p>Applying the pattern above with these values we have:</p>
<p>input action =
! http://example.com/stockquote/StockQuotePortType/GetLastTradePriceRequest</p>
<p>output action =
! http://example.com/stockquote/StockQuotePortType/GetLastTradePriceResponse</p>
</div>
</div>
--- 950,968 ----
</definitions>
</pre></div>
! <p> [targetNamespace] = http://greath.example.com/2004/wsdl/resSvc</p>
! <p> [port type name] = reservationInterface</p>
<p>According to the rules defined in <a href="http://www.w3.org/TR/wsdl#_names">Section 2.4.5</a> of
WSDL 1.1, if the name attribute is absent for the input of a request
response operation the default value is the name of the operation with
"Request" appended.</p>
! <p> [input name] = opCheckAvailabilityRequest</p>
<p>Likewise, the output defaults to the operation name with "Response"
appended.</p>
! <p> [output name] = opCheckAvailabilityResponse</p>
<p>Applying the pattern above with these values we have:</p>
<p>input action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityRequest</p>
<p>output action =
! http://greath.example.com/2004/wsdl/resSvc/reservationInterface/opCheckAvailabilityResponse</p>
</div>
</div>
***************
*** 1573,1577 ****
<div class="div1">
! <h2><a name="references"></a>6. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
--- 1525,1543 ----
<div class="div1">
! <h2><a name="conformance"></a>6. Conformance</h2>
! <p>An endpoint reference whose wsa:Metadata element has among its children the elements
! defined in <a href="#refmetadatfromepr"><b>2.1 Referencing WSDL Metadata from an EPR</b></a> conforms to this specification if it
! 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 <a href="#uaee"><b>3.1 UsingAddressing Extension Element</b></a> or the <a href="#wsdlsoapmodule"><b>3.3 WSDL SOAP Module</b></a> markers, and obeys the structural constraints defined in
! section <a href="#indicatinguse"><b>3. Indicating Use of WS-Addressing</b></a> appropriate to that marker, and those defined
! in section <a href="#actioninwsdl"><b>4.2 Action</b></a>. </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
! constraints defined in sections <a href="#mapvaluesinwsdl"><b>4. Specifying Message Addressing Properties in WSDL</b></a> and <a href="#WSDLMEPS"><b>5. WS-Addressing and WSDL Message Exchange Patterns</b></a>. </p>
! </div>
! <div class="div1">
!
! <h2><a name="references"></a>7. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
***************
*** 1651,1655 ****
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order):
! Abbie Barbir (Nortel Networks), Andreas Bjärlestam (ERICSSON), Dave Chappell (Sonic Software), Eran Chinthaka (WSO2), Francisco Curbera (IBM Corporation), Glen Daniels (Sonic Software), Vikas Deolaliker (Sonoa Systems, Inc.), Paul Downey (BT), Jacques Durand (Fujitsu Limited), Robert Freund (Hitachi, Ltd.), Marc Goodner (Microsoft Corporation), Arun Gupta (Sun Microsystems, Inc.), Hugo Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.), David Hull (TIBCO Software, Inc.), Yin-Leng Husband (HP), David Illsley (IBM Corporation), Anish Karmarkar (Oracle Corporation), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Amelia Lewis (TIBCO Software, Inc.), Bozhong Lin (IONA Technologies, Inc.), Mark Little (JBoss Inc.), Jonathan Marsh (Microsoft Corporation), Jeff Mischkinsky (Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama (Hitachi, Ltd.), Ales Novy (Systinet Inc.), David Orchard (BEA Systems, Inc.), Gilbert Pilz (BEA Systems, Inc.), Tony Rogers (Computer Associates, Tom Rutt (Fujitsu Limited), Davanum Srinivas (WSO2), Jiri Tejkl (Systinet Inc.), Mike Vernal (Microsoft Corporation), Steve Vinoski (IONA Technologies, Inc.), Katy Warr (IBM Corporation), Pete Wenzel (Sun Microsystems, Inc.), Steve Winkler (SAP AG), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
</p>
<p>Previous members of the Working Group were:
--- 1617,1621 ----
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order):
! Abbie Barbir (Nortel Networks), Andreas Bjärlestam (ERICSSON), Dave Chappell (Sonic Software), Eran Chinthaka (WSO2), Francisco Curbera (IBM Corporation), Glen Daniels (Sonic Software), Vikas Deolaliker (Sonoa Systems, Inc.), Paul Downey (BT), Jacques Durand (Fujitsu Limited), Robert Freund (Hitachi, Ltd.), Marc Goodner (Microsoft Corporation), Arun Gupta (Sun Microsystems, Inc.), Hugo Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.), David Hull (TIBCO Software, Inc.), Yin-Leng Husband (HP), David Illsley (IBM Corporation), Anish Karmarkar (Oracle Corporation), Paul Knight (Nortel Networks), Philippe Le Hégaret (W3C/MIT), Amelia Lewis (TIBCO Software, Inc.), Bozhong Lin (IONA Technologies, Inc.), Mark Little (JBoss Inc.), Jonathan Marsh (Microsoft Corporation), Jeff Mischkinsky (Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama (Hitachi, Ltd.), Ales Novy (Systinet Inc.), David Orchard (BEA Systems, Inc.), Gilbert Pilz (BEA Systems, Inc.), Alain Regnier (Ricoh Company, Lt.), Tony Rogers (Computer Associates), Tom Rutt (Fujitsu Limited), Davanum Srinivas (WSO2), Jiri Tejkl (Systinet Inc.), Mike Vernal (Microsoft Corporation), Steve Vinoski (IONA Technologies, Inc.), Katy Warr (IBM Corporation), Pete Wenzel (Sun Microsystems, Inc.), Steve Winkler (SAP AG), Ümit Yalçinalp (SAP AG), Prasad Yendluri (webMethods, Inc.).
</p>
<p>Previous members of the Working Group were:
***************
*** 1704,1723 ****
<div class="div2">
! <h3><a name="N10D5E"></a>C.1 Changes Since Third Working Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-04-17 @ 10:27</td><td>trogers</td><td>Removed MUST from section 4.1 concerning the value of [destination] (LC130)</td></tr><tr><td>2006-04-17 @ 10:14</td><td>trogers</td><td>Marking UsingAddressing using <el> tag to show that it is not a typo in heading 3.1 (LC126)</td></tr><tr><td>2006-04-17 @ 10:05</td><td>trogers</td><td>Added the class of product specification to the Abstract (LC125)</td></tr><tr><td>2006-04-17 @ 09:46</td><td>trogers</td><td>Applied the changes required for LC120 - typo in intro and correcting wsa:Action/wsaw:Action.</td></tr><tr><td>2006-04-17 @ 09:34</td><td>trogers</td><td>Applied the changes required for LC119.</td></tr><tr><td>2006-04-17 @ 08:42</td><td>trogers</td><td>Changed the {reference parameters} property from REQUIRED to OPTIONAL in the component model. This completes LC116.</td></tr><tr><td>2006-03-27 @ 19:48</td><td>mhadley</td><td>Used alternate words instead f lowercase RFC2119 terms</td></tr><tr><td>2006-03-20 @ 15:05</td><td>mhadley</td><td>Fixed a typo in example generated fault action</td></tr><tr><td>2006-03-15 @ 22:56</td><td>trogers</td><td>Implemented the resolution of LC116: added section describing the {reference parameters} property.</td></tr><tr><td>2006-03-13 @ 13:30</td><td>trogers</td><td>Added the resolution of LC113: clarifying section 3.3 WSDL SOAP module.</td></tr><tr><td>2006-03-13 @ 13:19</td><td>trogers</td><td>Added the resolution of LC111: clarifying the {addressing required} property.</td></tr><tr><td>2006-03-13 @ 13:03</td><td>trogers</td><td>Altered changelog limit from start of 2006 to end of 2006.</td></tr><tr><td>2006-03-13 @ 12:59</td><td>trogers</td><td>Added resolution of LC109: specify that at least one of reply or fault endpoint is required on Robust In-Only</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 13:48</td><td>mhadley</td><td>Added resolution toLC115 - definition to description for WSDL 2.0</td></tr><tr><td>2006-03-03 @ 13:45</td><td>mhadley</td><td>Added resolution to LC114 - typos</td></tr><tr><td>2006-02-22 @ 14:22</td><td>mhadley</td><td>Fixed a typo: 'by by' to 'by'</td></tr><tr><td>2006-02-13 @ 20:15</td><td>mhadley</td><td>Removed ed notes</td></tr><tr><td>2006-02-13 @ 16:56</td><td>mhadley</td><td>A few grammar fixes and noted that wsaw:Anonymous with a value of optional is equivalent to the default.</td></tr><tr><td>2006-02-13 @ 16:45</td><td>mhadley</td><td>Added resolution to issue 70, soften language on defining value of [destination] to allow runtime override.</td></tr><tr><td>2006-02-13 @ 15:50</td><td>mhadley</td><td>Added resolution to issue 66, explicit note that wsaw:UsingAddressing could be used outside WSDL, e.g. in a policy framework</td></tr><tr><td>2006-01-19 @ 20:37</td><td>mhadley</td><td>Fixed some grammar errors</td></tr><tr><td>2006-01-08 @ 23:14</td><td>trogers</td><td>Umit's description of the Anonymous element added;Umit added to editor list.</td></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td>td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication/td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10D68"></a>C.2 Changes Since Second Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10D72"></a>C.3 Changes Since First Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10D7C"></a>C.4 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
--- 1670,1689 ----
<div class="div2">
! <h3><a name="N10D4E"></a>C.1 Changes Since Third Working Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-04-28 @ 13:40</td><td>trogers</td><td>Implemented the resolution of LC131, simplifying table 3.1 to remove discussion of UsingAddressing not present.</td></tr><tr><td>2006-04-28 @ 13:25</td><td>trogers</td><td>Implemented the resolution of LC129, removing the default for wsaw:Anonymous</td></tr><tr><td>2006-04-28 @ 13:09</td><td>trogers</td><td>Implemented LC124, adding Conformance section.</td></tr><tr><td>2006-04-26 @ 15:34</td><td>mhadley</td><td>Added resolution of issue lc122 - added (n..m) notation to wsaw:InterfaceName, wsaw:ServiceName and wsaw:ServiceName/@EndpointName descriptions</td></tr><tr><td>2006-04-26 @ 15:28</td><td>mhadley</td><td>Added resolution of issue lc123 - changed all the examples to be based on the one used in the WSDL 2.0 primer</td></tr><tr><td>2006-04-17 @ 10:27</td><td>trogers</td><td>Removed MUST from section 4.1 concerning the value of [destination] (LC130)</td></tr><tr<td>2006-04-17 @ 10:14</td><td>trogers</td><td>Marking UsingAddressing using <el> tag to show that it is not a typo in heading 3.1 (LC126)</td></tr><tr><td>2006-04-17 @ 10:05</td><td>trogers</td><td>Added the class of product specification to the Abstract (LC125)</td></tr><tr><td>2006-04-17 @ 09:46</td><td>trogers</td><td>Applied the changes required for LC120 - typo in intro and correcting wsa:Action/wsaw:Action.</td></tr><tr><td>2006-04-17 @ 09:34</td><td>trogers</td><td>Applied the changes required for LC119.</td></tr><tr><td>2006-04-17 @ 08:42</td><td>trogers</td><td>Changed the {reference parameters} property from REQUIRED to OPTIONAL in the component model. This completes LC116.</td></tr><tr><td>2006-03-27 @ 19:48</td><td>mhadley</td><td>Used alternate words instead of lowercase RFC2119 terms</td></tr><tr><td>2006-03-20 @ 15:05</td><td>mhadley</td><td>Fixed a typo in example generated fault action</td></tr><tr><td>2006-03-15 @ 22:56</td><td>trogers</td><td>Implemented the resolution of LC116: aded section describing the {reference parameters} property.</td></tr><tr><td>2006-03-13 @ 13:30</td><td>trogers</td><td>Added the resolution of LC113: clarifying section 3.3 WSDL SOAP module.</td></tr><tr><td>2006-03-13 @ 13:19</td><td>trogers</td><td>Added the resolution of LC111: clarifying the {addressing required} property.</td></tr><tr><td>2006-03-13 @ 13:03</td><td>trogers</td><td>Altered changelog limit from start of 2006 to end of 2006.</td></tr><tr><td>2006-03-13 @ 12:59</td><td>trogers</td><td>Added resolution of LC109: specify that at least one of reply or fault endpoint is required on Robust In-Only</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 13:48</td><td>mhadley</td><td>Added resolution to LC115 - definition to description for WSDL 2.0</td></tr><tr><td>2006-03-03 @ 13:45</td><td>mhadley</td><td>Added resolution to LC114 - typos</td></tr><tr><td>2006-02-22 @ 14:22</td><td>mhadley</td><td>Fixed a typo: 'by by' to 'by'</d></tr><tr><td>2006-02-13 @ 20:15</td><td>mhadley</td><td>Removed ed notes</td></tr><tr><td>2006-02-13 @ 16:56</td><td>mhadley</td><td>A few grammar fixes and noted that wsaw:Anonymous with a value of optional is equivalent to the default.</td></tr><tr><td>2006-02-13 @ 16:45</td><td>mhadley</td><td>Added resolution to issue 70, soften language on defining value of [destination] to allow runtime override.</td></tr><tr><td>2006-02-13 @ 15:50</td><td>mhadley</td><td>Added resolution to issue 66, explicit note that wsaw:UsingAddressing could be used outside WSDL, e.g. in a policy framework</td></tr><tr><td>2006-01-19 @ 20:37</td><td>mhadley</td><td>Fixed some grammar errors</td></tr><tr><td>2006-01-08 @ 23:14</td><td>trogers</td><td>Umit's description of the Anonymous element added; Umit added to editor list.</td></tr><tr><td>2005-11-22 @ 21:29</td><td>mhadley</td><td>Added resolution to issue 63, new subsections describing impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 7:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>trogers</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Addd clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution - expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resoluion - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10D58"></a>C.2 Changes Since Second Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-03-21 @ 23:15</td><td>mgudgin</td><td>Moved sentence on WSDL 2.0/WSDL 1.1 from Section 1.2 to Section 1</td></tr><tr><td>2005-03-10 @ 03:40</td><td>mhadley</td><td>Incorporated additional editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-10 @ 02:06</td><td>mhadley</td><td>Incorporated editorial fixes from J. Marsh.</td></tr><tr><td>2005-03-02 @ 21:22</td><td>mhadley</td><td>Fixed some problems with use of wsdli:wsdlLocation.</td></tr><tr><td>2005-03-01 @ 13:33</td><td>mhadley</td><td>Changed MUST to SHOULD in section 2.2 wrt matching port name</td></tr><tr><td>2005-02-28 @ 22:08</td><td>mhadley</td><td>Added resolution to issues 24 and 26</td></tr><tr><td>2005-02-27 @ 19:42</td><td>mhadley</td><td>Changed URI to IRI where appropriate.</td></tr><tr><td>2005-02-23 @ 16:11</td><td>mhadley</td><td>Incorporated resolution to issue 17b</td></tr><tr><td>2005-02-15 @ 23:19</td><td>mhadley</td><td>Added reolution to issue 45</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10D62"></a>C.3 Changes Since First Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2005-02-01 @ 19:49</td><td>mhadley</td><td>Removed several occurances of the word 'identify' when used with endpoint references. Replaced with 'reference' or 'address' as appropriate.</td></tr><tr><td>2005-01-25 @ 22:23</td><td>mhadley</td><td>Added descriptive text for wsa:Action attribute. Fixed references to WSDL 1.1 to be more explicit version-wise.</td></tr><tr><td>2005-01-24 @ 10:12</td><td>mgudgin</td><td>Incorporated resolution of i034 and i035; default action URI for WSDL 2.0 and default action URI for faults. All edits in section 3</td></tr><tr><td>2005-01-18 @ 04:01</td><td>mgudgin</td><td>Modified text in Section 2 WRT closing issue i020</td></tr><tr><td>2004-12-16 @ 18:20</td><td>mhadley</td><td>Added resolution to issue 19 - WSDL version neutrality</td></tr><tr><td>2004-12-16 @ 16:50</td><td>mhadley</td><td>Added issue 33 resolution</td></tr><tr><td>2004-12-14 @ 20:10</td><td>mhadley</td><td>Swtched back to edcopy formatting</td></tr><tr><td>2004-12-14 @ 20:02</td><td>mhadley</td><td>Enhanced auto-changelog generation to allow specification of data ranges for logs. Split change log to show changes between early draft and first working draft and changes since first working draft.</td></tr><tr><td>2004-12-14 @ 18:13</td><td>mhadley</td><td>Added resolutions for issues 12 (EPR lifecycle), 37 (relationship from QName to URI) and 39 (spec name versioning)</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10D6C"></a>C.4 Changes Since Submission</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2004-12-04 @ 02:04</td><td>mgudgin</td><td>Added text to section on WSDL MEPs per resolution of Issue i003</td></tr><tr><td>2004-11-23 @ 21:38</td><td>mhadley</td><td>Updated titles of examples. Fixed table formatting and references. Replaced uuid URIs with http URIs in examples. Added document status.</td></tr><tr><td>2004-11-11 @ 18:31</td><td>mgudgin</td><td>
Added some TBD sections</td></tr><tr><td>2004-11-07 @ 02:03</td><td>mhadley</td><td>Second more detailed run through to separate core, SOAP and WSDL document contents. Removed dependency on WS-Policy. Removed references to WS-Trust and WS-SecurityPolicy</td></tr><tr><td>2004-11-02 @ 21:45</td><td>mhadley</td><td>Replaced hardcoded change log with one generated dynamically from CVS</td></tr><tr><td>2004-10-28 @ 18:09</td><td>mhadley</td><td>Fixed typo in abstract</td></tr><tr><td>2004-10-28 @ 17:05</td><td>mhadley</td><td>Initial cut of separating specification into core, soap and wsdl</td></tr></table>
Received on Friday, 28 April 2006 13:44:46 UTC