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

WWW/2002/ws/ra/edcopies wsmex.html,1.88,1.89 wsmex.xml,1.78,1.79

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 01 Dec 2009 22:23:52 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1NFb8S-0006N7-NO@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv24321

Modified Files:
	wsmex.html wsmex.xml 
Log Message:
8203


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -d -r1.78 -r1.79
--- wsmex.xml	1 Dec 2009 22:21:28 -0000	1.78
+++ wsmex.xml	1 Dec 2009 22:23:50 -0000	1.79
@@ -1229,12 +1229,6 @@
     </glist>
 
     <p>
-     An endpoint MAY respond with a fault message using the standard 
-     fault codes defined in WS-Addressing 
-     <bibref ref='AddrCore'/> (e.g., wsa:ActionNotSupported).
-    </p>
-
-    <p>
      If an endpoint accepts a GetMetadata request, it MUST reply with 
      a GetMetadataResponse message. The normative outline for a 
      GetMetadataResponse is:
@@ -2510,6 +2504,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8291">8291</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/12/01 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8203">8203</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -d -r1.88 -r1.89
--- wsmex.html	1 Dec 2009 22:21:28 -0000	1.88
+++ wsmex.html	1 Dec 2009 22:23:50 -0000	1.89
@@ -61,11 +61,11 @@
 9 <a href="#ImplicitWSDL">Exposing WSDL for Operations Implicitly Defined by a Policy Assertion</a><br/>
 10 <a href="#Security">Security Considerations</a><br/>
 11 <a href="#metadata">WS-Metadata Exchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_1466">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2_1_1461">MetadataExchange Assertion</a><br/>
 12 <a href="#Acknowledgements">Acknowledgements</a><br/>
 13 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;13.1 <a href="#iddiv2_1_1530">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;13.2 <a href="#iddiv2_1_1703">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;13.1 <a href="#iddiv2_1_1525">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;13.2 <a href="#iddiv2_1_1698">Informative 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/>
@@ -691,10 +691,6 @@
         When not present the default value is 
         "http://www.w3.org/2009/09/ws-mex/Content/Any".
        </p></dd></dl><p>
-     An endpoint MAY respond with a fault message using the standard 
-     fault codes defined in WS-Addressing 
-     <a href="#AddrCore">[WS-Addressing]</a> (e.g., wsa:ActionNotSupported).
-    </p><p>
      If an endpoint accepts a GetMetadata request, it MUST reply with 
      a GetMetadataResponse message. The normative outline for a 
      GetMetadataResponse is:
@@ -1000,7 +996,7 @@
     indicate a particular security mechanism used to protect the
     WS-MetadataExchange operations supported by this endpoint.
    </p><div class="div2">
-<h3><a name="iddiv2_1_1466" id="iddiv2_1_1466"/>11.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1461" id="iddiv2_1_1461"/>11.1 MetadataExchange Assertion</h3><p>
      The mechanism for indicating that a binding or endpoint conforms to the
      WS-MetadataExchange specification is through the use of the Web Services
      Policy - Framework <a href="#wspolicy">[WS-Policy]</a> and Web Services Policy -
@@ -1077,7 +1073,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>13 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1530" id="iddiv2_1_1530"/>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>
+<h3><a name="iddiv2_1_1525" id="iddiv2_1_1525"/>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.
@@ -1144,7 +1140,7 @@
        , P. Biron, A. Malhotra, Editors.
        World Wide Web Consortium (W3C), 28 October 2004.
       Available at <a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>.</dd></dl></div><div class="div2">
-<h3><a name="iddiv2_1_1703" id="iddiv2_1_1703"/>13.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
+<h3><a name="iddiv2_1_1698" id="iddiv2_1_1698"/>13.2 Informative References</h3><dl><dt class="label"><a name="WSSecureConversation" id="WSSecureConversation"/>WS-SecureConversation</dt><dd><a href="http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/os/ws-secureconversation-1.4-spec-os.doc"><cite>
         OASIS Standard, "Web Services Secure Conversation
           (WS-SecureConversation) 1.4"
        </cite></a>
@@ -1363,4 +1359,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8214">8214</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8124">8124</a></td></tr><tr><td> 2009/11/17 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8291">8291</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=8291">8291</a></td></tr><tr><td> 2009/12/01 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8203">8203</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Tuesday, 1 December 2009 22:23:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 1 December 2009 22:23:54 GMT