- From: Tony Rogers via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 30 Jan 2007 10:47:34 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv12929
Modified Files:
ws-addr-wsdl.html
Log Message:
Adjusted definitions of response assertions, Replaced section 3.1.4 (moved to 3.1.6 and changed content)
Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.53
retrieving revision 1.54
diff -C 2 -d -r1.53 -r1.54
*** ws-addr-wsdl.html 29 Jan 2007 09:41:06 -0000 1.53
--- ws-addr-wsdl.html 30 Jan 2007 10:47:32 -0000 1.54
***************
*** 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="#wspolicyassertions">WS-Policy Assertions</a><br> 3.1.1 <a href="#wspolicyaddressing">Addressing Assertion</a><br> 3.1.2 <a href="#wspolicyanonresponses">AnonymousResponses Assertion</a><br> 3.1.3 <a href="#wspolicynonanonresponses">NonAnonymousResponsesAssertion</a><br> 3.1.4 <a href="#usingbothnestedassertions">Using both AnonymousResponses and NonAnonymousResponses</a><br> 3.1.5 <a href="#policyexamplesincompact">Examples (Compact Form)</a><br> 3.1.6 <a href="#policyassertionsinnormal">Examples (Normal Form)</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="#N102F5">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="#N10449">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="#wsdl11solicitresponse">Solicit-response</a><br> 5.2 <a href="#WSDL20MEPS">WSDL 2.0 Message xchange 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> 7.1 <a href="#N10B37">Normative</a><br> 7.2 <a href="#N10CA8">nformative</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="#N10D36">Changes Since Candidate Recommendation Draft</a><br> C.2 <a href="#N10D40">Changes Since Last Call Working Draft</a><br> C.3 <a href="#N10D4A">Changes Since Third Working Draft</a><br> C.4 <a href="#N10D54">Changes Since Second Working Draft</a><br> C.5 <a href="#N10D5E">Changes Since First Working Draft</a><br> C.6 <a href="#N10D68">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="#wspolicyassertions">WS-Policy Assertions</a><br> 3.1.1 <a href="#wspolicyaddressing">Addressing Assertion</a><br> 3.1.2 <a href="#wspolicyanonresponses">AnonymousResponses Assertion</a><br> 3.1.3 <a href="#wspolicynonanonresponses">NonAnonymousResponsesAssertion</a><br> 3.1.4 <a href="#policyexamplesincompact">Examples (Compact Form)</a><br> 3.1.5 <a href="#policyassertionsinnormal">Examples (Normal Form)</a><br> 3.1.6 <a href="#usingintersection">Finding Compatible Policies</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="#N1032A">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> &bsp; 4.4.2 <a href="#defactionwsdl20">Default Action Pattern for WSDL 2.0</a><br> 4.4.3 <a href="#N1047E">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="#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="#wsdl20outoptionalin">Out-optional-in</a><br>6. <a href="#conformance">Conformance</a><br>7. <a href="#references"> References</a><br> 7.1 <a href="#N10B6C">Normative</a><br> 7.2 <a href="#N10CDD">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="#N10D6B">Changes Since Candidate Recommendation Draft</a><br> C.2 <a href="#N10D75">Changes Since Last Call Working Draft</a><br> C.3 <a href="#N10D7F">Changes Since Third Working Draft</a><br> C.4 <a href="#N10D89">Changes Since Second Working Draft</a><br> C.5 <a href="#N10D93">Changes Since First Working Draft</a><br> C.6 <a href="#N10D9D">Changes Since Submission</a><br></p></div><hr><div class="body">
<div class="div1">
***************
*** 323,327 ****
<h3><a name="wspolicyassertions"></a>3.1 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>The mechanism for indicating that a binding or endpoint conforms to the
WS-Addressing specification is through the use of the Web Services Policy -
--- 323,326 ----
***************
*** 348,360 ****
<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
! anonymous URI as an address; it simply indicates the lack of any affirmation
! of support for anonymous URIs. </p>
<p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
value of [address] in place of the anonymous URI; this value MUST be
--- 347,361 ----
<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.</p>
! <p> The appearance of this element within a policy alternative indicates that
! the endpoint expresses explicit support for request messages with response
! endpoint EPRs that contain the anonymous URI
("http://www.w3.org/2005/08/addressing/anonymous") as the value of
! [address]. In other words, the endpoint guarantees support for anonymous responses.</p>
! <p> 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 anonymous URI
! as an address; it simply indicates the lack of any affirmation of support
! for anonymous URIs. </p>
<p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
value of [address] in place of the anonymous URI; this value MUST be
***************
*** 366,407 ****
<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
! element within a policy alternative indicates that the endpoint will accept
! request messages with response endpoint EPRs that contain something other
! than the anonymous URI as the value of [address]. This assertion is
! deliberately vague; its presence indicates that a non-anonymous addresses
! might be accepted but doesn't constrain what such an address might look
! 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>
<p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
! value of [address] in place of a non-anonymous address; this value MUST be accepted.</p>
! </div>
! <div class="div3">
!
! <h4><a name="usingbothnestedassertions"></a>3.1.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
! an alternative without either assertion. </p>
! <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">We will be providing a rationale for the use of Optional in
! connection with the nested assertions, explaining how the assertions are
! used by the server and the client. We may also rephrase the description
! of the assertions to help that explanation.</td></tr></table>
</div>
<div class="div3">
! <h4><a name="policyexamplesincompact"></a>3.1.5 Examples (Compact Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
--- 367,392 ----
<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.</p>
! <p> The appearance of this element within a policy alternative indicates that
! the endpoint expresses explicit support for request messages with response
! endpoint EPRs that contain something other than the anonymous URI as the
! value of [address]. In other words, the endpoint guarantees support for
! non-anonymous responses. This assertion is deliberately vague; its presence
! indicates that some non-anonymous addresses will be accepted but doesn't
! constrain what such an address might look 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. </p>
! <p>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; it simply
! indicates the lack of any affirmation of support for them. </p>
<p>The None URI ("http://www.w3.org/2005/08/addressing/none") may appear as the
! value of [address] in place of a non-anonymous address; this value MUST be
! accepted.</p>
</div>
<div class="div3">
! <h4><a name="policyexamplesincompact"></a>3.1.4 Examples (Compact Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-1. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
***************
*** 457,461 ****
<div class="div3">
! <h4><a name="policyassertionsinnormal"></a>3.1.6 Examples (Normal Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
--- 442,446 ----
<div class="div3">
! <h4><a name="policyassertionsinnormal"></a>3.1.5 Examples (Normal Form)</h4>
<div class="exampleOuter">
<p class="exampleHead" style="text-align: left"><i><span>Example 3-6. </span>Subject supports WS-Addressing, no statement on supported response EPRs</i></p>
***************
*** 590,593 ****
--- 575,656 ----
</div>
</div>
+ <div class="div3">
+
+ <h4><a name="usingintersection"></a>3.1.6 Finding Compatible Policies</h4>
+ <p>When a client is looking for an endpoint with compatible policy, one common
+ method used is to take the policy intersection between the policy which the
+ client is looking for, and the policy asserted in the WSDL document; a
+ non-empty intersection is sought. The policy used by the client must be
+ written carefully to avoid unexpected results. This is most obvious when the
+ client is not looking for explicit support of a particular kind of response;
+ failing to take care could mean missing a compatible policy.</p>
+ <p>Consider the following example, where we have a client who does not care
+ whether the endpoint explicitly supports anonymous responses, and a WSDL
+ which states that the endpoint does explicitly support anonymous
+ responses.</p>
+ <div class="exampleOuter">
+ <p class="exampleHead" style="text-align: left"><i><span>Example 3-11. </span>Client looking for an endpoint which supports Addressing, WSDL states explicit support for anonymous responses</i></p>
+ <div class="exampleInner"><pre><wsp:Policy>
+ <wsam:Addressing>
+ <wsp:Policy/>
+ </wsam:Addressing>
+ </wsp:Policy></pre></div>
+ <p>The client's policy (above) states the requirement for Addressing, but no
+ requirement for explicit support of responses.</p>
+ <div class="exampleInner"><pre><wsp:Policy>
+ <wsam:Addressing>
+ <wsp:Policy>
+ <wsam:AnonymousResponses/>
+ </wsp:Policy>
+ </wsam:Addressing>
+ </wsp:Policy></pre></div>
+ <p>The policy attached to the endpoint in the WSDL (above) states explicit support
+ for anonymous responses. The intersection of this policy with the
+ client's policy will be empty, so the client will miss a compatible
+ endpoint.</p>
+ <div class="exampleInner"><pre><wsp:Policy>
+ <wsam:Addressing>
+ <wsp:Policy>
+ <wsam:AnonymousResponses wsp:Optional="true"/>
+ </wsp:Policy>
+ </wsam:Addressing>
+ </wsp:Policy></pre></div>
+ <p>This is what the client's policy could be; by stating that the
+ wsam:AnonymousResponses assertion is optional, there will be a non-empty
+ intersection with endpoint policies that do and do not contain this
+ assertion.</p>
+ </div>
+ <p>Now let us consider a variation on this same situation, where the WSDL marks its explicit
+ support of anonymous responses as ignorable.</p>
+ <div class="exampleOuter">
+ <p class="exampleHead" style="text-align: left"><i><span>Example 3-12. </span>Client looking for an endpoint which supports Addressing, WSDL states (ignorable) explicit support for anonymous responses</i></p>
+ <div class="exampleInner"><pre><wsp:Policy>
+ <wsam:Addressing>
+ <wsp:Policy/>
+ </wsam:Addressing>
+ </wsp:Policy></pre></div>
+ <p>The client's policy (above) states the requirement for Addressing, but no
+ requirement for explicit support of responses.</p>
+ <div class="exampleInner"><pre><wsp:Policy>
+ <wsam:Addressing>
+ <wsp:Policy>
+ <wsam:AnonymousResponses wsp:Ignorable="true"/>
+ </wsp:Policy>
+ </wsam:Addressing>
+ </wsp:Policy></pre></div>
+ <p>The policy attached to the endpoint in the WSDL (above) states explicit
+ support for anonymous responses, but marks that as an ignorable
+ assertion. Now the result of the policy intersection with the client's
+ policy will depend on whether the client is using lax or strict
+ intersection. The strict intersection of this policy with the client's
+ policy will still be empty. The lax intersection, on the other hand,
+ will not be empty, so the client will find a compatible endpoint.</p>
+ </div>
+ <p>These two examples show the use of wsp:Optional and wsp:Ignorable, and how
+ they can be used to produce non-empty intersections between client and
+ endpoint policies. For more detailed descriptions of the use of
+ wsp:Optional, wsp:Ignorable, and strict and lax intersection, please refer
+ to the WS-Policy Primer [<cite><a href="#WSPolicyPrimer">WS Policy 1.5 - Primer</a></cite>].</p>
+ </div>
</div>
</div>
***************
*** 611,615 ****
<div class="div3">
! <h4><a name="N102F5"></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>
--- 674,678 ----
<div class="div3">
! <h4><a name="N1032A"></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>
***************
*** 864,868 ****
<div class="div3">
! <h4><a name="N10449"></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>
--- 927,931 ----
<div class="div3">
! <h4><a name="N1047E"></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>
***************
*** 1559,1563 ****
<div class="div2">
! <h3><a name="N10B37"></a>7.1 Normative</h3>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
--- 1622,1626 ----
<div class="div2">
! <h3><a name="N10B6C"></a>7.1 Normative</h3>
<dl>
<dt class="label"><a name="WSADDR-CORE"></a>[WS-Addressing Core] </dt><dd>
***************
*** 1662,1666 ****
<div class="div2">
! <h3><a name="N10CA8"></a>7.2 Informative</h3>
<dl>
<dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
--- 1725,1729 ----
<div class="div2">
! <h3><a name="N10CDD"></a>7.2 Informative</h3>
<dl>
<dt class="label"><a name="WSPolicyPrimer"></a>[WS Policy 1.5 - Primer] </dt><dd>
***************
*** 1738,1743 ****
<div class="div2">
! <h3><a name="N10D36"></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-29 @ 09:37</td><td>trogers</td><td>Corrected the captions on examples 3-5 and 3-10</td></tr><tr><td>2007-01-22 @ 22:58</td><td>trogers</td><td>Corrected message label case in example 4-5 - editorial</td></tr><tr><td>2007-01-22 @ 22:45</td><td>trogers</td><td>Implemented editorial changes resulting from 23Jan telecon.
Implemented CR40 and CR42.</td></tr><tr><td>2007-01-14 @ 20:31</td><td>trogers</td><td>removed UsingAddressing and SOAP module, updated conformance to suit, added None URI as acceptable</td></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>
--- 1801,1806 ----
<div class="div2">
! <h3><a name="N10D6B"></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-30 @ 10:44</td><td>trogers</td><td>Adjusted definitions of response assertions, Replaced section 3.1.4 (moved to 3.1.6 and changed content)</td></tr><tr><td>2007-01-29 @ 09:37</td><td>trogers</td><td>Corrected the captions on examples 3-5 and 3-10</td></tr><tr><td>2007-01-22 @ 22:58</td><td>trogers</td><td>Corrected message label case in example 4-5 - editorial</td></tr><tr><td>2007-01-22 @ 22:45</td><td>trogers</td><td>Implemented editorial changes resulting from 23Jan telecon.
Implemented CR40 and CR42.</td></tr><tr><td>2007-01-14 @ 20:31</td><td>trogers</td><td>removed UsingAddressing and SOAP module, updated conformance to suit, added None URI as acceptable</td></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>
***************
*** 1745,1769 ****
<div class="div2">
! <h3><a name="N10D40"></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="N10D4A"></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="N10D54"></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="N10D5E"></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="N10D68"></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>
--- 1808,1832 ----
<div class="div2">
! <h3><a name="N10D75"></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="N10D7F"></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="N10D89"></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="N10D93"></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="N10D9D"></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 Tuesday, 30 January 2007 10:47:39 UTC