- From: Philippe Le Hegaret via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 26 Apr 2007 12:35:02 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv15714
Modified Files:
ws-addr-wsdl.html ws-addr-wsdl.xml
Log Message:
lc134 with "Add to Section 3 the language " This assertion implies support for ws-addr core and soap binding."
Index: ws-addr-wsdl.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.xml,v
retrieving revision 1.116
retrieving revision 1.117
diff -C 2 -d -r1.116 -r1.117
*** ws-addr-wsdl.xml 31 Jan 2007 15:23:32 -0000 1.116
--- ws-addr-wsdl.xml 26 Apr 2007 12:34:59 -0000 1.117
***************
*** 161,165 ****
<p>WS-Addressing is defined in terms of the XML Information Set [<bibref
ref="XMLInfoSet"/>]. WS-Addressing can be used with SOAP [<bibref
! ref="SOAP12-PART1"/>, <bibref ref="SOAP11"/>] as described in &wsa-soap.title;[<bibref
ref="WSADDR-SOAP"/>]. The examples in this specification use an XML 1.0
[<bibref ref="XML10"/>] representation but this is not a requirement.</p>
--- 161,165 ----
<p>WS-Addressing is defined in terms of the XML Information Set [<bibref
ref="XMLInfoSet"/>]. WS-Addressing can be used with SOAP [<bibref
! ref="SOAP12-PART1"/>, <bibref ref="SOAP11"/>] as described in &wsa-soap.title; [<bibref
ref="WSADDR-SOAP"/>]. The examples in this specification use an XML 1.0
[<bibref ref="XML10"/>] representation but this is not a requirement.</p>
***************
*** 318,350 ****
[<bibref ref="WSPolicyAttachment"/>] specifications. This specification
defines three policy assertions.</p>
! <p>For WSDL 1.1, these assertions may be attached to <code>wsdl11:port</code> or
! <code>wsdl11:binding</code>. For WSDL 2.0, they may be attached to
! <code>wsdl20:endpoint</code> or <code>wsdl20:binding</code>.</p>
! <div3 id="wspolicyaddressing">
<head>Addressing Assertion</head>
! <p>The wsam:Addressing policy assertion is a nested policy container assertion.
The meaning of this assertion, when present in a policy alternative, is that
! WS-Addressing is required to communicate with the subject. In order to
indicate that the subject supports WS-Addressing but does not require its
use, an additional policy alternative should be provided which does not
contain this assertion. This may be done in WS-Policy compact form by adding
! the attribute wsp:Optional="true" to the wsam:Addressing assertion. </p>
</div3>
<div3 id="wspolicyanonresponses">
<head>AnonymousResponses Assertion</head>
! <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
accepted.</p>
--- 318,366 ----
[<bibref ref="WSPolicyAttachment"/>] specifications. This specification
defines three policy assertions.</p>
! <p>The <code>wsam:Addressing</code> policy assertion applies to the endpoint policy subject.</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>. A policy
! expression containing the wsam:Addressing
! policy assertion MUST NOT be attached to a
! <code>wsdl:portType</code> or
! <code>wsdl20:interface</code>. The
! <code>wsam:Addressing</code> policy assertion specifies a
! concrete behavior whereas the
! <code>wsdl:portType</code> or
! <code>wsdl20:interface</code> is an abstract
! construct.
! </p>
! <div3 id="wspolicyaddressing">
<head>Addressing Assertion</head>
! <p>The <code>wsam:Addressing</code> 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. The <code>wsam:Addressing</code>
! assertion indicates that there are no restrictions on the use of WS-Addressing
! unless otherwise qualified by assertions in its nested policy expression. In order to
indicate that the subject supports WS-Addressing but does not require its
use, an additional policy alternative should be provided which does not
contain this assertion. This may be done in WS-Policy compact form by adding
! the attribute <code>wsp:Optional="true"</code> to the <code>wsam:Addressing</code> assertion. </p>
! <p>The inclusion of this assertion implies
! support for the &wsa-core.title; [<bibref
! ref="WSADDR-CORE"/>] and &wsa-soap.title; [<bibref
! ref="WSADDR-SOAP"/>].</p>
</div3>
<div3 id="wspolicyanonresponses">
<head>AnonymousResponses Assertion</head>
! <p>The <code>wsam:AnonymousResponses</code> element MAY be used as a policy assertion nested
! within the <code>wsam:Addressing</code> assertion in accordance with the rules laid down
! by <xspecref href='http://www.w3.org/TR/2007/CR-ws-policy-20070330/#Policy_Assertion_Nesting'>policy assertion nesting</xspecref> ([<bibref ref="WSPolicy"/>], section 4.3.2).</p>
! <p> The appearance of this element within the <code>wsam:Addressing</code> policy assertion indicates that
! the endpoint requires request messages to use response
endpoint EPRs that contain the anonymous URI
! ("<code>http://www.w3.org/2005/08/addressing/anonymous</code>") as the value of
! [address]. In other words, the endpoint requires the use of anonymous responses.</p>
! <p>The None URI ("<code>http://www.w3.org/2005/08/addressing/none</code>") may appear as the
value of [address] in place of the anonymous URI; this value MUST be
accepted.</p>
***************
*** 352,362 ****
<div3 id="wspolicynonanonresponses">
<head>NonAnonymousResponses Assertion</head>
! <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
--- 368,379 ----
<div3 id="wspolicynonanonresponses">
<head>NonAnonymousResponses Assertion</head>
! <p>The <code>wsam:NonAnonymousResponses</code> element MAY be used as a policy assertion
nested within the Addressing assertion in accordance with the rules laid
! down by <xspecref href='http://www.w3.org/TR/2007/CR-ws-policy-20070330/#Policy_Assertion_Nesting'>policy assertion nesting</xspecref> ([<bibref ref="WSPolicy"/>], section 4.3.2). The <code>wsam:NonAnonymousResponses</code> policy assertion
! MUST NOT be used in the same policy alternative as the <code>wsam:AnonymousResponses</code> policy assertion.</p>
! <p> The appearance of this element within the <code>wsam:Addressing</code> assertion indicates that
! the endpoint expresses requires request messages to use response
endpoint EPRs that contain something other than the anonymous URI as the
! value of [address]. In other words, the endpoint requires the use of
non-anonymous responses. This assertion is deliberately vague; its presence
indicates that some non-anonymous addresses will be accepted but doesn't
***************
*** 364,373 ****
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>
--- 381,385 ----
a request that contains an address that it doesn't understand or that
requires a binding it doesn't support. </p>
! <p>The None URI ("<code>http://www.w3.org/2005/08/addressing/none</code>") may appear as the
value of [address] in place of a non-anonymous address; this value MUST be
accepted.</p>
***************
*** 376,380 ****
<head>Examples (Compact Form)</head>
<example>
! <head>Subject supports WS-Addressing, no statement on supported response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<wsam:Addressing wsp:Optional="true">
--- 388,392 ----
<head>Examples (Compact Form)</head>
<example>
! <head>Subject supports WS-Addressing</head>
<eg xml:space="preserve"><wsp:Policy>
<wsam:Addressing wsp:Optional="true">
***************
*** 384,388 ****
</example>
<example>
! <head>Subject requires WS-Addressing, no statement on supported response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<wsam:Addressing>
--- 396,400 ----
</example>
<example>
! <head>Subject requires WS-Addressing</head>
<eg xml:space="preserve"><wsp:Policy>
<wsam:Addressing>
***************
*** 392,420 ****
</example>
<example>
! <head>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</head>
! <eg xml:space="preserve"><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></eg>
! </example>
! <example>
! <head>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</head>
! <eg xml:space="preserve"><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy>
! <wsp:ExactlyOne>
! <wsam:AnonymousResponses/>
! <wsam:NonAnonymousResponses/>
! </wsp:ExactlyOne>
! </wsp:Policy>
! </wsam:Addressing>
! </wsp:Policy></eg>
! </example>
! <example>
! <head>Subject requires WS-Addressing and explicit support of non-anonymous response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<wsam:Addressing>
--- 404,408 ----
</example>
<example>
! <head>Subject requires WS-Addressing and requires the use of non-anonymous response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<wsam:Addressing>
***************
*** 429,433 ****
<head>Examples (Normal Form)</head>
<example>
! <head>Subject supports WS-Addressing, no statement on supported response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
--- 417,421 ----
<head>Examples (Normal Form)</head>
<example>
! <head>Subject supports WS-Addressing</head>
<eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
***************
*** 446,450 ****
</example>
<example>
! <head>Subject requires WS-Addressing, no statement on supported response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
--- 434,438 ----
</example>
<example>
! <head>Subject requires WS-Addressing</head>
<eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
***************
*** 461,489 ****
</wsp:Policy></eg>
</example>
! <example>
! <head>Subject supports WS-Addressing, explicitly (and optionally) supports anonymous and non-anonymous response EPRs</head>
! <eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
- <wsp:All/>
- <wsp:All>
- <wsam:Addressing>
- <wsp:Policy>
- <wsp:ExactlyOne>
- <wsp:All/>
- </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>
--- 449,456 ----
</wsp:Policy></eg>
</example>
! <example>
! <head>Subject requires WS-Addressing and requires the use of non-anonymous response EPRs</head>
! <eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
<wsam:Addressing>
***************
*** 497,500 ****
--- 464,484 ----
</wsam:Addressing>
</wsp:All>
+ </wsp:ExactlyOne>
+ </wsp:Policy></eg>
+ </example>
+ </div3>
+ <div3 id="usingintersection">
+ <head>Finding Compatible Policies</head>
+ <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>
+ <example>
+ <head>Client looking for an endpoint which supports Addressing, and which supports anonymous responses</head>
+ <eg xml:space="preserve"><wsp:Policy>
+ <wsp:ExactlyOne>
<wsp:All>
<wsam:Addressing>
***************
*** 502,507 ****
<wsp:ExactlyOne>
<wsp:All>
! <wsam:AnonymousResponses/>
! <wsam:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
--- 486,490 ----
<wsp:ExactlyOne>
<wsp:All>
! <AnonymousResponses Optional=”true”/>
</wsp:All>
</wsp:ExactlyOne>
***************
*** 510,536 ****
</wsp:All>
</wsp:ExactlyOne>
! </wsp:Policy></eg>
! </example>
<example>
! <head>Subject requires WS-Addressing, requires explicit support of anonymous or non-anonymous response EPRs</head>
<eg xml:space="preserve"><wsp:Policy>
<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>
--- 493,515 ----
</wsp:All>
</wsp:ExactlyOne>
! </wsp:Policy>
! </eg>
! </example>
<example>
! <head>Client looking for an endpoint which supports Addressing, and does not require support for responses (will intersect with anything)</head>
<eg xml:space="preserve"><wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:Addressing> <-- supports all response types -->
<wsp:Policy>
</wsp:Policy>
</wsam:Addressing>
</wsp:All>
<wsp:All>
! <wsam:Addressing> <-- requires Anonymous responses -->
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <AnonymousResponses />
</wsp:All>
</wsp:ExactlyOne>
***************
*** 538,554 ****
</wsam:Addressing>
</wsp:All>
- </wsp:ExactlyOne>
- </wsp:Policy></eg>
- </example>
- <example>
- <head>Subject requires WS-Addressing and explicit support of non-anonymous response EPRs</head>
- <eg xml:space="preserve"><wsp:Policy>
- <wsp:ExactlyOne>
<wsp:All>
! <wsam:Addressing>
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <wsam:NonAnonymousResponses/>
</wsp:All>
</wsp:ExactlyOne>
--- 517,526 ----
</wsam:Addressing>
</wsp:All>
<wsp:All>
! <wsam:Addressing> <- requires nonAnonymous responses -->
<wsp:Policy>
<wsp:ExactlyOne>
<wsp:All>
! <NonAnonymousResponses />
</wsp:All>
</wsp:ExactlyOne>
***************
*** 557,637 ****
</wsp:All>
</wsp:ExactlyOne>
! </wsp:Policy></eg>
! </example>
! </div3>
! <div3 id="usingintersection">
! <head>Finding Compatible Policies</head>
! <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>
! <example>
! <head>Client looking for an endpoint which supports Addressing, WSDL states explicit support for anonymous responses</head>
! <eg xml:space="preserve"><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy/>
! </wsam:Addressing>
! </wsp:Policy></eg>
! <p>The client's policy (above) states the requirement for Addressing, but no
! requirement for explicit support of responses.</p>
! <eg xml:space="preserve"><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy>
! <wsam:AnonymousResponses/>
! </wsp:Policy>
! </wsam:Addressing>
! </wsp:Policy></eg>
! <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>
! <eg xml:space="preserve"><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy>
! <wsam:AnonymousResponses wsp:Optional="true"/>
! </wsp:Policy>
! </wsam:Addressing>
! </wsp:Policy></eg>
! <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>
! </example>
! <p>Now let us consider a variation on this same situation, where the WSDL marks its explicit
! support of anonymous responses as ignorable.</p>
! <example>
! <head>Client looking for an endpoint which supports Addressing, WSDL states (ignorable) explicit support for anonymous responses</head>
! <eg xml:space="preserve"><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy/>
! </wsam:Addressing>
! </wsp:Policy></eg>
! <p>The client's policy (above) states the requirement for Addressing, but no
! requirement for explicit support of responses.</p>
! <eg xml:space="preserve"><wsp:Policy>
! <wsam:Addressing>
! <wsp:Policy>
! <wsam:AnonymousResponses wsp:Ignorable="true"/>
! </wsp:Policy>
! </wsam:Addressing>
! </wsp:Policy></eg>
! <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>
</example>
! <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 [<bibref ref="WSPolicyPrimer"/>].</p>
--- 529,536 ----
</wsp:All>
</wsp:ExactlyOne>
! </wsp:Policy>
! </eg>
</example>
! <p>For more detailed descriptions of the use of
wsp:Optional, wsp:Ignorable, and strict and lax intersection, please refer
to the WS-Policy Primer [<bibref ref="WSPolicyPrimer"/>].</p>
Index: ws-addr-wsdl.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-wsdl.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -C 2 -d -r1.55 -r1.56
*** ws-addr-wsdl.html 31 Jan 2007 11:07:26 -0000 1.55
--- ws-addr-wsdl.html 26 Apr 2007 12:34:59 -0000 1.56
***************
*** 1,3 ****
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - Metadata</title><style type="text/css">
code { font-family: monospace; }
--- 1,3 ----
! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<html lang="en-US"><head><META http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Web Services Addressing 1.0 - Metadata</title><style type="text/css">
code { font-family: monospace; }
***************
*** 8,11 ****
--- 8,17 ----
[...2521 lines suppressed...]
! action pattern. The 200408 [action] can be made consistent with the 1.0 default by: </p><ol class="enumar"><li><p>specifying wsa200408:Action explicitly when the targetNamespace is a URN,
! and</p></li><li><p>specifying wsa200408:Action explicitly when the message is a fault.</p></li></ol><p> If the targetNamespace is a URN, it is not advisable to use the 2004-08 default
action pattern, as it leads to malformed IRIs. If the targetNamespace is not a URN,
and the 2004-08 default action pattern is in use, the 1.0 [action] value can be made
! consistent by: </p><ol class="enumar"><li><p>specifying wsam:Action explicitly when the message is a fault.</p></li></ol></div><div class="div1">
! <h2><a name="changelog" id="changelog"></a>C. Change Log (Non-Normative)</h2><div class="div2">
! <h3><a name="N68225" id="N68225"></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-31 @ 13:18</td><td>plehegar</td><td>Removed extra whitespaces, added missing whitespaces, fixed
! introduction to include mention of WS-Policy, changed prefix from
! "ws-addr-wsdl" to "ws-addr-metadata", latest version is CR of May 29,
! changed status back to WD, updated references (new editions of XML 1.0
! and XML Namespaces, new versions of WSDL 2.0, new policy primer)</td></tr><tr><td>2007-01-31 @ 10:57</td><td>trogers</td><td>Removed the last traces of UsingAddressing</td></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></div><div class="div2">
! <h3><a name="N68231" id="N68231"></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:3</td><td>mhadley</td><td>Added resolution of issue lc122 - added (n..m) notation to wsaw:InterfaceName, wsaw:ServiceName and wsaw:ServiceName/@EndpointName descriptions</td></tr><tr><td>2006-04-26 @ 15:28</td><td>mhadley</td><td>Added resolution of issue lc123 - changed all the examples to be based on the one used in the WSDL 2.0 primer</td></tr><tr><td>2006-04-17 @ 10:27</td><td>trogers</td><td>Removed MUST from section 4.1 concerning the value of [destination] (LC130)</td></tr><tr><td>2006-04-17 @ 10:14</td><td>trogers</td><td>Marking UsingAddressing using <el> tag to show that it is not a typo in heading 3.1 (LC126)</td></tr><tr><td>2006-04-17 @ 10:05</td><td>trogers</td><td>Added the class of product specification to the Abstract (LC125)</td></tr><tr><td>2006-04-17 @ 09:46</td><td>trogers</td><td>Applied the changes required for LC120 - typo in intro and correcting wsa:Action/wsaw:Action.</td></tr><tr><td>2006-04-17 @ 09:34</td><td>trogers</td><td>Applied the changes required for LC119.</td></tr><r><td>2006-04-17 @ 08:42</td><td>trogers</td><td>Changed the {reference parameters} property from REQUIRED to OPTIONAL in the component model. This completes LC116.</td></tr><tr><td>2006-03-27 @ 19:48</td><td>mhadley</td><td>Used alternate words instead of lowercase RFC2119 terms</td></tr><tr><td>2006-03-20 @ 15:05</td><td>mhadley</td><td>Fixed a typo in example generated fault action</td></tr><tr><td>2006-03-15 @ 22:56</td><td>trogers</td><td>Implemented the resolution of LC116: added section describing the {reference parameters} property.</td></tr><tr><td>2006-03-13 @ 13:30</td><td>trogers</td><td>Added the resolution of LC113: clarifying section 3.3 WSDL SOAP module.</td></tr><tr><td>2006-03-13 @ 13:19</td><td>trogers</td><td>Added the resolution of LC111: clarifying the {addressing required} property.</td></tr><tr><td>2006-03-13 @ 13:03</td><td>trogers</td><td>Altered changelog limit from start of 2006 to end of 2006.</td></tr><tr><td>2006-03-13 @ 12:59</td><td>trogers</td><td>Added resolution of LC109:specify that at least one of reply or fault endpoint is required on Robust In-Only</td></tr><tr><td>2006-03-03 @ 14:10</td><td>mhadley</td><td>Fixed editor list in references</td></tr><tr><td>2006-03-03 @ 13:48</td><td>mhadley</td><td>Added resolution 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="N68237" id="N68237"></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 impacts of extension elements on WSDL 2.0 component model</td></tr><tr><td>2005-11-07 @ 07:08</td><td>mhadley</td><td>Added resolution to issue 65, [action] defaults to same as SOAPAction in absence of wsaw:Action</td></tr><tr><td>2005-11-07 @ 06:44</td><td>mhadley</td><td>Updated resolution to issues 56, 57</td></tr><tr><td>2005-10-31 @ 20:35</td><td>mhadley</td><td>Updated UsingAddressing section to move some dense text into a simpler tabular form</td></tr><tr><td>2005-10-31 @ 20:12</td><td>mhadley</td><td>Added resolution to issues 56 and 57, added new top level section that describes how MAP values are derived from WSDL for [destination], [action] and [reference properties]</td></tr><tr><td>2005-10-24 @ 01:50</td><td>trogers</td><td>Added appendix on action compatibility with 200408 version (resolving i64)</td></tr><tr><td>2005-10-17 @ 18:44</td><td>mhadley</td><td>Added namesapce change policy</td></tr><tr><td>2005-10-11 @ 03:16</td><td>troger</td><td>Incorporated the resolution of i61.</td></tr><tr><td>2005-10-10 @ 20:20</td><td>mhadley</td><td>Fixed type in example fault action URI. Added clarification that WSDL 1.1 material is included for backwards compatibility only</td></tr><tr><td>2005-09-15 @ 19:16</td><td>mhadley</td><td>Added resolution to issue 62 - changed Fault: to [delimiter]Fault[delimiter] in default action for WSDL 1.1 faults</td></tr><tr><td>2005-09-15 @ 19:09</td><td>mhadley</td><td>Added resolution to issue 20 - noted that inclusion of InterfaceName or @EndpointName in an EPR makes the EPR specific to the identified interface or endpoint respectively</td></tr><tr><td>2005-09-15 @ 18:47</td><td>mhadley</td><td>Added resolution to issue 17 - noted that action fulfils WSDL best practice for unique message signatures</td></tr><tr><td>2005-05-25 @ 21:40</td><td>mhadley</td><td>Added new section in changelog to account for previous draft publication</td></tr><tr><td>2005-05-18 @ 19:42</td><td>mhadley</td><td>Added lc53 resolution -expanded MAP to message addressing property and fixed editorial glitch</td></tr><tr><td>2005-05-18 @ 19:22</td><td>mhadley</td><td>Added lc47 resolution - fixed URL in WSDL 2.0 biblio entry</td></tr><tr><td>2005-04-22 @ 22:37</td><td>mhadley</td><td>Added issue 21 resolution</td></tr></table></div><div class="div2">
! <h3><a name="N68243" id="N68243"></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 resolution to issue 45</td></tr></table></div><div class="div2">
! <h3><a name="N68249" id="N68249"></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>Switched 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="N68255" id="N68255"></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></div></div></div></body></html>
\ No newline at end of file
Received on Thursday, 26 April 2007 12:35:05 UTC