- From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 03 Jan 2007 13:20:39 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv13319
Modified Files:
ws-addr-wsdl.html
Log Message:
Updated to show latest Editor's Draft
Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -C 2 -d -r1.47 -r1.48
*** ws-addr-wsdl.html 4 May 2006 12:34:47 -0000 1.47
--- ws-addr-wsdl.html 3 Jan 2007 13:20:37 -0000 1.48
***************
*** 1,4 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
! <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - WSDL Binding</title><style type="text/css">
code { font-family: monospace; }
--- 1,4 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
! <html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - Metadata</title><style type="text/css">
code { font-family: monospace; }
***************
*** 45,51 ****
div.exampleHeader { font-weight: bold;
margin: 4px}
! </style><link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/base.css"><link rel="alternate" title="" href="" type=""><link rel="contents" href="#contents"></head><body>
<div class="head">
! <h1>Web Services Addressing 1.0 - WSDL Binding</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ws-addr-wsdl.html">ws-addr-wsdl.html</a>
--- 45,51 ----
div.exampleHeader { font-weight: bold;
margin: 4px}
! </style><link type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/base.css"><link type="" href="" title="" rel="alternate"><link href="#contents" rel="contents"></head><body>
<div class="head">
! <h1>Web Services Addressing 1.0 - Metadata</h1>
<h2>Editors' copy $Date$ @@ @@@@ @@@@</h2><dl><dt>This version:</dt><dd>
<a href="ws-addr-wsdl.html">ws-addr-wsdl.html</a>
***************
*** 53,57 ****
<a href="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl">http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl</a>
</dd><dt>Previous versions:</dt><dd>
! <a href="http://www.w3.org/TR/2005/WD-ws-addr-wsdl-20050413">http://www.w3.org/TR/2005/WD-ws-addr-wsdl-20050413</a>
</dd><dt>Editors:</dt>
<dd>Martin Gudgin, Microsoft Corp</dd>
--- 53,57 ----
<a href="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl">http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl</a>
</dd><dt>Previous versions:</dt><dd>
! <a href="http://www.w3.org/TR/2006/WD-ws-addr-wsdl-20060216/">http://www.w3.org/TR/2006/WD-ws-addr-wsdl-20060216/</a>
</dd><dt>Editors:</dt>
<dd>Martin Gudgin, Microsoft Corp</dd>
***************
*** 62,66 ****
<h2><a name="abstract">Abstract</a></h2>
<p>Web Services Addressing provides transport-neutral mechanisms to address Web services
! and messages. Web Services Addressing 1.0 - WSDL Binding (this document) defines how the abstract
properties defined in Web Services Addressing 1.0 - Core are described using WSDL.</p>
<p>The classes of products for which this specification is designed to be relevant
--- 62,66 ----
<h2><a name="abstract">Abstract</a></h2>
<p>Web Services Addressing provides transport-neutral mechanisms to address Web services
! and messages. Web Services Addressing 1.0 - Metadata (this document) defines how the abstract
properties defined in Web Services Addressing 1.0 - Core are described using WSDL.</p>
<p>The classes of products for which this specification is designed to be relevant
***************
*** 70,82 ****
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="#N66272">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="#eprinendpoint">Extending WSDL Endpoints with an EPR</a><br> 4.1.1 <a href="#N66471">WSDL 2.0 Component Model Changes</a><br> 4.2 <a href="#destinwsdl">Destination</a><br> 4.3 <a href="#refpinwsdl">Reference Parameters</a><br> 4.4 <a href="#actioninwsdl">Action</a><br> 4.4.1 <a href="#explicitaction">Explicit Association</a><br> 4.4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.4.3 <a href="#N66808">WSDL 2.0 Component Model hanges</a><br> 4.4.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</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>&nsp; 5.2.3 <a href="#wsdl20inout">In-out</a><br> 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> 7.1 <a href="#N68579">Normative</a><br> 7.2 <a href="#N68882">Informative</a><br></p>
! <h3><a name="appendix" id="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="#N68999">Changes Since Last Call Working Draft</a><br> C.2 <a href="#N69009">Changes Since Third Working Draft</a><br> C.3 <a href="#N69019">Changes Since Second Working Draft</a><br> C.4 <a href="#N69029">Changes Since First Working Draft</a><br> C.5 <a href="#N69039">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2>
! <p>Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>] defines a set of abstract
properties and an XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] representation thereof to
reference Web service endpoints and to facilitate end-to-end addressing of endpoints
! in messages. Web Services Addressing 1.0 - WSDL Binding (this document) defines how the abstract
properties defined in Web Services Addressing 1.0 - Core are described using WSDL. WS-Addressing
is designed to be able to work with WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0</a></cite>] and also (for
--- 70,82 ----
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="#N102E0">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="#eprinendpoint">Extending WSDL Endpoints with an EPR</a><br> 4.1.1 <a href="#N103A7">WSDL 2.0 Component Model Changes</a><br> 4.2 <a href="#destinwsdl">Destination</a><br> 4.3 <a href="#refpinwsdl">Reference Parameters</a><br> 4.4 <a href="#actioninwsdl">Action</a><br> 4.4.1 <a href="#explicitaction">Explicit Association</a><br> 4.4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.4.3 <a href="#N104FB">WSDL 2.0 Component Model hanges</a><br> 4.4.4 <a href="#defactionwsdl11"> Default Action Pattern for WSDL 1.1</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>&nsp; 5.2.3 <a href="#wsdl20inout">In-out</a><br> 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> 7.1 <a href="#N10BEC">Normative</a><br> 7.2 <a href="#N10D2B">Informative</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="#N10DA0">Changes Since Candidate Recommendation Draft</a><br> C.2 <a href="#N10DAA">Changes Since Last Call Working Draft</a><br> C.3 <a href="#N10DB4">Changes Since Third Working Draft</a><br> C.4 <a href="#N10DBE">Changes Since Second Working Draft</a><br> C.5 <a href="#N10DC8">Changes Since First Working Draft</a><br> C.6 <a href="#N10DD2">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
<h2><a name="tocRange"></a>1. Introduction</h2>
! <p>Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing Core</a></cite>] defines a set of abstract
properties and an XML Infoset [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>] representation thereof to
reference Web service endpoints and to facilitate end-to-end addressing of endpoints
! in messages. Web Services Addressing 1.0 - Metadata (this document) defines how the abstract
properties defined in Web Services Addressing 1.0 - Core are described using WSDL. WS-Addressing
is designed to be able to work with WSDL 2.0 [<cite><a href="#WSDL20">WSDL 2.0</a></cite>] and also (for
***************
*** 131,135 ****
<tr>
<td rowspan="1" colspan="1">wsoap</td>
! <td rowspan="1" colspan="1"> </td>
</tr>
<tr>
--- 131,135 ----
<tr>
<td rowspan="1" colspan="1">wsoap</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/2006/01/wsdl/soap </td>
</tr>
<tr>
***************
*** 156,167 ****
</tbody>
</table><br>
! <p>The working group intends to update the value of the Web Services Addressing 1.0 - WSDL Binding
namespace URI each time a new version of this document is published until such
time that the document reaches Candidate Recommendation status. Once it has
reached Candidate Recommendation status, the working group intends to maintain
! the value of the Web Services Addressing 1.0 - WSDL Binding namespace URI that was assigned in the
Candidate Recommendation unless significant changes are made that impact the
implementation of the specification.</p>
! <p>WS-Addressing is defined in terms of the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. WS-Addressing can be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] as described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. The examples in this specification use an XML 1.0
[<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is not a requirement.</p>
<p>All information items defined by this specification are identified by the XML
--- 156,167 ----
</tbody>
</table><br>
! <p>The working group intends to update the value of the Web Services Addressing 1.0 - Metadata
namespace URI each time a new version of this document is published until such
time that the document reaches Candidate Recommendation status. Once it has
reached Candidate Recommendation status, the working group intends to maintain
! the value of the Web Services Addressing 1.0 - Metadata namespace URI that was assigned in the
Candidate Recommendation unless significant changes are made that impact the
implementation of the specification.</p>
! <p>WS-Addressing is defined in terms of the XML Information Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]. WS-Addressing can be used with SOAP [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>, <cite><a href="#SOAP11">SOAP 1.1</a></cite>] as described in Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>]. The examples in this specification use an XML 1.0
[<cite><a href="#XML10">XML 1.0</a></cite>] representation but this is not a requirement.</p>
<p>All information items defined by this specification are identified by the XML
***************
*** 218,222 ****
"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 style="text-align: left" class="exampleHead"><i><span>Example 2-1. </span>Example endpoint reference.</i></p>
<div class="exampleInner"><pre>
<wsa:EndpointReference
--- 218,222 ----
"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>
<div class="exampleInner"><pre>
<wsa:EndpointReference
***************
*** 257,261 ****
an embedded description is undefined.</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
<div class="exampleInner"><pre>
<wsa:EndpointReference
--- 257,261 ----
an embedded description is undefined.</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 2-2. </span>An EPR containing WSDL 2.0 metadata</i></p>
<div class="exampleInner"><pre>
<wsa:EndpointReference
***************
*** 285,289 ****
</div>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
<div class="exampleInner"><pre>
<wsa:EndpointReference
--- 285,289 ----
</div>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 2-3. </span>An EPR containing WSDL 1.1 metadata</i></p>
<div class="exampleInner"><pre>
<wsa:EndpointReference
***************
*** 349,354 ****
<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 Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing-Core</a></cite>], applicable WS-Addressing protocol bindings (e.g.
! Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]), and this specification,
and MUST follow all applicable WS-Addressing normative requirements. </p>
<p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding
--- 349,354 ----
<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 Web Services Addressing 1.0 - Core[<cite><a href="#WSADDR-CORE">WS-Addressing Core</a></cite>], applicable WS-Addressing protocol bindings (e.g.
! Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>]), and this specification,
and MUST follow all applicable WS-Addressing normative requirements. </p>
<p>The wsaw:UsingAddressing element SHOULD appear as a child of the wsdl:binding
***************
*** 360,367 ****
non-anonymous URIs as addresses in an EPR. Specifically, when included in a SOAP
binding, the wsaw:UsingAddressing marker identifies the use of Web Services
! Addressing 1.0 bound to SOAP as defined by Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>].The presence of this element can extend the semantics
of the endpoint's WSDL binding. </p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
<div class="exampleInner"><pre><binding name="reservationSOAPBinding"
interface="tns:reservationInterface"
--- 360,367 ----
non-anonymous URIs as addresses in an EPR. Specifically, when included in a SOAP
binding, the wsaw:UsingAddressing marker identifies the use of Web Services
! Addressing 1.0 bound to SOAP as defined by Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>].The presence of this element can extend the semantics
of the endpoint's WSDL binding. </p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Indicating use of WS-Addressing using wsaw:UsingAddressing in WSDL 2.0</i></p>
<div class="exampleInner"><pre><binding name="reservationSOAPBinding"
interface="tns:reservationInterface"
***************
*** 375,379 ****
</div>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><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">
--- 375,379 ----
</div>
<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">
***************
*** 435,439 ****
<div class="div3">
! <h4><a name="N66272"></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 and that of related
--- 435,439 ----
<div class="div3">
! <h4><a name="N102E0"></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 and that of related
***************
*** 480,484 ****
<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>
--- 480,484 ----
<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 Binding</a></cite>] MUST be generated. </p>
</li>
<li>
***************
*** 487,491 ****
<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>
--- 487,491 ----
<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 Binding</a></cite>]
MUST be generated. </p>
</li>
***************
*** 494,498 ****
in WSDL 1.1, or as a binding operation extension element in WSDL 2.0.</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><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" />
--- 494,498 ----
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" />
***************
*** 551,558 ****
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 Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] and is identified with the following URI:
http://www.w3.org/2005/08/addressing/module</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 3-4. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
<div class="exampleInner"><pre><binding name="reservationSOAPBinding"
interface="tns:reservationInterface"
--- 551,558 ----
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 Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>] and is identified with the following URI:
http://www.w3.org/2005/08/addressing/module</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Indicating use of WS-Addressing using wsoap:module in WSDL 2.0</i></p>
<div class="exampleInner"><pre><binding name="reservationSOAPBinding"
interface="tns:reservationInterface"
***************
*** 588,592 ****
<div class="div3">
! <h4><a name="N66471"></a>4.1.1 WSDL 2.0 Component Model Changes</h4>
<p>Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0
component model:</p>
--- 588,592 ----
<div class="div3">
! <h4><a name="N103A7"></a>4.1.1 WSDL 2.0 Component Model Changes</h4>
<p>Use of WS-Addressing adds the following OPTIONAL properties to the WSDL 2.0
component model:</p>
***************
*** 645,654 ****
extension on the WSDL input, output and fault elements. A SOAP binding can
specify SOAPAction values for the input messages of operations. In the
! absence of a wsaw:Action attribute on a WSDL input element where a
SOAPAction value is specified, the value of the [action] property for the
! input message is the value of the SOAPAction specified.
! Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>] specifies restrictions
! on the relationship between the values of [action] and SOAPAction for SOAP
! 1.1 and SOAP 1.2.</p>
<p>The inclusion of wsaw:Action without inclusion of wsaw:UsingAddressing has no
normative intent and is only informational. In other words, the inclusion of
--- 645,659 ----
extension on the WSDL input, output and fault elements. A SOAP binding can
specify SOAPAction values for the input messages of operations. In the
! absence of a wsaw:Action attribute on a WSDL input element where a non-empty
SOAPAction value is specified, the value of the [action] property for the
! input message is the value of the SOAPAction specified. If the wsaw:Action
! attribute is absent, and SOAPAction is not specified, or is empty, then the
! default pattern is used. Note that the SOAPAction value is not required to
! be an absolute IRI, but the [action] property is required to be an absolute
! IRI; if wsaw:UsingAddressing is present, wsaw:Action is not specified, and
! the SOAPAction value is not empty or an absolute IRI, then the document MUST
! be considered invalid. Web Services Addressing 1.0 - SOAP Binding[<cite><a href="#WSADDR-SOAP">WS-Addressing SOAP Binding</a></cite>]
! specifies restrictions on the relationship between the values of [action]
! and SOAPAction for SOAP 1.1 and SOAP 1.2.</p>
<p>The inclusion of wsaw:Action without inclusion of wsaw:UsingAddressing has no
normative intent and is only informational. In other words, the inclusion of
***************
*** 662,666 ****
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><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" ...>
--- 667,671 ----
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
! <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" ...>
***************
*** 683,687 ****
http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse.</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><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" ...>
--- 688,692 ----
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" ...>
***************
*** 708,716 ****
<h4><a name="defactionwsdl20"></a>4.4.2 Default Action Pattern for WSDL 2.0</h4>
! <p>In the absence of the wsa:Action attribute, the following pattern is used in
! WSDL 2.0 documents to construct a default action for inputs and outputs. The
! general form of an action URI is as follows:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][interface name][delimiter][operation name][direction token]
--- 713,722 ----
<h4><a name="defactionwsdl20"></a>4.4.2 Default Action Pattern for WSDL 2.0</h4>
! <p>In the absence of an explicitly specified value for the [action] property
! (see section <a href="#explicitaction"><b>4.4.1 Explicit Association</b></a>), the following pattern is used
! in WSDL 2.0 documents to construct a default action for inputs and outputs.
! The general form of an action URI is as follows:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-3. </span>Structure of defaulted wsa:Action IRI in WSDL 2.0.</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][interface name][delimiter][operation name][direction token]
***************
*** 719,723 ****
<p>For fault messages, the general form of an action IRI is as follows:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][interface name][delimiter][fault name]
--- 725,729 ----
<p>For fault messages, the general form of an action IRI is as follows:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-4. </span>Structure of default wsa:Action IRI for faults</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][interface name][delimiter][fault name]
***************
*** 808,812 ****
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
names.</i></p>
<div class="exampleInner"><pre>
--- 814,818 ----
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-5. </span>Example WSDL without explicit wsa:Action values with explicit message
names.</i></p>
<div class="exampleInner"><pre>
***************
*** 836,840 ****
<div class="div3">
! <h4><a name="N66808"></a>4.4.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>
--- 842,846 ----
<div class="div3">
! <h4><a name="N104FB"></a>4.4.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>
***************
*** 843,849 ****
<p>A property of the Interface Message Reference and Interface Fault
components named {action}. The property is of type xs:anyURI. The
! property value is the value of the wsaw:Action attribute information
! item, if present; otherwise the default value computed following the
! rules from section <a href="#defactionwsdl20"><b>4.4.2 Default Action Pattern for WSDL 2.0</b></a>.</p>
</li>
</ul>
--- 849,855 ----
<p>A property of the Interface Message Reference and Interface Fault
components named {action}. The property is of type xs:anyURI. The
! property value is either explicitly specified, as described in
! section <a href="#explicitaction"><b>4.4.1 Explicit Association</b></a>, or the default value
! computed following the rules from section <a href="#defactionwsdl20"><b>4.4.2 Default Action Pattern for WSDL 2.0</b></a>.</p>
</li>
</ul>
***************
*** 853,861 ****
<h4><a name="defactionwsdl11"></a>4.4.4 Default Action Pattern for WSDL 1.1</h4>
<p>A default pattern is also defined for backwards compatibility with WSDL 1.1.
! In the absence of the wsaw:Action attribute, the following pattern is used
to construct a default action for inputs and outputs. The general form of an
action IRI is as follows:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][port type name][delimiter][input|output name]
--- 859,868 ----
<h4><a name="defactionwsdl11"></a>4.4.4 Default Action Pattern for WSDL 1.1</h4>
<p>A default pattern is also defined for backwards compatibility with WSDL 1.1.
! In the absence of an explicitly specified value for the [action] property
! (see section <a href="#explicitaction"><b>4.4.1 Explicit Association</b></a>), the following pattern is used
to construct a default action for inputs and outputs. The general form of an
action IRI is as follows:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-6. </span>Structure of defaulted wsa:Action IRI.</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][port type name][delimiter][input|output name]
***************
*** 864,868 ****
<p>For fault messages, the general form of an action IRI is as follows:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][port type name][delimiter][operation name][delimiter]Fault[delimiter][fault name]
--- 871,875 ----
<p>For fault messages, the general form of an action IRI is as follows:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-7. </span>Structure of default wsa:Action IRI for faults</i></p>
<div class="exampleInner"><pre>
[target namespace][delimiter][port type name][delimiter][operation name][delimiter]Fault[delimiter][fault name]
***************
*** 919,923 ****
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
names.</i></p>
<div class="exampleInner"><pre>
--- 926,930 ----
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-8. </span>Example WSDL without explicit wsa:Action values with explicit message
names.</i></p>
<div class="exampleInner"><pre>
***************
*** 950,954 ****
is not present. Consider the following example:</p>
<div class="exampleOuter">
! <p style="text-align: left" class="exampleHead"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message
names.</i></p>
<div class="exampleInner"><pre>
--- 957,961 ----
is not present. Consider the following example:</p>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 4-9. </span>Example WSDL without explicit wsa:Action values or explicit message
names.</i></p>
<div class="exampleInner"><pre>
***************
*** 1530,1541 ****
<div class="div2">
! <h3><a name="N68579"></a>7.1 Normative</h3>
<dl>
! <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing-Core] </dt><dd>
! <cite><a href="ws-addr-core.html">Web Services Addressing 1.0 - Core</a></cite>, M. Gudgin, M. Hadley, T. Rogers,
! Editors.</dd>
! <dt class="label"><a name="WSADDR-SOAP"></a>[WS-Addressing-SOAP] </dt><dd>
! <cite><a href="ws-addr-soap.html">Web Services Addressing 1.0 - SOAP Binding</a></cite>, M. Gudgin, M. Hadley, T. Rogers,
! Editors.</dd>
<dt class="label"><a name="WSDL20"></a>[WSDL 2.0] </dt><dd>
<cite><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060106/">Web Services Description Language (WSDL) Version 2.0 Part 1: Core
--- 1537,1560 ----
<div class="div2">
! <h3><a name="N10BEC"></a>7.1 Normative</h3>
<dl>
! <dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
! <cite><a href="http://www.w3.org/TR/2006/REC-ws-addr-core-20060509">Web Services Addressing 1.0 - Core</a></cite>, M. Gudgin, M. Hadley,
! and T. Rogers, Editors. World Wide Web Consortium,
! 9 May 2006. This version of the
! WS-Addressing Core Recommendation is
! http://www.w3.org/TR/2006/REC-ws-addr-core-20060509. The <a href="http://www.w3.org/TR/ws-addr-core">latest version of
! WS-Addressing Core</a> is available at
! http://www.w3.org/TR/ws-addr-core.
! </dd>
! <dt class="label"><a name="WSADDR-SOAP"></a>[WS-Addressing SOAP Binding] </dt><dd>
! <cite><a href="http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509">Web Services Addressing 1.0 - SOAP Binding</a></cite>, M. Gudgin, M. Hadley,
! and T. Rogers, Editors. World Wide Web Consortium,
! 9 May 2006. This version of the
! WS-Addressing Core Recommendation is
! http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509. The <a href="http://www.w3.org/TR/ws-addr-soap">latest version of
! WS-Addressing SOAP Binding</a> is available at
! http://www.w3.org/TR/ws-addr-soap.
! </dd>
<dt class="label"><a name="WSDL20"></a>[WSDL 2.0] </dt><dd>
<cite><a href="http://www.w3.org/TR/2006/CR-wsdl20-20060106/">Web Services Description Language (WSDL) Version 2.0 Part 1: Core
***************
*** 1609,1613 ****
<div class="div2">
! <h3><a name="N68882"></a>7.2 Informative</h3>
<dl>
<dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
--- 1628,1632 ----
<div class="div2">
! <h3><a name="N10D2B"></a>7.2 Informative</h3>
<dl>
<dt class="label"><a name="WS-Security"></a>[WS-Security] </dt><dd> OASIS, <cite><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">Web Services Security: SOAP Message Security</a></cite>,
***************
*** 1678,1702 ****
<div class="div2">
! <h3><a name="N68999"></a>C.1 Changes Since Last Call Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-05-04 @ 12:33</td><td>mhadley</td><td>Split the references into normative and informative, fixed a few editorial glitches</td></tr><tr><td>2006-04-28 @ 15:09</td><td>mhadley</td><td>Added new change log section for LC issues</td></tr><tr><td>2006-04-28 @ 15:04</td><td>mhadley</td><td>Incorporated resolution to issue lc132 - reworked section 4 to allow use of EPRs as WSDL endpoint/port extensions</td></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 (..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 {refeence 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: 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 o 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'</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N69009"></a>C.2 Changes Since Third Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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 imacts 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>005-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 editoria 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="N69019"></a>C.3 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="N69029"></a>C.4 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="N69039"></a>C.5 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>
--- 1697,1726 ----
<div class="div2">
! <h3><a name="N10DA0"></a>C.1 Changes Since Candidate Recommendation Draft</h3>
! <table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2007-01-03 @ 12:28</td><td>trogers</td><td>Implemented the resolution of CR30 - SOAPAction not empty or absolute IRI makes the document invalid</td></tr><tr><td>2007-01-03 @ 11:38</td><td>trogers</td><td>Implemented CR26 and CR28 about the rules for populating the [action] property.</td></tr></table>
! </div>
! <div class="div2">
!
! <h3><a name="N10DAA"></a>C.2 Changes Since Last Call Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></tr><tr><td>2006-05-04 @ 12:33</td><td>mhadley</td><td>Split the references into normative and informative, fixed a few editorial glitches</td></tr><tr><td>2006-04-28 @ 15:09</td><td>mhadley</td><td>Added new change log section for LC issues</td></tr><tr><td>2006-04-28 @ 15:04</td><td>mhadley</td><td>Incorporated resolution to issue lc132 - reworked section 4 to allow use of EPRs as WSDL endpoint/port extensions</td></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 (..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 {refeence 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: 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 o 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'</td></tr></table>
</div>
<div class="div2">
! <h3><a name="N10DB4"></a>C.3 Changes Since Third Working Draft</h3>
<table border="1"><tr><th>Date</th><th>Editor</th><th>Description</th></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 imacts 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>005-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 editoria 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="N10DBE"></a>C.4 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="N10DC8"></a>C.5 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="N10DD2"></a>C.6 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 Wednesday, 3 January 2007 13:20:57 UTC