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

WWW/2002/ws/ra/edcopies wsenum.html,1.57,1.58 wsenum.xml,1.48,1.49 wseventing.html,1.79,1.80 wseventing.xml,1.70,1.71 wsfrag.html,1.10,1.11 wsfrag.xml,1.10,1.11 wsmex.html,1.55,1.56 wsmex.xml,1.44,1.45 wsrt.html,1.49,1.50 wsrt.xml,1.38,1.39 wst.html,1.56,1.57 wst.xml,1.52,1.53

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 02 Sep 2009 11:36:59 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1Mio95-0000oh-MB@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv3013

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsfrag.html wsfrag.xml wsmex.html wsmex.xml wsrt.html wsrt.xml 
	wst.html wst.xml 
Log Message:
6694


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -d -r1.52 -r1.53
--- wst.xml	1 Sep 2009 22:21:16 -0000	1.52
+++ wst.xml	2 Sep 2009 11:36:57 -0000	1.53
@@ -1520,6 +1520,19 @@
         </item>
       </ulist>
     </div1>
+
+    <div1 id="policy">
+     <head>WS-Transfer Policy Assertion(s)</head>
+
+     <p>
+      An endpoint MAY indicate that it supports WS-Transfer, or its features,
+      by including the WS-Transfer Policy assertion(s) within its WSDL. By
+      doing so the endpoint is indicating that the corresponding WS-Transfer
+      operations are supported by that endpoint even though they do not
+      explicitly appear in its WSDL.
+     </p>
+    </div1>
+
     <div1 id="acks">
       <head>Acknowledgements</head>
       <p>
@@ -2069,6 +2082,13 @@
             <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6704">6704</loc>
           </td>
         </tr>
+        <tr>
+          <td> 2009/09/02 </td>
+          <td> DD </td>
+          <td> Added resolution of issue 
+            <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
+          </td>
+        </tr>
       </tbody>
      </table>
     </div1>

Index: wsrt.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- wsrt.xml	1 Sep 2009 22:33:11 -0000	1.38
+++ wsrt.xml	2 Sep 2009 11:36:57 -0000	1.39
@@ -2644,7 +2644,7 @@
   </div1>
 
   <div1 id="security">
-   <head>Security</head>
+   <head>Security Considerations</head>
  
    <p>
     It is strongly RECOMMENDED that the communication between services be
@@ -2677,6 +2677,18 @@
    </p>
   </div1>
 
+  <div1 id="policy">
+   <head>WS-ResourceTransfer Policy Assertion(s)</head>
+
+   <p>
+    An endpoint MAY indicate that it supports WS-ResourceTransfer, or its 
+    features, by including the WS-ResourceTransfer Policy assertion(s) within 
+    its WSDL. By doing so the endpoint is indicating that the corresponding 
+    WS-ResourceTransfer operations are supported by that endpoint even 
+    though they do not explicitly appear in its WSDL.
+   </p>
+  </div1>
+
   <div1 id="acks">
    <head>Acknowledgements</head>
  
@@ -3847,6 +3859,13 @@
        <loc href="http://www.w4.org/Bugs/Public/show_bug.cgi?id=6703">6703</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w4.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- wseventing.html	1 Sep 2009 22:18:37 -0000	1.79
+++ wseventing.html	2 Sep 2009 11:36:57 -0000	1.80
@@ -76,8 +76,9 @@
 &nbsp;&nbsp;&nbsp;7.1 <a href="#MessageSecurity">Message Security</a><br/>
 &nbsp;&nbsp;&nbsp;7.2 <a href="#AccessControl">Access Control</a><br/>
 8 <a href="#ImplConsideration">Implementation Considerations</a><br/>
-9 <a href="#acks">Acknowledgements</a><br/>
-10 <a href="#refs">References</a><br/>
+9 <a href="#policy">WS-Eventing Policy Assertion(s)</a><br/>
+10 <a href="#acks">Acknowledgements</a><br/>
+11 <a href="#refs">References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Metadata">Service Metadata for Eventing</a><br/>
 B <a href="#Schema">XML Schema</a><br/>
@@ -1448,7 +1449,14 @@
     notifications after receiving an unsubscribe response
     message.
    </p></div><div class="div1">
-<h2><a name="acks" id="acks"/>9 Acknowledgements</h2><p>
+<h2><a name="policy" id="policy"/>9 WS-Eventing Policy Assertion(s)</h2><p>
+    An endpoint MAY indicate that it supports WS-Eventing, or its features, 
+    by including the WS-Eventing Policy assertion(s) within its WSDL. By 
+    doing so the endpoint is indicating that the corresponding WS-Eventing 
+    operations are supported by that endpoint even though they do not 
+    explicitly appear in its WSDL.
+   </p></div><div class="div1">
+<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
       Ashok Malhotra (Oracle Corp.),
@@ -1471,7 +1479,7 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>10 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>11 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</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, March 1997.
@@ -2088,4 +2096,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7235">7235</a></td></tr><tr><td> 2009/08/26 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7160">7160</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</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=6700">6700</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsrt.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsrt.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- wsrt.html	1 Sep 2009 22:33:11 -0000	1.49
+++ wsrt.html	2 Sep 2009 11:36:57 -0000	1.50
@@ -73,9 +73,10 @@
 &nbsp;&nbsp;&nbsp;5.11 <a href="#createfault">CreateFault</a><br/>
 &nbsp;&nbsp;&nbsp;5.12 <a href="#exceedmulti">MultipartLimitExceededFault</a><br/>
 &nbsp;&nbsp;&nbsp;5.13 <a href="#putsyntaxfault">InvalidPutSyntaxFault</a><br/>
-6 <a href="#security">Security</a><br/>
-7 <a href="#acks">Acknowledgements</a><br/>
-8 <a href="#refs">References</a><br/>
+6 <a href="#security">Security Considerations</a><br/>
+7 <a href="#policy">WS-ResourceTransfer Policy Assertion(s)</a><br/>
+8 <a href="#acks">Acknowledgements</a><br/>
+9 <a href="#refs">References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#a_xpath1">XPath Level 1</a><br/>
 B <a href="#rt_metadata">Resource Metadata Content</a><br/>
@@ -1431,7 +1432,7 @@
     </p><a name="tab_putsyntaxfault" id="tab_putsyntaxfault"/><table border="1"><tbody><tr><th align="left"><b>[Action]</b></th><th align="left"> 
         http://www.w3.org/2009/02/ws-rst/fault 
        </th></tr><tr><td><b>[Code]</b></td><td> s12:Sender </td></tr><tr><td><b>[Subcode]</b></td><td> wsrt:InvalidRemoveSyntaxFault </td></tr><tr><td><b>[Reason]</b></td><td> Invalid syntax used for Put request </td></tr><tr><td><b>[Detail]</b></td><td/></tr></tbody></table></div></div><div class="div1">
-<h2><a name="security" id="security"/>6 Security</h2><p>
+<h2><a name="security" id="security"/>6 Security Considerations</h2><p>
     It is strongly RECOMMENDED that the communication between services be
      secured using the mechanisms described in <a href="#WSSec">[WS-Security]</a>.
    </p><p>
@@ -1454,7 +1455,14 @@
     references independent of transfer (e.g. embedded signatures and 
     encryption) are also out-of-scope.
    </p></div><div class="div1">
-<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
+<h2><a name="policy" id="policy"/>7 WS-ResourceTransfer Policy Assertion(s)</h2><p>
+    An endpoint MAY indicate that it supports WS-ResourceTransfer, or its 
+    features, by including the WS-ResourceTransfer Policy assertion(s) within 
+    its WSDL. By doing so the endpoint is indicating that the corresponding 
+    WS-ResourceTransfer operations are supported by that endpoint even 
+    though they do not explicitly appear in its WSDL.
+   </p></div><div class="div1">
+<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including:  
       Ashok Malhotra (Oracle Corp.),
@@ -1477,7 +1485,7 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>8 References</h2><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="refs" id="refs"/>9 References</h2><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, Harvard University, March 1997.
@@ -2152,4 +2160,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7429">7429</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w4.org/Bugs/Public/show_bug.cgi?id=6703">6703</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
+       <a href="http://www.w4.org/Bugs/Public/show_bug.cgi?id=6703">6703</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w4.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsfrag.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- wsfrag.xml	1 Sep 2009 22:40:13 -0000	1.10
+++ wsfrag.xml	2 Sep 2009 11:36:57 -0000	1.11
@@ -1670,6 +1670,18 @@
 
   </div1>
 
+  <div1 id="policy">
+   <head>WS-Fragment Policy Assertion(s)</head>
+
+   <p>
+    An endpoint MAY indicate that it supports WS-Fragment, or its features,
+    by including the WS-Fragment Policy assertion(s) within its WSDL. By
+    doing so the endpoint is indicating that the corresponding WS-Fragment
+    operations are supported by that endpoint even though they do not
+    explicitly appear in its WSDL.
+   </p>
+  </div1>
+
   <div1 id="acks">
    <head>Acknowledgements</head>
    <p>
@@ -1899,6 +1911,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsfrag.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsfrag.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- wsfrag.html	1 Sep 2009 22:40:13 -0000	1.10
+++ wsfrag.html	2 Sep 2009 11:36:57 -0000	1.11
@@ -64,8 +64,9 @@
 7 <a href="#XPath10">XPath 1.0 Expression Language</a><br/>
 8 <a href="#Faults">Faults</a><br/>
 &nbsp;&nbsp;&nbsp;8.1 <a href="#UnsupportedLanguage">UnsupportedLanguage</a><br/>
-9 <a href="#acks">Acknowledgements</a><br/>
-10 <a href="#refs">References</a><br/>
+9 <a href="#policy">WS-Fragment Policy Assertion(s)</a><br/>
+10 <a href="#acks">Acknowledgements</a><br/>
+11 <a href="#refs">References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
 B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -895,7 +896,14 @@
     </p><a name="Table3" id="Table3"/><table border="1" cellpadding="5"><tbody><tr><th align="left"><b>[Code]</b></th><td>s:Sender</td></tr><tr><th align="left"><b>[Subcode]</b></th><td>wst:UnknownLanguage</td></tr><tr><th align="left"><b>[Reason]</b></th><td>
         The specified Language URI is not known.
        </td></tr><tr><th align="left"><b>[Detail]</b></th><td><em>The unknown URI if specified</em></td></tr></tbody></table></div></div><div class="div1">
-<h2><a name="acks" id="acks"/>9 Acknowledgements</h2><p>
+<h2><a name="policy" id="policy"/>9 WS-Fragment Policy Assertion(s)</h2><p>
+    An endpoint MAY indicate that it supports WS-Fragment, or its features,
+    by including the WS-Fragment Policy assertion(s) within its WSDL. By
+    doing so the endpoint is indicating that the corresponding WS-Fragment
+    operations are supported by that endpoint even though they do not
+    explicitly appear in its WSDL.
+   </p></div><div class="div1">
+<h2><a name="acks" id="acks"/>10 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
      Ashok Malhotra (Oracle Corp.),
@@ -918,7 +926,7 @@
      Wu Chou (Avaya Communications),
      Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>10 References</h2><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="refs" id="refs"/>11 References</h2><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, Harvard University, March 1997.
@@ -1001,7 +1009,8 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7206">7206</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7197">7197</a></td></tr><tr><td> 2009/08/18 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a></td></tr></tbody></table></div><div class="div1">
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr></tbody></table></div><div class="div1">
 <h2><a name="Questions" id="Questions"/>D Open Questions and Actions</h2><p>
     Ram - If the expression resolves to a non-existent node should it fault
       or do nothing?

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- wst.html	1 Sep 2009 22:21:16 -0000	1.56
+++ wst.html	2 Sep 2009 11:36:57 -0000	1.57
@@ -57,8 +57,9 @@
 &nbsp;&nbsp;&nbsp;5.2 <a href="#UnknownDialect">UnknownDialect</a><br/>
 &nbsp;&nbsp;&nbsp;5.3 <a href="#PutDenied">PutDenied</a><br/>
 6 <a href="#Security_Considerations">Security Considerations</a><br/>
-7 <a href="#acks">Acknowledgements</a><br/>
-8 <a href="#refs">References</a><br/>
+7 <a href="#policy">WS-Transfer Policy Assertion(s)</a><br/>
+8 <a href="#acks">Acknowledgements</a><br/>
+9 <a href="#refs">References</a><br/>
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Appendix_I__E2_80_93_XSD">XML Schema</a><br/>
 B <a href="#Appendix_II__E2_80_93_WSDL">WSDL</a><br/>
@@ -857,7 +858,14 @@
      denial of service attacks are harder to avoid and are outside the scope
      of this specification. That said, care SHOULD be taken to ensure that
      minimal state is saved prior to any authenticating sequences.</p></li></ul></div><div class="div1">
-<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
+<h2><a name="policy" id="policy"/>7 WS-Transfer Policy Assertion(s)</h2><p>
+      An endpoint MAY indicate that it supports WS-Transfer, or its features,
+      by including the WS-Transfer Policy assertion(s) within its WSDL. By
+      doing so the endpoint is indicating that the corresponding WS-Transfer
+      operations are supported by that endpoint even though they do not
+      explicitly appear in its WSDL.
+     </p></div><div class="div1">
+<h2><a name="acks" id="acks"/>8 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
       Ashok Malhotra (Oracle Corp.),
@@ -880,7 +888,7 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>8 References</h2><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="refs" id="refs"/>9 References</h2><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, Harvard University, March 1997.
@@ -1161,4 +1169,5 @@
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7191">7191</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
-            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6704">6704</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=6704">6704</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -d -r1.44 -r1.45
--- wsmex.xml	1 Sep 2009 22:35:38 -0000	1.44
+++ wsmex.xml	2 Sep 2009 11:36:57 -0000	1.45
@@ -1473,7 +1473,7 @@
   </div1>
 
   <div1 id="Security">
-   <head>Security</head>
+   <head>Security Considerations</head>
 
    <p>
     It is strongly RECOMMENDED that the communication between Web services 
@@ -1587,6 +1587,18 @@
     </item>
    </ulist>
   </div1>
+
+  <div1 id="policy">
+   <head>WS-MetadataExchange Policy Assertion(s)</head>
+
+   <p>
+    An endpoint MAY indicate that it supports WS-MetadataExchange, or its 
+    features, by including the WS-MetadataExchange Policy assertion(s) within 
+    its WSDL. By doing so the endpoint is indicating that the corresponding 
+    WS-MetadataExchange operations are supported by that endpoint even 
+    though they do not explicitly appear in its WSDL.
+   </p>
+  </div1>
   
   <div1 id="Acknowledgements">
    <head>Acknowledgements</head>
@@ -2103,6 +2115,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6702">6702</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -d -r1.57 -r1.58
--- wsenum.html	1 Sep 2009 22:38:13 -0000	1.57
+++ wsenum.html	2 Sep 2009 11:36:56 -0000	1.58
@@ -66,8 +66,9 @@
 &nbsp;&nbsp;&nbsp;4.8 <a href="#UnableToRenew">UnableToRenew</a><br/>
 &nbsp;&nbsp;&nbsp;4.9 <a href="#UnusableEPR">UnusableEPR</a><br/>
 5 <a href="#Security">Security Considerations</a><br/>
-6 <a href="#acks">Acknowledgements</a><br/>
-7 <a href="#refs">References</a><br/>
+6 <a href="#policy">WS-Enumeration Policy Assertion(s)</a><br/>
+7 <a href="#acks">Acknowledgements</a><br/>
+8 <a href="#refs">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/>
@@ -1234,7 +1235,14 @@
       taken to ensure that minimal state is saved prior to any
       authenticating sequences.
      </p></li></ul></div><div class="div1">
-<h2><a name="acks" id="acks"/>6 Acknowledgements</h2><p>
+<h2><a name="policy" id="policy"/>6 WS-Enumeration Policy Assertion(s)</h2><p>
+    An endpoint MAY indicate that it supports WS-Enumeration, or its features,
+    by including the WS-Enumeration Policy assertion(s) within its WSDL. By
+    doing so the endpoint is indicating that the corresponding WS-Enumeration
+    operations are supported by that endpoint even though they do not
+    explicitly appear in its WSDL.
+   </p></div><div class="div1">
+<h2><a name="acks" id="acks"/>7 Acknowledgements</h2><p>
     This specification has been developed as a
     result of joint work with many individuals and teams,
     including: 
@@ -1258,7 +1266,7 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="refs" id="refs"/>7 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</dt><dd><a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>
+<h2><a name="refs" id="refs"/>8 References</h2><dl><dt class="label"><a name="RFC2119" id="RFC2119"/>RFC2119</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, March 1997.
@@ -1706,4 +1714,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7235">7235</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6701">6701</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=6701">6701</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</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.48
retrieving revision 1.49
diff -u -d -r1.48 -r1.49
--- wsenum.xml	1 Sep 2009 22:38:13 -0000	1.48
+++ wsenum.xml	2 Sep 2009 11:36:57 -0000	1.49
@@ -2266,6 +2266,18 @@
    </ulist>
   </div1>
 
+  <div1 id="policy">
+   <head>WS-Enumeration Policy Assertion(s)</head>
+
+   <p>
+    An endpoint MAY indicate that it supports WS-Enumeration, or its features,
+    by including the WS-Enumeration Policy assertion(s) within its WSDL. By
+    doing so the endpoint is indicating that the corresponding WS-Enumeration
+    operations are supported by that endpoint even though they do not
+    explicitly appear in its WSDL.
+   </p>
+  </div1>
+
   <div1 id="acks">
    <head>Acknowledgements</head>
 
@@ -3024,6 +3036,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6701">6701</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -d -r1.55 -r1.56
--- wsmex.html	1 Sep 2009 22:35:38 -0000	1.55
+++ wsmex.html	2 Sep 2009 11:36:57 -0000	1.56
@@ -58,9 +58,10 @@
 &nbsp;&nbsp;&nbsp;6.2 <a href="#Get-Metadata">Get Metadata</a><br/>
 7 <a href="#Metadata-in-Endpoint-References">Metadata in Endpoint References</a><br/>
 8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
-9 <a href="#Security">Security</a><br/>
-10 <a href="#Acknowledgements">Acknowledgements</a><br/>
-11 <a href="#References">References</a><br/>
+9 <a href="#Security">Security Considerations</a><br/>
+10 <a href="#policy">WS-MetadataExchange Policy Assertion(s)</a><br/>
+11 <a href="#Acknowledgements">Acknowledgements</a><br/>
+12 <a href="#References">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="#Appendix-B">WSDL</a><br/>
@@ -863,7 +864,7 @@
     metadata retrieval MAY be defined by communities within the 
     context of particular application domains. 
    </p></div><div class="div1">
-<h2><a name="Security" id="Security"/>9 Security</h2><p>
+<h2><a name="Security" id="Security"/>9 Security Considerations</h2><p>
     It is strongly RECOMMENDED that the communication between Web services 
     be secured using the mechanisms described in WS-Security 
     <a href="#WS-Security">[WS-Security]</a>. In order to properly secure messages, 
@@ -933,7 +934,14 @@
       technologies, such as sequencing, can also be used to prevent 
       replay of application messages.
      </p></li></ul></div><div class="div1">
-<h2><a name="Acknowledgements" id="Acknowledgements"/>10 Acknowledgements</h2><p>
+<h2><a name="policy" id="policy"/>10 WS-MetadataExchange Policy Assertion(s)</h2><p>
+    An endpoint MAY indicate that it supports WS-MetadataExchange, or its 
+    features, by including the WS-MetadataExchange Policy assertion(s) within 
+    its WSDL. By doing so the endpoint is indicating that the corresponding 
+    WS-MetadataExchange operations are supported by that endpoint even 
+    though they do not explicitly appear in its WSDL.
+   </p></div><div class="div1">
+<h2><a name="Acknowledgements" id="Acknowledgements"/>11 Acknowledgements</h2><p>
     This specification has been developed as a result of joint
     work with many individuals and teams, including: 
       Ashok Malhotra (Oracle Corp.),
@@ -956,7 +964,7 @@
       Wu Chou (Avaya Communications),
       Yves Lafon (W3C)
    </p></div><div class="div1">
-<h2><a name="References" id="References"/>11 References</h2><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"/>12 References</h2><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, Harvard University, March 1997.
@@ -1171,4 +1179,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7195">7195</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6702">6702</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=6702">6702</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -d -r1.70 -r1.71
--- wseventing.xml	1 Sep 2009 22:18:37 -0000	1.70
+++ wseventing.xml	2 Sep 2009 11:36:57 -0000	1.71
@@ -2625,7 +2625,7 @@
    </div2>
 
   </div1>
-  
+
   <div1 id="ImplConsideration">
    <head>Implementation Considerations</head>
 
@@ -2644,6 +2644,18 @@
    </p>
   </div1>
 
+  <div1 id="policy">
+   <head>WS-Eventing Policy Assertion(s)</head>
+
+   <p>
+    An endpoint MAY indicate that it supports WS-Eventing, or its features, 
+    by including the WS-Eventing Policy assertion(s) within its WSDL. By 
+    doing so the endpoint is indicating that the corresponding WS-Eventing 
+    operations are supported by that endpoint even though they do not 
+    explicitly appear in its WSDL.
+   </p>
+  </div1>
+  
   <div1 id="acks">
    <head>Acknowledgements</head>
 
@@ -3744,6 +3756,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Wednesday, 2 September 2009 11:37:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 2 September 2009 11:37:10 GMT