- From: Paul Downey via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 09 Sep 2005 19:18:07 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv28219
Modified Files:
ws-addr-testsuite.html ws-addr-testsuite.xml
Log Message:
moving scenarios into separate document. listed metadata for each test case. references assertions and message-exchanges
Index: ws-addr-testsuite.html
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-testsuite.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** ws-addr-testsuite.html 9 May 2005 21:47:24 -0000 1.2
--- ws-addr-testsuite.html 9 Sep 2005 19:18:05 -0000 1.3
***************
*** 1,4 ****
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
"en-US">
--- 1,4 ----
! <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
! "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
"en-US">
***************
*** 69,77 ****
<dl>
<dt>This version:</dt>
! <dd><a href="ws-addr-wsdl.html">ws-addr-wsdl.html</a></dd>
<dt>Latest version:</dt>
<dd><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl">
! http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl</a></dd>
<dt>Previous versions:</dt>
<dd><a href=""></a></dd>
--- 69,78 ----
<dl>
<dt>This version:</dt>
! <dd><a href=
! "ws-addr-testsuite.html">ws-addr-testsuite.html</a></dd>
<dt>Latest version:</dt>
<dd><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-testsuite">
! http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-testsuite</a></dd>
<dt>Previous versions:</dt>
<dd><a href=""></a></dd>
***************
*** 117,156 ****
1.2 <a href="#notation">Notational
Conventions</a><br />
! 1.3 <a href=
! "#namespaces">Namespaces</a><br />
! 2. <a href="#testScenarios">Test Scenarios</a><br />
! 2.1 <a href=
! "#messagePassingScenarios">Message Passing Scenarios</a><br />
! 2.1.1 <a href=
! "#OneWayScenarios">One Way Binding</a><br />
! 2.1.1.1
! <a href="#Oneway-In-only">One Way Robust In-Only</a><br />
! 2.1.1.2
! <a href="#Oneway-Robust-In-only">One Way Robust In-Only</a><br />
! 2.1.1.3
! <a href="#Oneway-In-Out">One Way In-Only</a><br />
! 2.1.1.4
! <a href="#Oneway-Out-Only">One Way Out-Only</a><br />
! 2.1.2 <a href=
! "#TwoWayScenarios">Two Way Binding</a><br />
! 2.1.2.1
! <a href="#Twoway-In-Only">Two Way In-Only</a><br />
! 2.1.2.2
! <a href="#Twoway-Robust-In-Only-A">Two Way Robust-In-Only (Option
! A)</a><br />
! 2.1.2.3
! <a href="#Twoway-Robust-In-Only-B">Two Way Robust-In-Only (Option
! B)</a><br />
! 2.1.2.4
! <a href="#Twoway-In-Out-A">Two Way In-Out (Option A)</a><br />
! 2.1.2.5
! <a href="#Twoway-In-Out-B">Two Way In-Out (Option B)</a><br />
! 2.2 <a href="#otherScenarios">Other
! Scenarios</a><br />
! 3. <a href="#testAssertions">Test Assertions</a><br />
! 4. <a href="#testCases">Test Cases</a><br />
! 5. <a href="#testDocuments">Test Documents</a><br />
! 6. <a href="#contributing">Contributing Test Materials</a><br />
! 7. <a href="#references">References</a><br /></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3>
<p class="toc">A. <a href="#acknowledgments">Acknowledgements</a>
--- 118,124 ----
1.2 <a href="#notation">Notational
Conventions</a><br />
! 2. <a href="#testCases">Test Cases</a><br />
! 3. <a href="#contributing">Contributing Test Materials</a><br />
! 4. <a href="#references">References</a><br /></p>
<h3><a name="appendix" id="appendix">Appendices</a></h3>
<p class="toc">A. <a href="#acknowledgments">Acknowledgements</a>
***************
*** 170,174 ****
during the Call for Implementations step.</em> It is anticipated
that some, but not all of the test cases held within the test suite
! will be used to practially test implementations during an
interoperability Workshop and thereby satisfy the entrance criteria
for the Web Service Addressing specifications to enter the <a href=
--- 138,142 ----
during the Call for Implementations step.</em> It is anticipated
that some, but not all of the test cases held within the test suite
! will be used to practically test implementations during an
interoperability Workshop and thereby satisfy the entrance criteria
for the Web Service Addressing specifications to enter the <a href=
***************
*** 217,582 ****
(<xs:anyAttribute/>).</p>
</div>
- <div class="div2">
- <h3><a name="namespaces" id="namespaces"></a>1.3 Namespaces</h3>
- <p>This specification uses a number of namespace prefixes
- throughout; they are listed in <a href="#nsprefix">Table 1-1</a>.
- Note that the choice of any namespace prefix is arbitrary and not
- semantically significant (see [<cite><a href="#XMLNS">XML
- Namespaces</a></cite> ]).</p>
- <a name="nsprefix" id="nsprefix"></a>
- <table summary="Namespace prefixes usage in this specification"
- border="1">
- <caption>Table 1-1. Prefixes and Namespaces used in this
- specification</caption>
- <tbody>
- <tr>
- <th align="left" rowspan="1" colspan="1">Prefix</th>
- <th align="left" rowspan="1" colspan="1">Namespace</th>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">S</td>
- <td rowspan="1" colspan="1">
- http://www.w3.org/2003/05/soap-envelope</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">S11</td>
- <td rowspan="1" colspan="1">
- http://schemas.xmlsoap.org/soap/envelope</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">wsa</td>
- <td rowspan="1" colspan="1">
- http://www.w3.org/@@@@/@@/addressing</td>
- </tr>
- <tr>
- <td rowspan="1" colspan="1">xs</td>
- <td rowspan="1" colspan="1">http://www.w3.org/2001/XMLSchema</td>
- </tr>
- </tbody>
- </table>
- <br />
- <p>WS-Addressing may be used with SOAP [<cite><a href=
- "#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework</a></cite>] as
- described in Web Services Addressing 1.0 - SOAP
- Binding[<cite><a href=
- "#WSADDR-SOAP">WS-Addressing-SOAP</a></cite>]. WS-Addressing may be
- used with WSDL [<cite><a href="#WSDL20">WSDL 2.0</a></cite>]
- described services as described in Web Services Addressing 1.0 -
- WSDL Binding[<cite><a href=
- "#WSADDR-WSDL">WS-Addressing-WSDL</a></cite>]. Examples in this
- specification use an XML 1.0 [<cite><a href="#XML10">XML
- 1.0</a></cite>] representation but this is not a requirement.</p>
- <p>All information items defined by this specification are
- identified by the XML namespace URI [<cite><a href="#XMLNS">XML
- Namespaces</a></cite>] "http://www.w3.org/@@@@/@@/addressing". 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>
- </div>
- </div>
- <div class="div1">
- <h2><a name="testScenarios" id="testScenarios"></a>2. Test
- Scenarios</h2>
- <table border="1" summary="Editorial note: P Downey">
- <tr>
- <td align="left" valign="top" width="50%"><b>Editorial note: P
- Downey</b></td>
- <td align="right" valign="top" width="50%"> </td>
- </tr>
- <tr>
- <td colspan="2" align="left" valign="top">Scenarios taken from a
- whiteboard discussion of the Async Task Force, 18-4-2005.</td>
- </tr>
- </table>
- <div class="div2">
- <h3><a name="messagePassingScenarios" id=
- "messagePassingScenarios"></a>2.1 Message Passing Scenarios</h3>
- <div class="div3">
- <h4><a name="OneWayScenarios" id="OneWayScenarios"></a>2.1.1 One
- Way Binding</h4>
- <p>Message passing scenarios using an underlying protocol to
- exchange messages which has no natural return path for messages,
- e.g. UDP.</p>
- <div class="div4">
- <h5><a name="Oneway-In-only" id="Oneway-In-only"></a>2.1.1.1 One
- Way Robust In-Only</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inonly.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-1.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Oneway-Robust-In-only" id=
- "Oneway-Robust-In-only"></a>2.1.1.2 One Way Robust In-Only</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-robustinonly.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-2.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Oneway-In-Out" id="Oneway-In-Out"></a>2.1.1.3 One Way
- In-Only</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inout.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-3.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Oneway-Out-Only" id="Oneway-Out-Only"></a>2.1.1.4 One
- Way Out-Only</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-outonly.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-4.</span></i></p>
- <br /></div>
- </div>
- </div>
- <div class="div3">
- <h4><a name="TwoWayScenarios" id="TwoWayScenarios"></a>2.1.2 Two
- Way Binding</h4>
- <p>Message passing scenarios using an underlying protocol to
- exchange messages which has a 'back-channel', e.g. HTTP.</p>
- <div class="div4">
- <h5><a name="Twoway-In-Only" id="Twoway-In-Only"></a>2.1.2.1 Two
- Way In-Only</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inonly.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-5.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Twoway-Robust-In-Only-A" id=
- "Twoway-Robust-In-Only-A"></a>2.1.2.2 Two Way Robust-In-Only
- (Option A)</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-a.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-6.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Twoway-Robust-In-Only-B" id=
- "Twoway-Robust-In-Only-B"></a>2.1.2.3 Two Way Robust-In-Only
- (Option B)</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-b.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-7.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Twoway-In-Out-A" id="Twoway-In-Out-A"></a>2.1.2.4 Two
- Way In-Out (Option A)</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-a.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-8.</span></i></p>
- <br /></div>
- </div>
- <div class="div4">
- <h5><a name="Twoway-In-Out-B" id="Twoway-In-Out-B"></a>2.1.2.5 Two
- Way In-Out (Option B)</h5>
- <div class="figure" style="text-align: center"><br />
- <img src=
- "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-b.png?rev=1.1&content-type=image/png" />
- <p style="text-align:left"><i><span>Figure 2-9.</span></i></p>
- <br /></div>
- </div>
- </div>
- </div>
- <div class="div2">
- <h3><a name="otherScenarios" id="otherScenarios"></a>2.2 Other
- Scenarios</h3>
- <table border="1" summary="Editorial note: P Downey">
- <tr>
- <td align="left" valign="top" width="50%"><b>Editorial note: P
- Downey</b></td>
- <td align="right" valign="top" width="50%"> </td>
- </tr>
- <tr>
- <td colspan="2" align="left" valign="top">There may be other types
- of scenario we would use to catalogue tests, such as "security",
- which may be used in conjuction with the message passing
- scenarios.</td>
- </tr>
- </table>
- </div>
</div>
<div class="div1">
! <h2><a name="testAssertions" id="testAssertions"></a>3. Test
! Assertions</h2>
! <p>Assertions to be defined in a separate assertions document.</p>
! <table border="1" summary="Editorial note: P Downey">
! <tr>
! <td align="left" valign="top" width="50%"><b>Editorial note: P
! Downey</b></td>
! <td align="right" valign="top" width="50%"> </td>
! </tr>
! <tr>
! <td colspan="2" align="left" valign="top">The SOAP 1.2 assertions
! document made it to Recommended. Should we afford our assertion
! document the same status given it is likely to remain stable with
! the specfication?</td>
! </tr>
! </table>
! </div>
! <div class="div1">
! <h2><a name="testCases" id="testCases"></a>4. Test Cases</h2>
! <table border="1" summary="Editorial note: P Downey">
! <tr>
! <td align="left" valign="top" width="50%"><b>Editorial note: P
! Downey</b></td>
! <td align="right" valign="top" width="50%"> </td>
! </tr>
! <tr>
! <td colspan="2" align="left" valign="top">The test cases from the
! Microsoft submitted scenarios reference a version of WS-Addressing.
! dated 2004/03 and possibly not the Member Submission. Is this an
! issue from the IP perspective?</td>
! </tr>
! </table>
</div>
<div class="div1">
! <h2><a name="testDocuments" id="testDocuments"></a>5. Test
! Documents</h2>
! <table border="1" summary="Editorial note: P Downey">
! <tr>
! <td align="left" valign="top" width="50%"><b>Editorial note: P
! Downey</b></td>
! <td align="right" valign="top" width="50%"> </td>
! </tr>
! <tr>
! <td colspan="2" align="left" valign="top">Test from the Microsoft
! submitted scenarios reference a version of WS-Addressing. dated
! 2004/03 and possibly not the Member Submission. Is this an issue
! from the IP perspective?</td>
! </tr>
! </table>
! <a name="testDocumentsTable" id="testDocumentsTable"></a>
! <table summary="Test Documents" border="1">
! <caption>Table 5-1. Test Documents</caption>
! <tbody>
! <tr>
! <th align="left" rowspan="1" colspan="1">Contributor</th>
! <th align="left" rowspan="1" colspan="1">Message</th>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/fault-4.xml">
! fault-4.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/fault-5.xml">
! fault-5.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-1.xml">
! request-1.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-2.xml">
! request-2.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-3.xml">
! request-3.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-4.xml">
! request-4.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-5.xml">
! request-5.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-6.xml">
! request-6.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-7.xml">
! request-7.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-8.xml">
! request-8.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-9.xml">
! request-9.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-2.xml">
! response-2.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-3.xml">
! response-3.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-4.xml">
! response-4.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-6.xml">
! response-6.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-7.xml">
! response-7.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-8.xml">
! response-8.xml</a></td>
! </tr>
! <tr>
! <td rowspan="1" colspan="1">Microsoft</td>
! <td rowspan="1" colspan="1"><a href=
! "http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-9.xml">
! response-9.xml</a></td>
! </tr>
! </tbody>
! </table>
! <br /></div>
! <div class="div1">
! <h2><a name="contributing" id="contributing"></a>6. Contributing
Test Materials</h2>
<p>The Test Suite consists entirely of voluntary contributions of
--- 185,251 ----
(<xs:anyAttribute/>).</p>
</div>
</div>
<div class="div1">
! <h2><a name="testCases" id="testCases"></a>2. Test Cases</h2>
! <p>The Test Suite comprises of a collection of <a href=
! "test-cases/cases/cases.html">test cases</a>. Each test case
! contains the following information:</p>
! <dl>
! <dt class="label">identifier</dt>
! <dd>
! <p>An unambiguous xml:id value to enable the test case to be
! referenced within a specific version of the test suite.</p>
! </dd>
! <dt class="label">title</dt>
! <dd>
! <p>A friendly name for the test case.</p>
! </dd>
! <dt class="label">cr</dt>
! <dd>
! <p>An indication that this test forms part of the Exit Criteria for
! the Candidate Recommendation phase for one or more Web Service
! Addressing specifications.</p>
! </dd>
! <dt class="label">assertions</dt>
! <dd>
! <p>A list of <a href=
! "test-cases/assertions/assertions.html">assertions</a> document the
! test case exhibits. The purpose of the assertions being to access
! the coverage of the Test Suite.</p>
! </dd>
! <dt class="label">message exchange</dt>
! <dd>
! <p>The concrete <a href=
! "test-cases/assertions/message-exchanges.html">message exchange</a>
! followed by a successful execution of the test case.</p>
! </dd>
! <dt class="label">scenarios</dt>
! <dd>
! <p>A list of the abstract scenarios exhibited by the test case, at
! most one from each of the categories: <a href=
! "test-cases/assertions/scenarios.html#MessagePassing">message
! passing</a>, <a href=
! "test-cases/assertions/scenarios.html#Security">security</a>,
! etc.</p>
! </dd>
! <dt class="label">description</dt>
! <dd>
! <p>A description of the nature and characteristics of the test case
! to assist reviewers to understand the purpose of a test and provide
! those executing the test with any additional information that will
! be helpful should the test fail.</p>
! </dd>
! <dt class="label">documents</dt>
! <dd>
! <p>One or more example <a href=
! "test-cases/documents/documents.html">test documents</a>, including
! WSDL 1.1 and WSDL 2.0 documents as well as SOAP 1.1 and SOAP 1.2
! messages which may be used to build canned test interactions for
! some test cases.</p>
! </dd>
! </dl>
</div>
<div class="div1">
! <h2><a name="contributing" id="contributing"></a>3. Contributing
Test Materials</h2>
<p>The Test Suite consists entirely of voluntary contributions of
***************
*** 585,599 ****
developed to the Test Suite.</p>
<p>Tests may be submitted to the Suite in the form of an Email sent
! to <a href=
"mailto:public-ws-addressing-tests@w3.org">public-ws-addressing-tests@w3.org</a>
! An archive is available at <a href=
"http://lists.w3.org/Archives/Public/public-ws-addressing-tests/">http://lists.w3.org/Archives/Public/public-ws-addressing-tests</a>
Submited test cases should be released to the Test Suite by
! completing the <a href=
"http://www.w3.org/2002/09/wbs/1/testgrants2-200409/">Test Case
Grant II Form</a>.</p>
</div>
<div class="div1">
! <h2><a name="references" id="references"></a>7. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE" id=
--- 254,275 ----
developed to the Test Suite.</p>
<p>Tests may be submitted to the Suite in the form of an Email sent
! to<a href=
"mailto:public-ws-addressing-tests@w3.org">public-ws-addressing-tests@w3.org</a>
! An archive is available at<a href=
"http://lists.w3.org/Archives/Public/public-ws-addressing-tests/">http://lists.w3.org/Archives/Public/public-ws-addressing-tests</a>
Submited test cases should be released to the Test Suite by
! completing the<a href=
"http://www.w3.org/2002/09/wbs/1/testgrants2-200409/">Test Case
Grant II Form</a>.</p>
+ <p>When contributing materials to the Test Suite, it is helpful if
+ each individual test case cites the metadata such as the existing
+ Test Assertions, Scenarios and Message Exchanges exhibited. The
+ submission may also include details of any new scenarios which the
+ test case exhibits. Providing examples of the messages exchanged
+ and metadata such as WSDL 1.1 and WSDL 2.0 in the form of complete
+ XML documents will also be of value.</p>
</div>
<div class="div1">
! <h2><a name="references" id="references"></a>4. References</h2>
<dl>
<dt class="label"><a name="WSADDR-CORE" id=
***************
*** 711,737 ****
alphabetical order): Abbie Barbir (Nortel Networks), Rebecca
Bergersen (IONA Technologies, Inc.), Andreas Bjärlestam (ERICSSON),
! Ugo Corda (SeeBeyond Technology Corporation), Francisco Curbera
! (IBM Corporation), Glen Daniels (Sonic Software), Paul Downey (BT),
! Jacques Durand (Fujitsu Limited), Michael Eder (Nokia), Robert
! Freund (Hitachi, Ltd.), Yaron Goland (BEA Systems, Inc.), Martin
! Gudgin (Microsoft Corporation), Arun Gupta (Sun Microsystems,
! Inc.), Hugo Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.),
! David Hull (TIBCO Software, Inc.), Yin-Leng Husband (HP), Anish
! Karmarkar (Oracle Corporation), Paul Knight (Nortel Networks),
! Philippe Le Hégaret (W3C/MIT), Mark Little (Arjuna Technologies
! Ltd.), Jonathan Marsh (Microsoft Corporation), Jeff Mischkinsky
! (Oracle Corporation), Nilo Mitra (ERICSSON), Eisaku Nishiyama
! (Hitachi, Ltd.), Mark Nottingham (BEA Systems, Inc.), Ales Novy
! (Systinet Inc.), David Orchard (BEA Systems, Inc.), Mark Peel
! (Novell, Inc.), Tony Rogers (Computer Associates), Tom Rutt
! (Fujitsu Limited), Rich Salz (DataPower Technology, Inc.), Davanum
! Srinivas (Computer Associates), Jiri Tejkl (Systinet Inc.), Greg
! Truty (IBM Corporation), Steve Vinoski (IONA Technologies, Inc.),
! Pete Wenzel (SeeBeyond Technology Corporation), Steve Winkler (SAP
! AG), Ümit Yalçınalp (SAP AG), Prasad Yendluri (webMethods,
! Inc.).</p>
<p>Previous members of the Working Group were: Lisa Bahler (SAIC -
Telcordia Technologies), Marc Goodner (SAP AG), Harris Reynolds
! (webMethods, Inc.).</p>
<p>The people who have contributed to <a href=
"http://lists.w3.org/Archives/Public/public-ws-addressing/">discussions
--- 387,415 ----
alphabetical order): Abbie Barbir (Nortel Networks), Rebecca
Bergersen (IONA Technologies, Inc.), Andreas Bjärlestam (ERICSSON),
! Dave Chappell (Sonic Software), Ugo Corda (SeeBeyond Technology
! Corporation), Francisco Curbera (IBM Corporation), Glen Daniels
! (Sonic Software), Vikas Deolaliker (Sonoa Systems, Inc.), Paul
! Downey (BT), Jacques Durand (Fujitsu Limited), Michael Eder
! (Nokia), Robert Freund (Hitachi, Ltd.), Yaron Goland (BEA Systems,
! Inc.), Marc Goodner (Microsoft Corporation), Martin Gudgin
! (Microsoft Corporation), Arun Gupta (Sun Microsystems, Inc.), Hugo
! Haas (W3C/ERCIM), Marc Hadley (Sun Microsystems, Inc.), David Hull
! (TIBCO Software, Inc.), Yin-Leng Husband (HP), Anish Karmarkar
! (Oracle Corporation), Paul Knight (Nortel Networks), Philippe Le
! Hégaret (W3C/MIT), Amelia Lewis (TIBCO Software, Inc.), Mark Little
! (Arjuna Technologies Ltd.), Jonathan Marsh (Microsoft Corporation),
! Jeff Mischkinsky (Oracle Corporation), Nilo Mitra (ERICSSON),
! Eisaku Nishiyama (Hitachi, Ltd.), Mark Nottingham (BEA Systems,
! Inc.), Ales Novy (Systinet Inc.), David Orchard (BEA Systems,
! Inc.), Mark Peel (Novell, Inc.), Tony Rogers (Computer Associates),
! Tom Rutt (Fujitsu Limited), Rich Salz (DataPower Technology, Inc.),
! Davanum Srinivas (Computer Associates), Jiri Tejkl (Systinet Inc.),
! Steve Vinoski (IONA Technologies, Inc.), Katy Warr (IBM
! Corporation), Pete Wenzel (SeeBeyond Technology Corporation), Steve
! Winkler (SAP AG), Ümit Yalçinalp (SAP AG), Prasad Yendluri
! (webMethods, Inc.).</p>
<p>Previous members of the Working Group were: Lisa Bahler (SAIC -
Telcordia Technologies), Marc Goodner (SAP AG), Harris Reynolds
! (webMethods, Inc.), Greg Truty (IBM Corporation).</p>
<p>The people who have contributed to <a href=
"http://lists.w3.org/Archives/Public/public-ws-addressing/">discussions
Index: ws-addr-testsuite.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-testsuite.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** ws-addr-testsuite.xml 9 May 2005 21:47:24 -0000 1.2
--- ws-addr-testsuite.xml 9 Sep 2005 19:18:05 -0000 1.3
***************
*** 22,26 ****
</pubdate>
<publoc>
! <loc href="&w3c-designation-wsa-testsuite;">&w3c-designation-wsa-testsuite;</loc>
</publoc> &altlocs; <prevlocs>
<loc href="&prevloc;">&prevloc;</loc>
--- 22,27 ----
</pubdate>
<publoc>
! <loc href="&w3c-designation-wsa-testsuite;"
! >&w3c-designation-wsa-testsuite;</loc>
</publoc> &altlocs; <prevlocs>
<loc href="&prevloc;">&prevloc;</loc>
***************
*** 36,43 ****
</authlist>
<abstract>
! <p>This document describes the Test Suite deliverable for the
! <loc href='http://www.w3.org/2002/ws/addr/'>Web Services Addressing Working Group</loc>
! as defined by the Working Group's
! <loc href="http://www.w3.org/2004/09/wsa-charter.html">Charter</loc>. </p>
</abstract> &status; <langusage>
<language id="en-US">English</language>
--- 37,44 ----
</authlist>
<abstract>
! <p>This document describes the Test Suite deliverable for the <loc
! href="http://www.w3.org/2002/ws/addr/">Web Services Addressing Working
! Group</loc> as defined by the Working Group's <loc
! href="http://www.w3.org/2004/09/wsa-charter.html">Charter</loc>. </p>
</abstract> &status; <langusage>
<language id="en-US">English</language>
***************
*** 51,88 ****
<head>Introduction</head>
<p>One of the deliverables specified in the Charter of the Web Services Addressing
! Working Group is
! <emph>a test suite intended to promote implementation of the
! Candidate Recommendation, and to assess interoperability between these
! implementations.</emph>
! </p>
! <p>The Working Group Charter also states that <emph>the Working Group is expected to demonstrate four
! interoperable implementations during the Call for Implementations step.</emph>
! It is anticipated that some, but not all of the test cases held within the test suite
! will be used to practially test implementations during an interoperability
! Workshop and thereby satisfy the entrance
! criteria for the Web Service Addressing
! specifications to enter the
! <loc href='http://www.w3.org/Consortium/Process-20010719/tr.html#RecsPR'>Proposed Recommendation stage</loc>.</p>
! <p>The test suite will be maintained by the Working Group and remain available for
! regression testing beyond publication of the Web Addressing Recommendation, however
! it is not expected that the test suite will form a part of the Web Addressing
! Recommendation; the status of this document will remain as a Working Group note.
! </p>
!
<div2 id="conformance">
<head>Conformance Claims</head>
! <p>
! A Web Services Addressing implementation that passes all of the tests specified
! in this document may claim conformance to the Web Services Addressing Test
! Suite $Date$.
! </p>
! <p>
! Conformance to the Web services Addressing Test Suite does not by itself enable a
! party to claim conformance with the Web Services Addressing specification.
! Not passing an individual test may be used as an indication that an implementation
! is likely not to conform to the Web Services Addressing specification.
! </p>
! </div2>
!
<div2 id="notation">
<head>Notational Conventions</head>
--- 52,81 ----
<head>Introduction</head>
<p>One of the deliverables specified in the Charter of the Web Services Addressing
! Working Group is <emph>a test suite intended to promote implementation of the
! Candidate Recommendation, and to assess interoperability between these
! implementations.</emph>
! </p>
! <p>The Working Group Charter also states that <emph>the Working Group is expected to
! demonstrate four interoperable implementations during the Call for
! Implementations step.</emph> It is anticipated that some, but not all of the
! test cases held within the test suite will be used to practically test
! implementations during an interoperability Workshop and thereby satisfy the entrance
! criteria for the Web Service Addressing specifications to enter the <loc
! href="http://www.w3.org/Consortium/Process-20010719/tr.html#RecsPR">Proposed
! Recommendation stage</loc>.</p>
! <p>The test suite will be maintained by the Working Group and remain available for
! regression testing beyond publication of the Web Addressing Recommendation, however
! it is not expected that the test suite will form a part of the Web Addressing
! Recommendation; the status of this document will remain as a Working Group note. </p>
<div2 id="conformance">
<head>Conformance Claims</head>
! <p> A Web Services Addressing implementation that passes all of the tests specified
! in this document may claim conformance to the Web Services Addressing Test Suite
! $Date$. </p>
! <p> Conformance to the Web services Addressing Test Suite does not by itself enable
! a party to claim conformance with the Web Services Addressing specification. Not
! passing an individual test may be used as an indication that an implementation
! is likely not to conform to the Web Services Addressing specification. </p>
! </div2>
<div2 id="notation">
<head>Notational Conventions</head>
***************
*** 103,352 ****
(<xs:anyAttribute/>).</p>
</div2>
- <div2 id="namespaces">
- <head>Namespaces</head>
- <p> This specification uses a number of namespace prefixes throughout; they are
- listed in <specref ref="nsprefix"/>. Note that the choice of any namespace
- prefix is arbitrary and not semantically significant (see [<bibref ref="XMLNS"/>
- ]).</p>
- <table summary="Namespace prefixes usage in this specification" id="nsprefix"
- border="1">
- <caption>Prefixes and Namespaces used in this specification</caption>
- <tbody>
- <tr>
- <th align="left">Prefix</th>
- <th align="left">Namespace</th>
- </tr>
- <tr>
- <td>S</td>
- <td>http://www.w3.org/2003/05/soap-envelope</td>
- </tr>
- <tr>
- <td>S11</td>
- <td>http://schemas.xmlsoap.org/soap/envelope</td>
- </tr>
- <tr>
- <td>wsa</td>
- <td>&nsuri;</td>
- </tr>
- <tr>
- <td>xs</td>
- <td>http://www.w3.org/2001/XMLSchema</td>
- </tr>
- </tbody>
- </table>
- <p>WS-Addressing may be used with SOAP [<bibref ref="SOAP12-PART1"/>] as described
- in &wsa-soap.title;[<bibref ref="WSADDR-SOAP"/>]. WS-Addressing may be used
- with WSDL [<bibref ref="WSDL20"/>] described services as described in
- &wsa-wsdl.title;[<bibref ref="WSADDR-WSDL"/>]. Examples in this
- specification use an XML 1.0 [<bibref ref="XML10"/>] representation but this is
- not a requirement.</p>
- <p>All information items defined by this specification are identified by the XML
- namespace URI [<bibref ref="XMLNS"/>] "&nsuri;". A normative XML Schema
- [<bibref ref="XMLSchemaP1"/>, <bibref ref="XMLSchemaP2"/>] document can be
- obtained by dereferencing the XML namespace URI.</p>
- </div2>
</div1>
-
- <div1 id="testScenarios">
- <head>Test Scenarios</head>
-
- <p>
- <ednote>
- <name>P Downey</name>
- <edtext>
- Scenarios taken from a whiteboard discussion
- of the Async Task Force, 18-4-2005.
- </edtext>
- </ednote>
- </p>
-
- <div2 id="messagePassingScenarios">
- <head>Message Passing Scenarios</head>
-
- <div3 id="OneWayScenarios">
- <head>One Way Binding</head>
- <p>Message passing scenarios using an underlying protocol to exchange
- messages which has no natural return path for messages, e.g. UDP.
- </p>
-
- <div4 id="Oneway-In-only">
- <head>One Way Robust In-Only</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inonly.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Oneway-Robust-In-only">
- <head>One Way Robust In-Only</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-robustinonly.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Oneway-In-Out">
- <head>One Way In-Only</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-inout.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Oneway-Out-Only">
- <head>One Way Out-Only</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/oneway-outonly.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- </div3>
-
- <div3 id="TwoWayScenarios">
- <head>Two Way Binding</head>
- <p>Message passing scenarios using an underlying protocol to exchange
- messages which has a 'back-channel', e.g. HTTP.
- </p>
-
- <div4 id="Twoway-In-Only">
- <head>Two Way In-Only</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inonly.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Twoway-Robust-In-Only-A">
- <head>Two Way Robust-In-Only (Option A)</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-a.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Twoway-Robust-In-Only-B">
- <head>Two Way Robust-In-Only (Option B)</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-robustinonly-b.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Twoway-In-Out-A">
- <head>Two Way In-Out (Option A)</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-a.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- <div4 id="Twoway-In-Out-B">
- <head>Two Way In-Out (Option B)</head>
- <p>
- <graphic source="http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/diagrams/twoway-inout-b.png?rev=1.1&content-type=image/png"/>
- </p>
- </div4>
-
- </div3>
- </div2>
-
- <div2 id="otherScenarios">
- <head>Other Scenarios</head>
-
- <ednote>
- <name>P Downey</name>
- <edtext>
- There may be other types of scenario we would use to
- catalogue tests, such as "security", which may be used in conjuction
- with the message passing scenarios.
- </edtext>
- </ednote>
- </div2>
-
- </div1>
-
- <div1 id="testAssertions">
- <head>Test Assertions</head>
- <p>
- Assertions to be defined in a separate assertions document.
- </p>
- <ednote>
- <name>P Downey</name>
- <edtext>
- The SOAP 1.2 assertions document made it to Recommended.
- Should we afford our assertion document the same status
- given it is likely to remain stable with the specfication?
- </edtext>
- </ednote>
- </div1>
-
<div1 id="testCases">
<head>Test Cases</head>
!
! <ednote>
! <name>P Downey</name>
! <edtext>
! The test cases from the Microsoft submitted
! scenarios reference a version of WS-Addressing.
! dated 2004/03 and possibly not the Member Submission.
! Is this an issue from the IP perspective?
! </edtext>
! </ednote>
! </div1>
!
! <div1 id="testDocuments">
! <head>Test Documents</head>
!
! <p>
! <ednote>
! <name>P Downey</name>
! <edtext>
! Test from the Microsoft submitted
! scenarios reference a version of WS-Addressing.
! dated 2004/03 and possibly not the Member Submission.
! Is this an issue from the IP perspective?
! </edtext>
! </ednote>
! </p>
!
! <table summary="Test Documents" id="testDocumentsTable" border="1">
! <caption>Test Documents</caption>
! <tbody>
! <tr>
! <th align="left">Contributor</th>
! <th align="left">Message</th>
! </tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/fault-4.xml'>fault-4.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/fault-5.xml'>fault-5.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-1.xml'>request-1.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-2.xml'>request-2.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-3.xml'>request-3.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-4.xml'>request-4.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-5.xml'>request-5.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-6.xml'>request-6.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-7.xml'>request-7.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-8.xml'>request-8.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/request-9.xml'>request-9.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-2.xml'>response-2.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-3.xml'>response-3.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-4.xml'>response-4.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-6.xml'>response-6.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-7.xml'>response-7.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-8.xml'>response-8.xml</loc></td></tr>
! <tr><td>Microsoft</td><td><loc href='http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/test-cases/Microsoft/2005Mar-0209/response-9.xml'>response-9.xml</loc></td></tr>
! </tbody>
! </table>
!
</div1>
-
<div1 id="contributing">
<head>Contributing Test Materials</head>
! <p>The Test Suite consists entirely of voluntary contributions of tests from interested parties. We encourage all members of the community to consider contributing any tests they may have developed to the Test Suite.
! </p>
! <p>
! Tests may be submitted to the Suite in the form of an Email sent to
! <loc href='mailto:public-ws-addressing-tests@w3.org'>public-ws-addressing-tests@w3.org</loc>
! An archive is available at
! <loc href='http://lists.w3.org/Archives/Public/public-ws-addressing-tests/'>http://lists.w3.org/Archives/Public/public-ws-addressing-tests</loc>
! Submited test cases should be released to the Test Suite
! by completing the
! <loc href='http://www.w3.org/2002/09/wbs/1/testgrants2-200409/'>Test Case Grant II Form</loc>.
! </p>
!
</div1>
-
<div1 id="references">
<head>References</head>
--- 96,192 ----
(<xs:anyAttribute/>).</p>
</div2>
</div1>
<div1 id="testCases">
<head>Test Cases</head>
! <p>The Test Suite comprises of a collection of <loc href="test-cases/cases/cases.html"
! >test cases</loc>. Each test case contains the following information:</p>
! <glist>
! <gitem>
! <label>identifier</label>
! <def>
! <p>An unambiguous xml:id value to enable the test case to be referenced
! within a specific version of the test suite.</p>
! </def>
! </gitem>
! <gitem>
! <label>title</label>
! <def>
! <p>A friendly name for the test case.</p>
! </def>
! </gitem>
! <gitem>
! <label>cr</label>
! <def>
! <p>An indication that this test forms part of the Exit Criteria for the
! Candidate Recommendation phase for one or more Web Service Addressing
! specifications.</p>
! </def>
! </gitem>
! <gitem>
! <label>assertions</label>
! <def>
! <p>A list of <loc href="test-cases/assertions/assertions.html"
! >assertions</loc> document the test case exhibits. The purpose of the
! assertions being to access the coverage of the Test Suite.</p>
! </def>
! </gitem>
! <gitem>
! <label>message exchange</label>
! <def>
! <p>The concrete <loc href="test-cases/assertions/message-exchanges.html">message
! exchange</loc> followed by a successful execution of the test case.</p>
! </def>
! </gitem>
! <gitem>
! <label>scenarios</label>
! <def>
! <p>A list of the abstract scenarios exhibited by the test case, at most one
! from each of the categories: <loc
! href="test-cases/assertions/scenarios.html#MessagePassing">message
! passing</loc>, <loc
! href="test-cases/assertions/scenarios.html#Security">security</loc>,
! etc.</p>
! </def>
! </gitem>
! <gitem>
! <label>description</label>
! <def>
! <p>A description of the nature and characteristics of the test case to
! assist reviewers to understand the purpose of a test and provide those
! executing the test with any additional information that will be helpful
! should the test fail.</p>
! </def>
! </gitem>
! <gitem>
! <label>documents</label>
! <def>
! <p>One or more example <loc href="test-cases/documents/documents.html"> test
! documents</loc>, including WSDL 1.1 and WSDL 2.0 documents as well as
! SOAP 1.1 and SOAP 1.2 messages which may be used to build canned test
! interactions for some test cases.</p>
! </def>
! </gitem>
! </glist>
</div1>
<div1 id="contributing">
<head>Contributing Test Materials</head>
! <p>The Test Suite consists entirely of voluntary contributions of tests from interested
! parties. We encourage all members of the community to consider contributing any
! tests they may have developed to the Test Suite.</p>
! <p> Tests may be submitted to the Suite in the form of an Email sent to<loc
! href="mailto:public-ws-addressing-tests@w3.org"
! >public-ws-addressing-tests@w3.org</loc> An archive is available at<loc
! href="http://lists.w3.org/Archives/Public/public-ws-addressing-tests/"
! >http://lists.w3.org/Archives/Public/public-ws-addressing-tests</loc> Submited
! test cases should be released to the Test Suite by completing the<loc
! href="http://www.w3.org/2002/09/wbs/1/testgrants2-200409/">Test Case Grant II
! Form</loc>.</p>
! <p> When contributing materials to the Test Suite, it is helpful if each individual test case
! cites the metadata such as the existing Test Assertions, Scenarios and Message
! Exchanges exhibited. The submission may also include details of any new scenarios
! which the test case exhibits. Providing examples of the messages exchanged and
! metadata such as WSDL 1.1 and WSDL 2.0 in the form of complete XML documents will
! also be of value.</p>
</div1>
<div1 id="references">
<head>References</head>
***************
*** 368,385 ****
href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</loc> is
available at http://www.w3.org/TR/wsdl20.</bibl>
-
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement Levels</titleref>,
S. Bradner. Internet Engineering Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt. </bibl>
! <bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt"> M.
! Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January
2005.</bibl>
-
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204">
<titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
! Consortium, 4 February 2004. This version of the XML
! 1.0 Recommendation is http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
available at http://www.w3.org/TR/REC-xml. </bibl>
--- 208,223 ----
href="http://www.w3.org/TR/wsdl20">latest version of WSDL 2.0</loc> is
available at http://www.w3.org/TR/wsdl20.</bibl>
<bibl key="IETF RFC 2119" href="http://www.ietf.org/rfc/rfc2119.txt" id="RFC2119">
<titleref>Key words for use in RFCs to Indicate Requirement Levels</titleref>,
S. Bradner. Internet Engineering Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2119.txt. </bibl>
! <bibl id="RFC3987" key="IETF RFC 3987" href="http://www.ietf.org/rfc/rfc3987.txt">
! M. Duerst, M. Suignard, "Internationalized Resource Identifiers (IRIs)", January
2005.</bibl>
<bibl id="XML10" key="XML 1.0" href="http://www.w3.org/TR/2004/REC-xml-20040204">
<titleref>Extensible Markup Language (XML) 1.0 (Third Edition)</titleref>, T.
Bray, J. Paoli, C. M. Sperberg-McQueen, and E. Maler, Editors. World Wide Web
! Consortium, 4 February 2004. This version of the XML 1.0 Recommendation is
! http://www.w3.org/TR/2004/REC-xml-20040204. The <loc
href="http://www.w3.org/TR/REC-xml">latest version of XML 1.0</loc> is
available at http://www.w3.org/TR/REC-xml. </bibl>
***************
*** 399,409 ****
href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
Set</loc> is available at http://www.w3.org/TR/xml-infoset. </bibl>
-
<bibl id="XMLSchemaP1" key="XML Schema Structures"
href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
! <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson, D. Beech, M.
! Maloney, and N. Mendelsohn, Editors. World Wide
! Web Consortium, 28 October 2004. This
! version of the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
--- 237,245 ----
href="http://www.w3.org/TR/xml-infoset">latest version of XML Information
Set</loc> is available at http://www.w3.org/TR/xml-infoset. </bibl>
<bibl id="XMLSchemaP1" key="XML Schema Structures"
href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">
! <titleref>XML Schema Part 1: Structures Second Edition</titleref>, H. Thompson,
! D. Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web Consortium, 28
! October 2004. This version of the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <loc
href="http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema Part
***************
*** 411,419 ****
<bibl key="XML Schema Datatypes" id="XMLSchemaP2"
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
! <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and A. Malhotra,
! Editors. World Wide Web Consortium, 28 October 2004. This version of the XML Schema
! Part 2 Recommendation is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The
! <loc href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
! Part 2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
<bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
--- 247,256 ----
<bibl key="XML Schema Datatypes" id="XMLSchemaP2"
href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
! <titleref>XML Schema Part 2: Datatypes Second Edition</titleref>, P. Byron and
! A. Malhotra, Editors. World Wide Web Consortium, 28 October 2004. This version
! of the XML Schema Part 2 Recommendation is
! http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <loc
! href="http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema Part
! 2</loc> is available at http://www.w3.org/TR/xmlschema-2. </bibl>
<bibl id="SOAP12-PART1" key="SOAP 1.2 Part 1: Messaging Framework"
href="http://www.w3.org/TR/2003/REC-soap12-part1-20030624/">
Received on Friday, 9 September 2005 19:18:24 UTC