- From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 10 Jan 2007 11:33:23 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv29743
Modified Files:
ws-addr-wsdl.html
Log Message:
updated to show changes made to Metadata document
Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -C 2 -d -r1.49 -r1.50
*** ws-addr-wsdl.html 5 Jan 2007 14:23:30 -0000 1.49
--- ws-addr-wsdl.html 10 Jan 2007 11:33:21 -0000 1.50
***************
*** 63,67 ****
<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
include WSDL and WS-Addressing EPR consumers.</p>
--- 63,68 ----
<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, and how
! WS-Policy can be used to indicate the support of WS-Addressing by a Web service.</p>
<p>The classes of products for which this specification is designed to be relevant
include WSDL and WS-Addressing EPR consumers.</p>
***************
*** 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.2 <a href="#wspolicyassertions">WS-Policy Assertions</a><br> 3.2.1 <a href="#wspolicyaddressing">Addressing Assertion</a><br> &nbp; 3.2.2 <a href="#wspolicyanonresponses">AnonymousResponses Assertion</a><br> 3.2.3 <a href="#wspolicynonanonresponses">NonAnonymousResponses Assertion</a><br> 3.2.4 <a href="#N10323">Examples (Compact Form)</a><br> 3.2.5 <a href="#N1035B">Examples (Normal Form)</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="#N103C4">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>&bsp; 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="#N10518">WSDL 2.0 Component Model Changes</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="#wsdl11soliciresponse">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> 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> &bsp; 7.1 <a href="#N10C09">Normative</a><br> 7.2 <a href="#N10D93">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="#N10E08">Changes Since Candidate Recommendation Draft</a><br> C.2 <a href="#N10E12">Changes Since Last Call Working Draft</a><br> C.3 <a href="#N10E1C">Changes Since Third Working Draft</a><br> C.4 <a href="#N10E26">Changes Since Second Working Draft</a><br> C.5 <a href="#N10E30">Changes Since First Working Draft</a><br> C.6 <a href="#N10E3A">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
--- 71,76 ----
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.2 <a href="#wspolicyassertions">WS-Policy Assertions</a><br> 3.2.1 <a href="#wspolicyaddressing">Addressing Assertion</a><br> &nbp; 3.2.2 <a href="#wspolicyanonresponses">AnonymousResponses Assertion</a><br> 3.2.3 <a href="#wspolicynonanonresponses">NonAnonymousResponses Assertion</a><br> 3.2.4 <a href="#N10336">Using both AnonymousResponses and NonAnonymousResponses</a><br> 3.2.5 <a href="#N10345">Examples (Compact Form)</a><br> 3.2.6 <a href="#N1037D">Examples (Normal Form)</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="#N103E6">WSDL 2.0 Component Model Changes</a><br> 4.2 <a href="#destinwsdl">Destination</a><br> &nbs; 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="#N1053A">WSDL 2.0 Component Model Changes</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> &nbp;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> 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="#wsdl2outoptionalin">Out-optional-in</a><br>6. <a href="#conformance">Conformance</a><br>7. <a href="#references"> References</a><br> 7.1 <a href="#N10C2B">Normative</a><br> 7.2 <a href="#N10D9C">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="#N10E2A">Changes Since Candidate Recommendation Draft</a><br> C.2 <a href="#N10E34">Changes Since Last Call Working Draft</a><br> C.3 <a href="#N10E3E">Changes Since Third Working Draft</a><br> C.4 <a href="#N10E48">Changes Since Second Working Draft</a><br> C.5 <a href="#N10E52">Changes Since First Working Draft</a><br> C.6 <a href="#N10E5C">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 126,131 ****
</tr>
<tr>
! <td rowspan="1" colspan="1">wsaw</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/@@@@/@@/addressing/wsdl </td>
</tr>
<tr>
--- 127,132 ----
</tr>
<tr>
! <td rowspan="1" colspan="1">wsam</td>
! <td rowspan="1" colspan="1"> http://www.w3.org/@@@@/@@/addressing/metadata </td>
</tr>
<tr>
***************
*** 154,157 ****
--- 155,162 ----
<td rowspan="1" colspan="1">http://schemas.xmlsoap.org/wsdl/soap/</td>
</tr>
+ <tr>
+ <td rowspan="1" colspan="1">wsp</td>
+ <td rowspan="1" colspan="1">http://www.w3.org/2006/07/ws-policy</td>
+ </tr>
</tbody>
</table><br>
***************
*** 166,170 ****
[<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
! namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] "http://www.w3.org/@@@@/@@/addressing/wsdl". A normative XML
Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document can
be obtained by dereferencing the XML namespace URI.</p>
--- 171,175 ----
[<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
! namespace URI [<cite><a href="#XMLNS">XML Namespaces</a></cite>] "http://www.w3.org/@@@@/@@/addressing/metadata". A normative XML
Schema [<cite><a href="#XMLSchemaP1">XML Schema Structures</a></cite>, <cite><a href="#XMLSchemaP2">XML Schema Datatypes</a></cite>] document can
be obtained by dereferencing the XML namespace URI.</p>
***************
*** 184,188 ****
<dl>
! <dt class="label"> wsaw:InterfaceName (0..1)</dt>
<dd>
<p>A QName identifying a description of the sequences of messages that a
--- 189,193 ----
<dl>
! <dt class="label"> wsam:InterfaceName (0..1)</dt>
<dd>
<p>A QName identifying a description of the sequences of messages that a
***************
*** 194,198 ****
! <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"> wsam:ServiceName (0..1)</dt>
<dd>
<p>A QName that identifies the set of endpoints at which a particular
***************
*** 203,207 ****
! <dt class="label"> wsaw:ServiceName/@EndpointName (0..1)</dt>
<dd>
<p>An NCName that identifies one endpoint amongst the set identified by
--- 208,212 ----
! <dt class="label"> wsam:ServiceName/@EndpointName (0..1)</dt>
<dd>
<p>An NCName that identifies one endpoint amongst the set identified by
***************
*** 227,231 ****
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>
--- 232,236 ----
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">
! <wsam:InterfaceName>ghns:reservationInterface</wsam:InterfaceName>
</wsa:Metadata>
</wsa:EndpointReference></pre></div>
***************
*** 317,321 ****
<h3><a name="uaee"></a>3.1 <code>UsingAddressing</code> Extension Element</h3>
! <p> WS-Addressing defines an empty global element, wsaw:UsingAddressing, that can be
used to indicate that an endpoint conforms to the WS-Addressing specification.
The wsdl:required attribute MAY be used to indicate whether WS-Addressing
--- 322,326 ----
<h3><a name="uaee"></a>3.1 <code>UsingAddressing</code> Extension Element</h3>
! <p> WS-Addressing defines an empty global element, wsam:UsingAddressing, that can be
used to indicate that an endpoint conforms to the WS-Addressing specification.
The wsdl:required attribute MAY be used to indicate whether WS-Addressing
***************
*** 325,329 ****
how the use of addressing is indicated in the WSDL. </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>
--- 330,334 ----
how the use of addressing is indicated in the WSDL. </p>
<a name="mappresence"></a><table border="1">
! <caption>Table 3-1. MAPs Present in output message when wsam:UsingAddressing is present</caption>
<thead>
<tr>
***************
*** 352,372 ****
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
! element. Alternatively, the wsaw:UsingAddressing element MAY instead be included
as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
indicate compliance with WS-Addressing for a specific endpoint only.</p>
! <p>The inclusion of the wsaw:UsingAddressing element indicates that the applicable
WS-Addressing specifications are supported and allows use of anonymous or
non-anonymous URIs as addresses in an EPR. Specifically, when included in a SOAP
! binding, the 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"
type="http://www.w3.org/2006/01/wsdl/soap"
wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
! <wsaw:UsingAddressing wsdl:required="true" />
<operation ref="tns:opCheckAvailability"
wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" />
--- 357,377 ----
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 wsam:UsingAddressing element SHOULD appear as a child of the wsdl:binding
! element. Alternatively, the wsam:UsingAddressing element MAY instead be included
as a child of the wsdl20:endpoint (or wsdl11:port) when an endpoint intends to
indicate compliance with WS-Addressing for a specific endpoint only.</p>
! <p>The inclusion of the wsam:UsingAddressing element indicates that the applicable
WS-Addressing specifications are supported and allows use of anonymous or
non-anonymous URIs as addresses in an EPR. Specifically, when included in a SOAP
! binding, the wsam:UsingAddressing marker identifies the use of Web Services
Addressing 1.0 bound to SOAP as defined by 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 wsam:UsingAddressing in WSDL 2.0</i></p>
<div class="exampleInner"><pre><binding name="reservationSOAPBinding"
interface="tns:reservationInterface"
type="http://www.w3.org/2006/01/wsdl/soap"
wsoap:protocol="http://www.w3.org/2003/05/soap/bindings/HTTP">
! <wsam:UsingAddressing wsdl:required="true" />
<operation ref="tns:opCheckAvailability"
wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response" />
***************
*** 375,383 ****
</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">
<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" />
--- 380,388 ----
</div>
<div class="exampleOuter">
! <p class="exampleHead" style="text-align: left"><i><span>Example 3-2. </span>Indicating use of WS-Addressing using wsam: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" />
! <wsam:UsingAddressing wsdl:required="true" />
<operation name="opCheckAvailability">
<soap:operation soapaction="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability" />
***************
*** 416,420 ****
<tr>
<td rowspan="1" colspan="1">{addressing}</td>
! <td rowspan="1" colspan="1"> If a <code>wsaw:UsingAddresing</code> extension element is present: <ul>
<li>
<p>if a <code>wsdl:required</code> <em>attribute information item</em> is present
--- 421,425 ----
<tr>
<td rowspan="1" colspan="1">{addressing}</td>
! <td rowspan="1" colspan="1"> If a <code>wsam:UsingAddresing</code> extension element is present: <ul>
<li>
<p>if a <code>wsdl:required</code> <em>attribute information item</em> is present
***************
*** 437,448 ****
<h3><a name="wspolicyassertions"></a>3.2 WS-Policy Assertions</h3>
! <p>Another mechanism for indicating that a binding or endpoint <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">open issue on policy attachment options</td></tr></table> conforms to the WS-Addressing specification is through the use of the
Web Services Policy - Framework [<cite><a href="#WSPolicy">WS Policy 1.5 - Framework</a></cite>] and Web Services
Policy - Attachment [<cite><a href="#WSPolicyAttachment">WS Policy 1.5 - Attachment</a></cite>] specifications. This
! specification defines the following three policy assertions.</p>
<div class="div3">
<h4><a name="wspolicyaddressing"></a>3.2.1 Addressing Assertion</h4>
! <p>The wsaw:Addressing policy assertion is a nested policy container assertion.
The meaning of this assertion when present in a policy alternative is that
WS-Addressing is required to communicate with the subject. In order to
--- 442,457 ----
<h3><a name="wspolicyassertions"></a>3.2 WS-Policy Assertions</h3>
! <table border="1" summary="Editorial note"><tr><td width="50%" valign="top" align="left"><b>Editorial note</b></td><td width="50%" valign="top" align="right"> </td></tr><tr><td valign="top" align="left" colspan="2">open issue on policy attachment options</td></tr></table>
! <p>Another mechanism for indicating that a binding or endpoint conforms to the WS-Addressing specification is through the use of the
Web Services Policy - Framework [<cite><a href="#WSPolicy">WS Policy 1.5 - Framework</a></cite>] and Web Services
Policy - Attachment [<cite><a href="#WSPolicyAttachment">WS Policy 1.5 - Attachment</a></cite>] specifications. This
! specification defines three policy assertions.</p>
! <p>For WSDL 1.1, these assertions may be attached to <code>wsdl11:port</code> or
! <code>wsdl11:binding</code>. For WSDL 2.0, they may be attached to
! <code>wsdl20:endpoint</code> or <code>wsdl20:binding</code>.</p>
<div class="div3">
<h4><a name="wspolicyaddressing"></a>3.2.1 Addressing Assertion</h4>
! <p>The wsam:Addressing policy assertion is a nested policy container assertion.
The meaning of this assertion when present in a policy alternative is that
WS-Addressing is required to communicate with the subject. In order to
***************
*** 455,465 ****
<h4><a name="wspolicyanonresponses"></a>3.2.2 AnonymousResponses Assertion</h4>
! <p>The wsaw:AnonymousResponses element MAY be used as a policy assertion nested
! within the wsaw:Addressing assertion in accordance with the rules laid down
by WS-Policy Framework 1.5 section 4.3.2. The appearance of this element
within a policy alternative indicates that the endpoint will accept request
messages with response endpoint EPRs that contain the anonymous URI
("http://www.w3.org/2005/08/addressing/anonymous") as the value of
! [address]. The absence of the wsaw:AnonymousResponses policy assertion
within a policy alternative does <b>not</b> indicate that the endpoint will
not accept request messages with response endpoint EPRs that contain the
--- 464,474 ----
<h4><a name="wspolicyanonresponses"></a>3.2.2 AnonymousResponses Assertion</h4>
! <p>The wsam:AnonymousResponses element MAY be used as a policy assertion nested
! within the wsam:Addressing assertion in accordance with the rules laid down
by WS-Policy Framework 1.5 section 4.3.2. The appearance of this element
within a policy alternative indicates that the endpoint will accept request
messages with response endpoint EPRs that contain the anonymous URI
("http://www.w3.org/2005/08/addressing/anonymous") as the value of
! [address]. The absence of the wsam:AnonymousResponses policy assertion
within a policy alternative does <b>not</b> indicate that the endpoint will
not accept request messages with response endpoint EPRs that contain the
***************
*** 470,474 ****
<h4><a name="wspolicynonanonresponses"></a>3.2.3 NonAnonymousResponses Assertion</h4>
! <p>The wsaw:NonAnonymousResponses element MAY be used as a policy assertion
nested within the Addressing assertion in accordance with the rules laid
down by WS-Policy Framework 1.5 section 4.3.2. The appearance of this
--- 479,483 ----
<h4><a name="wspolicynonanonresponses"></a>3.2.3 NonAnonymousResponses Assertion</h4>
! <p>The wsam:NonAnonymousResponses element MAY be used as a policy assertion
nested within the Addressing assertion in accordance with the rules laid
down by WS-Policy Framework 1.5 section 4.3.2. The appearance of this
***************
*** 480,495 ****
like. A receiver can still reject a request that contains an address that it
doesn't understand or that requires a binding it doesn't support. As with
! the other assertions, the absence of the wsaw:NonAnonymousResponses policy
assertion within a policy alternative does <b>not</b> indicate that the
endpoint will not accept request messages with response endpoint EPRs that
contain something other than the anonymous URI address. </p>
!
! <p>NOTE: If both AnonymousResponses and NonAnonymousResponses are supported and the
! intention is to allow either to be used care should be taken to ensure there is
! an alternative which includes just AnonymousResponses as a nested assertion and
! an alternative with just NonAnonymousResponses as a nested assertion so that a
! subject which supports only one will have a compatible policy [<cite><a href="#WSPolicyPrimer">WS Policy 1.5 - Primer</a></cite> section 3.4].</p>
! <p> Also, given that the lack of either of these assertions (AnonymousResponses and
! NonAnonymousResponses) does not indicate lack of support, it is suggested that a
subject that does not have a strict compatibility requirement that an
interacting subject understands or is concerned with these assertions provides
--- 489,509 ----
like. A receiver can still reject a request that contains an address that it
doesn't understand or that requires a binding it doesn't support. As with
! the other assertions, the absence of the wsam:NonAnonymousResponses policy
assertion within a policy alternative does <b>not</b> indicate that the
endpoint will not accept request messages with response endpoint EPRs that
contain something other than the anonymous URI address. </p>
! </div>
! <div class="div3">
!
! <h4><a name="N10336"></a>3.2.4 Using both AnonymousResponses and NonAnonymousResponses</h4>
! <p>If both AnonymousResponses and NonAnonymousResponses are supported, and the
! intention is to allow either to be used, care should be taken to ensure that
! there are alternatives such that a subject which supports only one will have
! a compatible policy [<cite><a href="#WSPolicyPrimer">WS Policy 1.5 - Primer</a></cite> section 3.4]. There
! should be at least an alternative which includes just AnonymousResponses as
! a nested assertion and an alternative with just NonAnonymousResponses as a
! nested assertion.</p>
! <p>Note also that the lack of either of these assertions (AnonymousResponses and
! NonAnonymousResponses) does not indicate lack of support. So it is suggested that a
subject that does not have a strict compatibility requirement that an
interacting subject understands or is concerned with these assertions provides
***************
*** 498,508 ****
<div class="div3">
! <h4><a name="N10323"></a>3.2.4 Examples (Compact Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsaw:Addressing wsp:Optional="true">
! <wsp:Policy></wsp:Policy>
! </wsaw:Addressing>
</wsp:Policy></pre></div>
</div>
--- 512,522 ----
<div class="div3">
! <h4><a name="N10345"></a>3.2.5 Examples (Compact Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-3. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsam:Addressing wsp:Optional="true">
! <wsp:Policy/>
! </wsam:Addressing>
</wsp:Policy></pre></div>
</div>
***************
*** 510,516 ****
<p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Subject requires WS-Addressing, no statement on supported response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsaw:Addressing>
! <wsp:Policy></wsp:Policy>
! </wsaw:Addressing>
</wsp:Policy></pre></div>
</div>
--- 524,530 ----
<p class="exampleHead" style="text-align: left"><i><span>Example 3-4. </span>Subject requires WS-Addressing, no statement on supported response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy/>
! </wsam:Addressing>
</wsp:Policy></pre></div>
</div>
***************
*** 518,527 ****
<p class="exampleHead" style="text-align: left"><i><span>Example 3-5. </span>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsaw:Addressing wsp:Optional="true">
<wsp:Policy>
! <wsaw:AnonymousResponses wsp:Optional="true"/>
! <wsaw:NonAnonymousResponses wsp:Optional="true"/>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:Policy></pre></div>
</div>
--- 532,541 ----
<p class="exampleHead" style="text-align: left"><i><span>Example 3-5. </span>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsam:Addressing wsp:Optional="true">
<wsp:Policy>
! <wsam:AnonymousResponses wsp:Optional="true"/>
! <wsam:NonAnonymousResponses wsp:Optional="true"/>
</wsp:Policy>
! </wsam:Addressing>
</wsp:Policy></pre></div>
</div>
***************
*** 529,540 ****
<p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
! <wsaw:AnonymousResponses wsp:Optional="true"/>
! <wsaw:NonAnonymousResponses wsp:Optional="true"/>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:Policy></pre></div>
</div>
--- 543,554 ----
<p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
! <wsam:AnonymousResponses wsp:Optional="true"/>
! <wsam:NonAnonymousResponses wsp:Optional="true"/>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:Policy></pre></div>
</div>
***************
*** 542,550 ****
<p class="exampleHead" style="text-align: left"><i><span>Example 3-7. </span>Subject requires WS-Addressing and use of non-anonymous response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsaw:Addressing>
<wsp:Policy>
! <wsaw:NonAnonymousResponses/>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:Policy></pre></div>
</div>
--- 556,564 ----
<p class="exampleHead" style="text-align: left"><i><span>Example 3-7. </span>Subject requires WS-Addressing and use of non-anonymous response EPRs</i></p>
<div class="exampleInner"><pre><wsp:Policy>
! <wsam:Addressing>
<wsp:Policy>
! <wsam:NonAnonymousResponses/>
</wsp:Policy>
! </wsam:Addressing>
</wsp:Policy></pre></div>
</div>
***************
*** 552,556 ****
<div class="div3">
! <h4><a name="N1035B"></a>3.2.5 Examples (Normal Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-8. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
--- 566,570 ----
<div class="div3">
! <h4><a name="N1037D"></a>3.2.6 Examples (Normal Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-8. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
***************
*** 559,563 ****
<wsp:All/>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
--- 573,577 ----
<wsp:All/>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
***************
*** 565,569 ****
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
</wsp:ExactlyOne>
--- 579,583 ----
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
</wsp:ExactlyOne>
***************
*** 575,579 ****
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
--- 589,593 ----
<wsp:ExactlyOne>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
***************
*** 581,585 ****
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
</wsp:ExactlyOne>
--- 595,599 ----
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
</wsp:ExactlyOne>
***************
*** 592,596 ****
<wsp:All/>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
--- 606,610 ----
<wsp:All/>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
***************
*** 598,636 ****
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:AnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:AnonymousResponses/>
! <wsaw:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
</wsp:ExactlyOne>
--- 612,650 ----
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:AnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:AnonymousResponses/>
! <wsam:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
</wsp:ExactlyOne>
***************
*** 642,665 ****
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:AnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
</wsp:ExactlyOne>
--- 656,679 ----
<wsp:ExactlyOne>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:AnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
</wsp:ExactlyOne>
***************
*** 671,683 ****
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsaw:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsaw:Addressing>
</wsp:All>
</wsp:ExactlyOne>
--- 685,697 ----
<wsp:ExactlyOne>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
! </wsam:Addressing>
</wsp:All>
</wsp:ExactlyOne>
***************
*** 707,711 ****
<operation ref="tns:opCheckAvailability"
wsoap:mep="http://www.w3.org/2003/05/soap/mep/request-response">
- <wsaw:Anonymous>required</wsaw:Anonymous>
</operation>
<fault ref="tns:invalidDataFault" wsoap:code="soap:Sender" />
--- 721,724 ----
***************
*** 733,737 ****
<div class="div3">
! <h4><a name="N103C4"></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>
--- 746,750 ----
<div class="div3">
! <h4><a name="N103E6"></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>
***************
*** 785,813 ****
<h4><a name="explicitaction"></a>4.4.1 Explicit Association</h4>
! <p>WS-Addressing defines a global attribute, wsaw:Action, that can be used to
explicitly define the value of the [action] property for messages in a WSDL
description. The type of the attribute is xs:anyURI and it is used as an
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
! wsaw:Action attributes 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
! wsaw:UsingAddressing. Other specifications defining the value of [action]
! are under no constraint to be consistent with wsaw:Action.</p>
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
--- 798,826 ----
<h4><a name="explicitaction"></a>4.4.1 Explicit Association</h4>
! <p>WS-Addressing defines a global attribute, wsam:Action, that can be used to
explicitly define the value of the [action] property for messages in a WSDL
description. The type of the attribute is xs:anyURI and it is used as an
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 wsam: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 wsam: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 wsam:UsingAddressing is present, wsam: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 wsam:Action without inclusion of wsam:UsingAddressing has no
normative intent and is only informational. In other words, the inclusion of
! wsam:Action attributes 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
! wsam:UsingAddressing. Other specifications defining the value of [action]
! are under no constraint to be consistent with wsam:Action.</p>
<p>For example consider the following WSDL excerpt:</p>
<div class="exampleOuter">
***************
*** 819,825 ****
<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>
--- 832,838 ----
<operation name="opCheckAvailability" pattern="http://www.w3.org/2006/01/wsdl/in-out">
<input element="tns:checkAvailability" messageLabel="In"
! wsam:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability"/>
<output element="tns:checkAvailabilityResponse" messageLabel="Out"
! wsam:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse"/>
</operation>
</interface>
***************
*** 840,846 ****
<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>
--- 853,859 ----
<operation name="opCheckAvailability">
<input message="tns:checkAvailability"
! wsam:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailability"/>
<output message="tns:checkAvailabilityResponse"
! wsam:Action="http://greath.example.com/2004/wsdl/resSvc/opCheckAvailabilityResponse"/>
</operation>
</portType>
***************
*** 987,991 ****
<div class="div3">
! <h4><a name="N10518"></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>
--- 1000,1004 ----
<div class="div3">
! <h4><a name="N1053A"></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>
***************
*** 1670,1674 ****
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.4 Action</b></a>. </p>
--- 1683,1687 ----
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="#wspolicyassertions"><b>3.2 WS-Policy Assertions</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.4 Action</b></a>. </p>
***************
*** 1682,1686 ****
<div class="div2">
! <h3><a name="N10C09"></a>7.1 Normative</h3>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
--- 1695,1699 ----
<div class="div2">
! <h3><a name="N10C2B"></a>7.1 Normative</h3>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
***************
*** 1728,1738 ****
Attachment is http://www.w3.org/TR/2006/WD-ws-policy-attach-20061117. The <a href="http://www.w3.org/TR/ws-policy-attach">latest version of WS Policy
Attachment</a> is available at http://www.w3.org/TR/ws-policy-attach </dd>
- <dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
- <cite><a href="http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018/">Web Services Policy 1.5 - Attachment</a></cite>, Asir S Vedamuthu,
- David Orchard, Maryann Hondo, Toufic Boubez, Prasad Yendluri, Editors. World
- Wide Web Consortium, 18 November 2006. This version of the WS-Policy Primer
- is http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018. The <a href="http://www.w3.org/TR/ws-policy-primer">latest version of WS Policy
- Primer</a> is available at http://www.w3.org/TR/ws-policy-primer
- </dd>
<dt class="label"><a name="RFC2119"></a>[IETF RFC 2119] </dt><dd>
<cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words for use in RFCs to Indicate Requirement
--- 1741,1744 ----
***************
*** 1792,1797 ****
<div class="div2">
! <h3><a name="N10D93"></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>,
March 2004.</dd>
--- 1798,1810 ----
<div class="div2">
! <h3><a name="N10D9C"></a>7.2 Informative</h3>
<dl>
+ <dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
+ <cite><a href="http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018/">Web Services Policy 1.5 - Primer</a></cite>, Asir S Vedamuthu,
+ David Orchard, Maryann Hondo, Toufic Boubez, Prasad Yendluri, Editors. World
+ Wide Web Consortium, 18 November 2006. This version of the WS-Policy Primer
+ is http://www.w3.org/TR/2006/WD-ws-policy-primer-20061018. The <a href="http://www.w3.org/TR/ws-policy-primer">latest version of WS Policy
+ Primer</a> is available at http://www.w3.org/TR/ws-policy-primer
+ </dd>
<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>,
March 2004.</dd>
***************
*** 1830,1834 ****
for 1.0 [action] and 2004-08 [action]. </p>
<p>However, when describing services in WSDL, the namespace of the Action attribute used
! to associate values with WSDL operations differs in the two versions (wsaw:Action
versus wsa200408:Action), and the default action pattern in WS-Addressing 1.0
differs in two respects from that in the 2004-08 version: the [delimiter] can be
--- 1843,1847 ----
for 1.0 [action] and 2004-08 [action]. </p>
<p>However, when describing services in WSDL, the namespace of the Action attribute used
! to associate values with WSDL operations differs in the two versions (wsam:Action
versus wsa200408:Action), and the default action pattern in WS-Addressing 1.0
differs in two respects from that in the 2004-08 version: the [delimiter] can be
***************
*** 1852,1856 ****
<ol>
<li>
! <p>specifying wsaw:Action explicitly when the message is a fault.</p>
</li>
</ol>
--- 1865,1869 ----
<ol>
<li>
! <p>specifying wsam:Action explicitly when the message is a fault.</p>
</li>
</ol>
***************
*** 1861,1890 ****
<div class="div2">
! <h3><a name="N10E08"></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-05 @ 14:20</td><td>trogers</td><td>Implemented the resolutions of CR33 and CR44: policy assertions for using addressing and anon/non-anon responses</td></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="N10E12"></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="N10E1C"></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="N10E26"></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="N10E30"></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="N10E3A"></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>
--- 1874,1904 ----
<div class="div2">
! <h3><a name="N10E2A"></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-10 @ 11:26</td><td>trogers</td><td>Changed the namespace and namespace prefix for this document
! Corrected introduction and conformance section</td></tr><tr><td>2007-01-05 @ 14:20</td><td>trogers</td><td>Implemented the resolutions of CR33 and CR44: policy assertions for using addressing and anon/non-anon responses</td></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="N10E34"></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="N10E3E"></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="N10E48"></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="N10E52"></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="N10E5C"></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, 10 January 2007 11:33:39 UTC