W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > March 2010

WWW/2002/ws/ra/edcopies wsenum.html,1.122,1.123 wsenum.xml,1.113,1.114 wseventing.html,1.169,1.170 wseventing.xml,1.161,1.162

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 17 Mar 2010 03:22:18 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Nrjpq-00007H-LF@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv343

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
Log Message:
8886


Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.161
retrieving revision 1.162
diff -u -d -r1.161 -r1.162
--- wseventing.xml	16 Mar 2010 19:49:32 -0000	1.161
+++ wseventing.xml	17 Mar 2010 03:22:16 -0000	1.162
@@ -1822,6 +1822,15 @@
      was present in the Subscribe message for that subscription 
      (see <specref ref="Subscribe"/>), the SubscriptionEnd message
      MUST be sent to the endpoint reference indicated by that EPR. 
+    </p>
+
+    <p>
+     Note, a subscription expiring as expected is not considered to be 
+     an unexpected termination, therefore a SubscriptionEnd message MUST NOT
+     be sent in this case.
+    </p>
+    
+    <p>
      The message MUST be of the following form:
     </p>
 
@@ -5001,6 +5010,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/16 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.169
retrieving revision 1.170
diff -u -d -r1.169 -r1.170
--- wseventing.html	16 Mar 2010 19:49:32 -0000	1.169
+++ wseventing.html	17 Mar 2010 03:22:16 -0000	1.170
@@ -76,22 +76,22 @@
 &nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</a><br/>
 8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
 9 <a href="#metadata">WS-Eventing Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2170">EventSource Assertion</a><br/>
-&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2281">SubscriptionManager Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.1 <a href="#iddiv2_1_2174">EventSource Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;9.2 <a href="#iddiv2_1_2285">SubscriptionManager Assertion</a><br/>
 10 <a href="#acks">Acknowledgements</a><br/>
 11 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2363">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2497">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_2367">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;11.2 <a href="#iddiv2_1_2501">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
 &nbsp;&nbsp;&nbsp;A.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2699">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2720">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2725">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2743">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2703">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2724">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2729">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2747">Binding for Wrapped Notifications</a><br/>
 &nbsp;&nbsp;&nbsp;A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2770">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2791">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2774">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2795">Multiple Event Information Metadata Sections</a><br/>
 B <a href="#Schema">XML Schema</a><br/>
 C <a href="#WSDL">WSDL</a><br/>
 D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -1151,6 +1151,11 @@
      was present in the Subscribe message for that subscription 
      (see <a href="#Subscribe"><b>4.1 Subscribe</b></a>), the SubscriptionEnd message
      MUST be sent to the endpoint reference indicated by that EPR. 
+    </p><p>
+     Note, a subscription expiring as expected is not considered to be 
+     an unexpected termination, therefore a SubscriptionEnd message MUST NOT
+     be sent in this case.
+    </p><p>
      The message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2002/ws/ra/edcopies/ws-evt/SubscriptionEnd
@@ -1516,7 +1521,7 @@
     that indicate a particular security mechanism used to protect
     the WS-Eventing operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_2170" id="iddiv2_1_2170"/>9.1 EventSource Assertion</h3><p>
+<h3><a name="iddiv2_1_2174" id="iddiv2_1_2174"/>9.1 EventSource Assertion</h3><p>
      Services indicate support for the WS-Eventing's definition 
      of an event source through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1617,7 +1622,7 @@
      Note: The WS-RA WG is interested in Last Call feedback on the use
      of nested policy expressions.
     </p></div><div class="div2">
-<h3><a name="iddiv2_1_2281" id="iddiv2_1_2281"/>9.2 SubscriptionManager Assertion</h3><p>
+<h3><a name="iddiv2_1_2285" id="iddiv2_1_2285"/>9.2 SubscriptionManager Assertion</h3><p>
      Services indicate support for the
      WS-Eventing's definition of a subscription manager 
      through the use of the Web Services
@@ -1715,7 +1720,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>11 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2363" id="iddiv2_1_2363"/>11.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>
+<h3><a name="iddiv2_1_2367" id="iddiv2_1_2367"/>11.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.
@@ -1767,7 +1772,7 @@
        , A. Vedamuthu, et al., Editors.
        World Wide Web Consortium (W3C), 4 September 2007.
       Available at <a href="http://www.w3.org/TR/ws-policy-attach">http://www.w3.org/TR/ws-policy-attach</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2497" id="iddiv2_1_2497"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
+<h3><a name="iddiv2_1_2501" id="iddiv2_1_2501"/>11.2 Informative References</h3><dl><dt class="label"><a name="WSMC" id="WSMC"/>WS-MakeConnection</dt><dd><a href="http://docs.oasis-open.org/ws-rx/wsmc/v1.1/wsmc.doc"><cite>
         OASIS Standard, "Web Services Make Connection (WS-MakeConnection) 1.1"
         Web Services Make Connection (WS-MakeConnection)
        </cite></a>
@@ -1871,7 +1876,7 @@
      serve as a description of the Event Type used in 
      <a href="#Table1">Example 2-1</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2689" id="idexample_1_2689"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2693" id="idexample_1_2693"/>Example A-1: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
 (02)        targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/2002/ws/ra/edcopies/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1891,7 +1896,7 @@
      GED for this Event Type is defined on line (08) as being of type 
      "{http://www.example.org/oceanwatch}:WindReportType". 
     </p><div class="div3">
-<h4><a name="iddiv3_1_2699" id="iddiv3_1_2699"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2703" id="iddiv3_1_2703"/>A.1.1 Retrieving Event Descriptions</h4><p>
       Although there are many ways in which an event source can make its 
       EventDescriptions available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1902,7 +1907,7 @@
       be equal to the value of its wse:EventDescriptions/@targetNamespace. An 
       event source MUST NOT have more than one EventDescriptions document.
      </p></div><div class="div3">
-<h4><a name="iddiv3_1_2720" id="iddiv3_1_2720"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2724" id="iddiv3_1_2724"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it MUST be possible to determine how a 
       given wse:eventType will appear on the wire as a notification in a 
       subscription created with that format. The following sections define 
@@ -1914,7 +1919,7 @@
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the notification operations. 
      </p><div class="div4">
-<h5><a name="iddiv4_1_2725" id="iddiv4_1_2725"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2729" id="iddiv4_1_2729"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
        The information about an Event Type contained in the wse:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
@@ -1928,7 +1933,7 @@
          of the wse:eventType element corresponding to the type of the 
          event being transmitted.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2743" id="iddiv4_1_2743"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2747" id="iddiv4_1_2747"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
        The information about an Event Type contained in the eventType element 
        binds to a Wrapped Notification for that type as follows: 
       </p><ul><li><p>
@@ -1952,7 +1957,7 @@
      successful Subscribe request that used a particular Format IRI. The 
      following is an example of a Notification WSDL: 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2764" id="idexample_1_2764"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2768" id="idexample_1_2768"/>Example A-2: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 (02)                   targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)                   xmlns:xs="http://www.w3.org/2001/XMLSchema"
 (04)                   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1987,7 +1992,7 @@
 (33)     &lt;/wsdl:operation&gt;
 (34)   &lt;/wsdl:binding&gt;
 (35) &lt;/wsdl:definitions&gt;</pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2770" id="iddiv3_1_2770"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2774" id="iddiv3_1_2774"/>A.2.1 Retrieving Notification WSDLs</h4><p>
       Although there are many ways in which an event source can make 
       Notification WSDLs available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -2003,7 +2008,7 @@
       Format IRI/@Identifier, there MUST NOT exist more than one 
       Notification WSDL document. 
      </p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2791" id="iddiv2_1_2791"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2795" id="iddiv2_1_2795"/>A.3 Multiple Event Information Metadata Sections</h3><p>
      When WS-MetadataExchange is used to retrieve metadata about an event 
      source, recipients of mex:Metadata elements that contain Metadata 
      Sections with both the 
@@ -2695,4 +2700,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271">8271</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -d -r1.122 -r1.123
--- wsenum.html	16 Mar 2010 19:49:32 -0000	1.122
+++ wsenum.html	17 Mar 2010 03:22:16 -0000	1.123
@@ -69,11 +69,11 @@
 &nbsp;&nbsp;&nbsp;4.11 <a href="#EmptyFilter">EmptyFilter</a><br/>
 5 <a href="#Security">Security Considerations</a><br/>
 6 <a href="#metadata">WS-Enumeration Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_2019">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_2023">Enumeration Assertion</a><br/>
 7 <a href="#acks">Acknowledgements</a><br/>
 8 <a href="#refs">References</a><br/>
-&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2134">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2320">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2138">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2324">Informative References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#schema">XML Schema</a><br/>
 B <a href="#WSDL">WSDL</a><br/>
@@ -1039,6 +1039,11 @@
      Enumerate message for that enumeration (see <a href="#Enumerate"><b>3.1 Enumerate</b></a>),
      the EnumerationEnd message MUST be sent to the endpoint reference 
      indicated by that EPR. 
+    </p><p>
+     Note, a enumeration context expiring as expected is not considered to 
+     be an unexpected termination, therefore a EnumerationEnd message MUST NOT
+     be sent in this case.
+    </p><p>
      The message MUST be of the following form:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2002/ws/ra/edcopies/ws-enu/EnumerationEnd
@@ -1307,7 +1312,7 @@
     that indicate a particular security mechanism used to protect 
     the WS-Enumeration operations supported by this endpoint. 
    </p><div class="div2">
-<h3><a name="iddiv2_1_2019" id="iddiv2_1_2019"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_2023" id="iddiv2_1_2023"/>6.1 Enumeration Assertion</h3><p>
      Services indicate support for the WS-Enumeration's definition of a 
      data source through the use of the Web Services 
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
@@ -1430,7 +1435,7 @@
      Yves Lafon (W3C/ERCIM).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2134" id="iddiv2_1_2134"/>8.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>
+<h3><a name="iddiv2_1_2138" id="iddiv2_1_2138"/>8.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. 
@@ -1502,7 +1507,7 @@
        , J. Clark, S. DeRose, Editors.
        World Wide Web Consortium (W3C), 16 November 1999. 
       Available at <a href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_2320" id="iddiv2_1_2320"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
+<h3><a name="iddiv2_1_2324" id="iddiv2_1_2324"/>8.2 Informative References</h3><dl><dt class="label"><a name="MEX" id="MEX"/>WS-MetadataExchange</dt><dd><a href="http://www.w3.org/TR/ws-metadata-exchange"><cite>
         W3C Working Group Draft, "Web Services Metadata Exchange
           (WS-MetadataExchange) 1.1"
        </cite></a>
@@ -2124,4 +2129,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8306">8306</a></td></tr><tr><td> 2010/03/09 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6463">6463</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8031">8031</a>,
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</a></td></tr><tr><td> 2010/03/16 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -d -r1.113 -r1.114
--- wsenum.xml	16 Mar 2010 19:49:32 -0000	1.113
+++ wsenum.xml	17 Mar 2010 03:22:16 -0000	1.114
@@ -1708,6 +1708,15 @@
      Enumerate message for that enumeration (see <specref ref="Enumerate"/>),
      the EnumerationEnd message MUST be sent to the endpoint reference 
      indicated by that EPR. 
+    </p>
+
+    <p>
+     Note, a enumeration context expiring as expected is not considered to 
+     be an unexpected termination, therefore a EnumerationEnd message MUST NOT
+     be sent in this case.
+    </p>
+
+    <p>
      The message MUST be of the following form:
     </p>
 
@@ -3996,6 +4005,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8198">8198</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/03/16 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8886">8886</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Wednesday, 17 March 2010 03:22:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 17 March 2010 03:22:28 GMT