WWW/2002/ws/ra/test scenario.html,1.17,1.18 scenario.xml,1.18,1.19

Update of /w3ccvs/WWW/2002/ws/ra/test
In directory hutz:/tmp/cvs-serv28289

Modified Files:
	scenario.html scenario.xml 
Log Message:
Add a blurb about ws-sa and ws-evd policy


Index: scenario.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/test/scenario.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- scenario.xml	24 May 2011 17:52:14 -0000	1.18
+++ scenario.xml	21 Jun 2011 14:16:09 -0000	1.19
@@ -3966,6 +3966,18 @@
     
   </div1>
 
+  <div1 id="policy">
+   <head>WS-SOAP Assertions &amp; WS-Event Descriptions</head>
+
+   <p>
+    While this working group will not explicitly test the use of WS-Policy,
+    this test scenario allows for the inclusion of the WS-SA and 
+    WS-EVD policy assertions to appear in the WSDL of the Tracker Service.
+    In doing this the scenario is verifying that the assertions can
+    successfully be included as part of the WSDL/Policy of a service.
+   </p>
+  </div1>
+
   <div1 id="wsdl">
    <head>WSDL</head>
 

Index: scenario.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/test/scenario.html,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- scenario.html	24 May 2011 17:52:14 -0000	1.17
+++ scenario.html	21 Jun 2011 14:16:09 -0000	1.18
@@ -94,14 +94,15 @@
 &nbsp;&nbsp;&nbsp;7.12 <a href="#iddiv2x1x2534">EnumerationEnd Test</a><br/>
 &nbsp;&nbsp;&nbsp;7.13 <a href="#iddiv2x1x2589">Filter Test - XPath 1.0</a><br/>
 &nbsp;&nbsp;&nbsp;7.14 <a href="#iddiv2x1x2646">Filter Test - XPath 2.0</a><br/>
-8 <a href="#wsdl">WSDL</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2x1x2707">Event Source WSDL</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2x1x2712">Notification WSDL</a><br/>
-9 <a href="#evd">EventDescriptions</a><br/>
-10 <a href="#xsd">Schemas</a><br/>
-11 <a href="#acks">Acknowledgements</a><br/>
-12 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2751">Normative References</a><br/>
+8 <a href="#policy">WS-SOAP Assertions &amp; WS-Event Descriptions</a><br/>
+9 <a href="#wsdl">WSDL</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2x1x2713">Event Source WSDL</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2x1x2718">Notification WSDL</a><br/>
+10 <a href="#evd">EventDescriptions</a><br/>
+11 <a href="#xsd">Schemas</a><br/>
+12 <a href="#acks">Acknowledgements</a><br/>
+13 <a href="#References">References</a><br/>
+&nbsp;&nbsp;&nbsp;13.1 <a href="#iddiv2x1x2757">Normative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix-A">XML Schema</a><br/>
 B <a href="#changelog">Change Log</a><br/>
@@ -237,7 +238,7 @@
      full XML represenation of the Animal within the Body of the event.
      An EventDescriptions document that 
      describes the structure of the event information within the 
-     notifications can be found in <a href="#evd"><b>9 EventDescriptions</b></a>.
+     notifications can be found in <a href="#evd"><b>10 EventDescriptions</b></a>.
     </p></div><div class="div2">
 <h3><a name="iddiv2x1x686" id="iddiv2x1x686"/>3.3 Structure of Test Sections</h3><p>
      The following sections describe tests designed to exercise all the 
@@ -1777,20 +1778,27 @@
           filter will never evaluate to true for the lifetime of 
           the enumeration.
         </p></div></div></div><div class="div1">
-<h2><a name="wsdl" id="wsdl"/>8 WSDL</h2><div class="div2">
-<h3><a name="iddiv2x1x2707" id="iddiv2x1x2707"/>8.1 Event Source WSDL</h3><p>
+<h2><a name="policy" id="policy"/>8 WS-SOAP Assertions &amp; WS-Event Descriptions</h2><p>
+    While this working group will not explicitly test the use of WS-Policy,
+    this test scenario allows for the inclusion of the WS-SA and 
+    WS-EVD policy assertions to appear in the WSDL of the Tracker Service.
+    In doing this the scenario is verifying that the assertions can
+    successfully be included as part of the WSDL/Policy of a service.
+   </p></div><div class="div1">
+<h2><a name="wsdl" id="wsdl"/>9 WSDL</h2><div class="div2">
+<h3><a name="iddiv2x1x2713" id="iddiv2x1x2713"/>9.1 Event Source WSDL</h3><p>
      TBD
     </p></div><div class="div2">
-<h3><a name="iddiv2x1x2712" id="iddiv2x1x2712"/>8.2 Notification WSDL</h3><p>
+<h3><a name="iddiv2x1x2718" id="iddiv2x1x2718"/>9.2 Notification WSDL</h3><p>
      Available here:
     <a href="http://www.w3.org/2002/ws/ra/test/scenario/scenarioSink.wsdl">http://www.w3.org/2002/ws/ra/test/scenario/scenarioSink.wsdl</a></p></div></div><div class="div1">
-<h2><a name="evd" id="evd"/>9 EventDescriptions</h2><p>
+<h2><a name="evd" id="evd"/>10 EventDescriptions</h2><p>
      Available here:
     <a href="http://www.w3.org/2002/ws/ra/test/scenario/scenarioSource.evd">http://www.w3.org/2002/ws/ra/test/scenario/scenarioSource.evd</a></p></div><div class="div1">
-<h2><a name="xsd" id="xsd"/>10 Schemas</h2><p>
+<h2><a name="xsd" id="xsd"/>11 Schemas</h2><p>
     TBD
    </p></div><div class="div1">
-<h2><a name="acks" id="acks"/>11 Acknowledgements</h2><p>
+<h2><a name="acks" id="acks"/>12 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
      Alessio Soldano (Red Hat),
@@ -1820,8 +1828,8 @@
      Wu Chou (Avaya Communications),
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
-<h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2x1x2751" id="iddiv2x1x2751"/>12.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="References" id="References"/>13 References</h2><div class="div2">
+<h3><a name="iddiv2x1x2757" id="iddiv2x1x2757"/>13.1 Normative References</h3><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC 2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.

Received on Tuesday, 21 June 2011 14:16:13 UTC