WWW/2002/ws/ra/edcopies wsmex.html,1.70,1.71 wsmex.xml,1.60,1.61

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

Modified Files:
	wsmex.html wsmex.xml 
Log Message:
fix some bad refs - thanks katy


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- wsmex.xml	20 Oct 2009 23:59:21 -0000	1.60
+++ wsmex.xml	27 Oct 2009 17:25:18 -0000	1.61
@@ -760,7 +760,8 @@
 
    <p>
     When the representation of a resource is mex:Metadata, as defined 
-    in Section 4, or any other document format (e.g.
+    in <specref ref="web-services-metadata"/>, or any other document format 
+    (e.g.
     <bibref ref='XMLSchema1'/>,<bibref ref='XMLSchema2'/>, 
     <bibref ref='WSDL11'/>, 
     <bibref ref='wspolicy'/>) for which a mex:MetadataSection/@Dialect has 
@@ -1264,7 +1265,7 @@
       <def>
        <p>
         The body of the response message MUST contain one mex:Metadata 
-        element as defined in Section 4 of this specification.
+        element as defined in <specref ref="web-services-metadata"/>.
        </p>
       </def>
      </gitem>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -d -r1.70 -r1.71
--- wsmex.html	20 Oct 2009 23:59:21 -0000	1.70
+++ wsmex.html	27 Oct 2009 17:25:18 -0000	1.71
@@ -60,11 +60,11 @@
 8 <a href="#Bootstrapping-Metadata-Retrieval">Bootstrapping Metadata Retrieval</a><br/>
 9 <a href="#Security">Security Considerations</a><br/>
 10 <a href="#metadata">WS-Metadata Exchange Metadata</a><br/>
-&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2_1_1420">MetadataExchange Assertion</a><br/>
+&nbsp;&nbsp;&nbsp;10.1 <a href="#iddiv2_1_1426">MetadataExchange Assertion</a><br/>
 11 <a href="#Acknowledgements">Acknowledgements</a><br/>
 12 <a href="#References">References</a><br/>
-&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_1484">Normative References</a><br/>
-&nbsp;&nbsp;&nbsp;12.2 <a href="#iddiv2_1_1657">Informative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2_1_1490">Normative References</a><br/>
+&nbsp;&nbsp;&nbsp;12.2 <a href="#iddiv2_1_1663">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/>
@@ -467,7 +467,8 @@
     <a href="#WS-Transfer">[WS-Transfer]</a>.
    </p><p>
     When the representation of a resource is mex:Metadata, as defined 
-    in Section 4, or any other document format (e.g.
+    in <a href="#web-services-metadata"><b>5 Web Services Metadata</b></a>, or any other document format 
+    (e.g.
     <a href="#XMLSchema1">[XMLSchema - Part 1]</a>,<a href="#XMLSchema2">[XMLSchema - Part 2]</a>, 
     <a href="#WSDL11">[WSDL11]</a>, 
     <a href="#wspolicy">[WS-Policy]</a>) for which a mex:MetadataSection/@Dialect has 
@@ -705,7 +706,7 @@
      outline listed above:
     </p><dl><dt class="label"><b>[Body]</b>/mex:GetMetadataResponse/mex:Metadata </dt><dd><p>
         The body of the response message MUST contain one mex:Metadata 
-        element as defined in Section 4 of this specification.
+        element as defined in <a href="#web-services-metadata"><b>5 Web Services Metadata</b></a>.
        </p></dd></dl><p>
      This operation is safe; it will not result in any side effect
      imputable to the requester. This means that in case of an underlying
@@ -974,7 +975,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_1420" id="iddiv2_1_1420"/>10.1 MetadataExchange Assertion</h3><p>
+<h3><a name="iddiv2_1_1426" id="iddiv2_1_1426"/>10.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 -
@@ -1052,7 +1053,7 @@
       Yves Lafon (W3C).
    </p></div><div class="div1">
 <h2><a name="References" id="References"/>12 References</h2><div class="div2">
-<h3><a name="iddiv2_1_1484" id="iddiv2_1_1484"/>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>
+<h3><a name="iddiv2_1_1490" id="iddiv2_1_1490"/>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>
         Key words for use in RFCs to Indicate Requirement Levels
        </cite></a>
        , S. Bradner, Author.
@@ -1119,7 +1120,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_1657" id="iddiv2_1_1657"/>12.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_1663" id="iddiv2_1_1663"/>12.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>

Received on Tuesday, 27 October 2009 17:32:31 UTC