WWW/2002/ws/ra/edcopies wsenum.html,1.104,1.105 wsenum.xml,1.97,1.98 wseventing.html,1.152,1.153 wseventing.xml,1.146,1.147 wsmex.html,1.95,1.96

Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv15205

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsmex.html 
Log Message:
8275


Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.152
retrieving revision 1.153
diff -u -d -r1.152 -r1.153
--- wseventing.html	26 Jan 2010 19:29:52 -0000	1.152
+++ wseventing.html	26 Jan 2010 22:47:39 -0000	1.153
@@ -616,18 +616,12 @@
        </p></dd><dt class="label"><a name="Dialect" id="Dialect"/><b>[Body]</b>/wse:Subscribe/wse:Filter/@Dialect </dt><dd><p>
         Implied value is "http://www.w3.org/2009/09/ws-evt/Dialects/XPath10".
        </p><p>
-        While an XPath predicate expression provides great
-        flexibility and power, alternate filter dialects MAY be
-        defined. For instance, a simpler, less powerful dialect might
-        be defined for resource-constrained implementations, or a new
-        dialect might be defined to support filtering based on data
-        not included in the notification message itself. If desired,
-        a filter dialect could allow the definition of a composite
-        filter that contained multiple filters from other
-        dialects.
-        New dialect definitions MUST include sufficient information for 
-        proper application. For example, it would need to include the 
-        context (which data) over which the filter operates.
+        If filtering is supported, then support for the XPath 1.0 dialect 
+        (described below) is RECOMMENDED. 
+        Alternate filter dialects can be defined. 
+        Such dialect definitions MUST include sufficient information for 
+        proper application. For example, it would need to define the context 
+        (which data) over which the filter operates.
        </p></dd><dt class="label"><b>[Body]</b>/wse:Subscribe/wse:Filter/@Dialect="<a href="http://www.w3.org/2009/09/ws-evt/Dialects/XPath10">
         http://www.w3.org/2009/09/ws-evt/Dialects/XPath10
        </a>"
@@ -2509,4 +2503,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8068">8068</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288">8288</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=8288">8288</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</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.104
retrieving revision 1.105
diff -u -d -r1.104 -r1.105
--- wsenum.html	19 Jan 2010 23:59:58 -0000	1.104
+++ wsenum.html	26 Jan 2010 22:47:39 -0000	1.105
@@ -68,11 +68,11 @@
 &nbsp;&nbsp;&nbsp;4.10 <a href="#EndToNotSupported">EndToNotSupported</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_1957">Enumeration Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;6.1 <a href="#iddiv2_1_1965">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_2052">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2238">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.1 <a href="#iddiv2_1_2060">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;8.2 <a href="#iddiv2_1_2246">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/>
@@ -478,11 +478,15 @@
         Implied value is
         "http://www.w3.org/2009/09/ws-enu/Dialects/XPath10". 
        </p><p>
-        New dialect definitions MUST include sufficient information for 
-        proper application. For example, it would need to include the 
-        context (which data) over which the filter operates. 
-       </p><p><b>[Body]</b>/wsen:Enumerate/wsen:Filter/@Dialect="http://www.w3.org/2009/09/ws-enu/Dialects/XPath10"
-       </p><p>
+        If filtering is supported, then support for the XPath 1.0 dialect
+        (described below) is RECOMMENDED.
+        Alternate filter dialects can be defined.
+        Such dialect definitions MUST include sufficient information for
+        proper application. For example, it would need to define the context
+        (which data) over which the filter operates.
+       </p></dd><dt class="label"><b>[Body]</b>/wsen:Enumerate/wsen:Filter/@Dialect="<a href="http://www.w3.org/2009/09/ws-enu/Dialects/XPath10">
+        http://www.w3.org/2009/09/ws-enu/Dialects/XPath10
+       </a></dt><dd><p>
         Value of <b>[Body]</b>/wsenu:Enumerate/wsen:Filter is
         an XPath <a href="#XPath1">[XPath1.0]</a>
         predicate expression (PredicateExpr); the context
@@ -1286,7 +1290,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_1957" id="iddiv2_1_1957"/>6.1 Enumeration Assertion</h3><p>
+<h3><a name="iddiv2_1_1965" id="iddiv2_1_1965"/>6.1 Enumeration Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the 
      WS-Enumeration specification is through the use of the Web Services 
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy - 
@@ -1389,7 +1393,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="refs" id="refs"/>8 References</h2><div class="div2">
-<h3><a name="iddiv2_1_2052" id="iddiv2_1_2052"/>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_2060" id="iddiv2_1_2060"/>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. 
@@ -1461,7 +1465,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_2238" id="iddiv2_1_2238"/>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_2246" id="iddiv2_1_2246"/>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>
@@ -1969,4 +1973,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8159">8159</a></td></tr><tr><td> 2009/12/08 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8161">8161</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8286">8286</a></td></tr><tr><td> 2010/01/19 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</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=8283">8283</a></td></tr><tr><td> 2010/01/26 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</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.97
retrieving revision 1.98
diff -u -d -r1.97 -r1.98
--- wsenum.xml	19 Jan 2010 23:59:58 -0000	1.97
+++ wsenum.xml	26 Jan 2010 22:47:39 -0000	1.98
@@ -823,14 +823,24 @@
        </p>
        
        <p>
-        New dialect definitions MUST include sufficient information for 
-        proper application. For example, it would need to include the 
-        context (which data) over which the filter operates. 
-       </p>
-       
-       <p>
-        <kw>[Body]</kw>/wsen:Enumerate/wsen:Filter/@Dialect="http://www.w3.org/&wsenu.nsprefix;/ws-enu/Dialects/XPath10"
+        If filtering is supported, then support for the XPath 1.0 dialect
+        (described below) is RECOMMENDED.
+        Alternate filter dialects can be defined.
+        Such dialect definitions MUST include sufficient information for
+        proper application. For example, it would need to define the context
+        (which data) over which the filter operates.
        </p>
+      </def>
+     </gitem>
+
+     <gitem>
+      <label><kw>[Body]</kw>/wsen:Enumerate/wsen:Filter/@Dialect="<loc
+       href="http://www.w3.org/&wsenu.nsprefix;/ws-enu/Dialects/XPath10">
+        http://www.w3.org/&wsenu.nsprefix;/ws-enu/Dialects/XPath10
+       </loc>
+      </label>
+
+      <def>
        <p>
         Value of <kw>[Body]</kw>/wsenu:Enumerate/wsen:Filter is
         an XPath <bibref ref="XPath1"/>
@@ -3605,6 +3615,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8283">8283</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/01/26 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- wsmex.html	12 Jan 2010 20:46:08 -0000	1.95
+++ wsmex.html	26 Jan 2010 22:47:39 -0000	1.96
@@ -1365,4 +1365,4 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8200">8200</a></td></tr><tr><td> 2009/12/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8297">8297</a></td></tr><tr><td> 2009/12/15 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8202">8202</a></td></tr><tr><td> 2010/01/12 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8293">8293</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=8293">8293</a></td></tr></tbody></table></div></div></body></html>

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.146
retrieving revision 1.147
diff -u -d -r1.146 -r1.147
--- wseventing.xml	26 Jan 2010 19:29:52 -0000	1.146
+++ wseventing.xml	26 Jan 2010 22:47:39 -0000	1.147
@@ -1063,18 +1063,12 @@
        </p>
 
        <p>
-        While an XPath predicate expression provides great
-        flexibility and power, alternate filter dialects MAY be
-        defined. For instance, a simpler, less powerful dialect might
-        be defined for resource-constrained implementations, or a new
-        dialect might be defined to support filtering based on data
-        not included in the notification message itself. If desired,
-        a filter dialect could allow the definition of a composite
-        filter that contained multiple filters from other
-        dialects.
-        New dialect definitions MUST include sufficient information for 
-        proper application. For example, it would need to include the 
-        context (which data) over which the filter operates.
+        If filtering is supported, then support for the XPath 1.0 dialect 
+        (described below) is RECOMMENDED. 
+        Alternate filter dialects can be defined. 
+        Such dialect definitions MUST include sufficient information for 
+        proper application. For example, it would need to define the context 
+        (which data) over which the filter operates.
        </p>
       </def>
      </gitem>
@@ -4594,6 +4588,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288">8288</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2010/01/26 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8275">8275</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Received on Tuesday, 26 January 2010 22:47:44 UTC