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

WWW/2002/ws/ra/edcopies wsmex.html,1.142,1.143 wsmex.xml,1.132,1.133

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 29 Nov 2010 18:29:00 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1PN8TE-0003mF-Q2@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv14431

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


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.132
retrieving revision 1.133
diff -u -d -r1.132 -r1.133
--- wsmex.xml	28 Nov 2010 15:54:18 -0000	1.132
+++ wsmex.xml	29 Nov 2010 18:28:58 -0000	1.133
@@ -3073,7 +3073,7 @@
   </div1>
 
   <div1 id="bootstrapping">
-   <head>Boostrapping Metadata Retrieval</head>
+   <head>Bootstrapping Metadata Retrieval</head>
 
    <p>
     Although the operations described in <specref ref="Retrieving-Metadata"/>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.142
retrieving revision 1.143
diff -u -d -r1.142 -r1.143
--- wsmex.html	28 Nov 2010 15:54:18 -0000	1.142
+++ wsmex.html	29 Nov 2010 18:28:58 -0000	1.143
@@ -76,7 +76,7 @@
 &nbsp;&nbsp;&nbsp;11.1 <a href="#iddiv2x1x2029">Metadata and Security Bootstrapping</a><br/>
 12 <a href="#metadata">WS-MetadataExchange Metadata</a><br/>
 &nbsp;&nbsp;&nbsp;12.1 <a href="#iddiv2x1x2050">MetadataExchange Assertion</a><br/>
-13 <a href="#bootstrapping">Boostrapping Metadata Retrieval</a><br/>
+13 <a href="#bootstrapping">Bootstrapping Metadata Retrieval</a><br/>
 14 <a href="#acks">Acknowledgements</a><br/>
 15 <a href="#References">References</a><br/>
 &nbsp;&nbsp;&nbsp;15.1 <a href="#iddiv2x1x2306">Normative References</a><br/>
@@ -1635,7 +1635,7 @@
      (i.e. the constructs defined by WS-SecurityPolicy), there is an obvious 
      dilemma when attempting to protect metadata in this way. Services 
      wishing to protect access to their metadata are advised to use the 
-     mechanisms described in <a href="#bootstrapping"><b>13 Boostrapping Metadata Retrieval</b></a> to advertise 
+     mechanisms described in <a href="#bootstrapping"><b>13 Bootstrapping Metadata Retrieval</b></a> to advertise 
      the security requirements for clients wishing to access metadata via 
      the mechanisms defined in this specification.
     </p></div></div><div class="div1">
@@ -1789,7 +1789,7 @@
          appears is scoped to the operations and features of the 
          WS-MetadataExchange specification.
         </p></dd></dl></div></div><div class="div1">
-<h2><a name="bootstrapping" id="bootstrapping"/>13 Boostrapping Metadata Retrieval</h2><p>
+<h2><a name="bootstrapping" id="bootstrapping"/>13 Bootstrapping Metadata Retrieval</h2><p>
     Although the operations described in <a href="#Retrieving-Metadata"><b>6 Retrieving Metadata about Service Endpoints</b></a>
     can be used by a requester to obtain the metadata about a particular 
     Service Endpoint, there is the 'chicken and egg' problem of how the 
Received on Monday, 29 November 2010 18:29:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 29 November 2010 18:29:03 GMT