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

WWW/2002/ws/ra/edcopies wsmex.html,1.46,1.47 wsmex.xml,1.35,1.36

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 06 Aug 2009 17:51:46 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MZ77y-0000cJ-Fm@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv2280

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


Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -d -r1.35 -r1.36
--- wsmex.xml	6 Aug 2009 17:45:38 -0000	1.35
+++ wsmex.xml	6 Aug 2009 17:51:44 -0000	1.36
@@ -360,12 +360,12 @@
      mex:MetadataReference element in lines 72-76 of 
      <specref ref="GetResponse"/>,
      some endpoints may choose to support explicit request for metadata. 
-     <specref ref="GetMexReq"/> illustrates a sample Get Metadata request 
+     <specref ref="GetMexReq"/> illustrates a sample GetMetadata request 
      for the <bibref ref ='WS-Policy'/>.
     </p>
 
     <example id="GetMexReq">
-     <head>Sample Get Metadata request message</head>
+     <head>Sample GetMetadata request message</head>
 
      <eg>(01)  &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
@@ -404,7 +404,7 @@
     </p>
 
     <example id="GetMexRes">
-     <head>Sample Get Metadata response message</head>
+     <head>Sample GetMetadataResponse message</head>
 
      <eg>(01)   &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
@@ -438,13 +438,13 @@
 
     <p>
      Lines 8-10 in <specref ref="GetMexRes"/> indicate this message is a 
-     response to a Get Metadata request, and lines 11-13 indicate that it 
+     response to a GetMetadata request, and lines 11-13 indicate that it 
      is a response to the request in <specref ref="GetMexReq"/>. Lines 
      16-26 contain a single Metadata Section (lines 17-25); line 18 
      indicates that the metadata in this section is of type, or 
      dialect, WS-Policy while line 19 identifies a specific policy 
      document. Line 22 would have contained the policy expressions for the 
-     Web service endpoint to which the Get Metadata request of 
+     Web service endpoint to which the GetMetadata request of 
      <specref ref="GetMexReq"/> was directed.
     </p>
    </div2>
@@ -1052,18 +1052,16 @@
     <head>Get Metadata</head>
 
     <p>
-     When the metadata for an endpoint is not available or is unknown 
-     and there is no information on how to retrieve it (e.g. an endpoint 
-     reference to a <bibref ref='WS-Transfer'/> resource representing 
-     the metadata), a requester MAY send a Get Metadata request message 
-     to that endpoint to retrieve its metadata. A service endpoint MAY 
-     support the Get Metadata request. Observe that, in the case where 
+     A requester MAY send a GetMetadata request message to an endpoint to 
+     retrieve the metadata associated with that endpoint.
+     A service endpoint MAY 
+     support the GetMetadata request. Observe that, in the case where 
      a service endpoint is also a <bibref ref='WS-Transfer'/> resource, 
      the <bibref ref='WS-Transfer'/> Get operation allows requesters to 
      retrieve the resource representation associated with that endpoint 
      (i.e. the "data"), while the GetMetadata operation can be used to 
      retrieve that endpoint's metadata. The normative outline for a 
-     Get Metadata request is:
+     GetMetadata request is:
     </p>
 
     <example>
@@ -1203,9 +1201,9 @@
     </p>
 
     <p>
-     If an endpoint accepts a Get Metadata request, it MUST reply with 
-     a Get Metadata response message. The normative outline for a 
-     Get Metadata response is:
+     If an endpoint accepts a GetMetadata request, it MUST reply with 
+     a GetMetadataResponse message. The normative outline for a 
+     GetMetadataResponse is:
     </p>
 
     <example>
@@ -1760,7 +1758,7 @@
       namespace="http://www.w3.org/2005/08/addressing"
       schemaLocation="http://www.w3.org/2006/03/addressing/ws-addr.xsd"/>
 
-  &lt;!-- Get Metadata request -->
+  &lt;!-- GetMetadata request -->
   &lt;xs:element name='GetMetadata'>
     &lt;xs:complexType>
       &lt;xs:sequence>
@@ -1772,7 +1770,7 @@
     &lt;/xs:complexType>
   &lt;/xs:element>
 
-  &lt;!-- Get Metadata response -->
+  &lt;!-- GetMetadataResponse -->
   &lt;xs:element name='GetMetadataResponse'>
     &lt;xs:complexType>
       &lt;xs:sequence>
@@ -2038,6 +2036,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7194">7194</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/08/06 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679">6679</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- wsmex.html	6 Aug 2009 17:45:38 -0000	1.46
+++ wsmex.html	6 Aug 2009 17:51:44 -0000	1.47
@@ -261,10 +261,10 @@
      mex:MetadataReference element in lines 72-76 of 
      <a href="#GetResponse">Example 2-2</a>,
      some endpoints may choose to support explicit request for metadata. 
-     <a href="#GetMexReq">Example 2-3</a> illustrates a sample Get Metadata request 
+     <a href="#GetMexReq">Example 2-3</a> illustrates a sample GetMetadata request 
      for the <a href="#WS-Policy">[WS-Policy]</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-3: Sample Get Metadata request message</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
+<div class="exampleHeader"><a name="GetMexReq" id="GetMexReq"/>Example 2-3: Sample GetMetadata request message</div><div class="exampleInner"><pre>(01)  &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
 (03)      xmlns:wsa='http://www.w3.org/2005/08/addressing'
 (04)      xmlns:mex='http://www.w3.org/2009/02/ws-mex' &gt;
@@ -293,7 +293,7 @@
     </p><p><a href="#GetMexRes">Example 2-4</a> lists a sample response to the request in 
      <a href="#GetMexReq">Example 2-3</a>.
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="GetMexRes" id="GetMexRes"/>Example 2-4: Sample Get Metadata response message</div><div class="exampleInner"><pre>(01)   &lt;s11:Envelope
+<div class="exampleHeader"><a name="GetMexRes" id="GetMexRes"/>Example 2-4: Sample GetMetadataResponse message</div><div class="exampleInner"><pre>(01)   &lt;s11:Envelope
 (02)      xmlns:s11='http://schemas.xmlsoap.org/soap/envelope/'
 (03)      xmlns:wsa='http://www.w3.org/2005/08/addressing'
 (04)      xmlns:wsp='http://www.w3.org/ns/ws-policy'
@@ -322,13 +322,13 @@
 (27)    &lt;/s11:Body&gt;
 (28)  &lt;/s11:Envelope&gt;</pre></div></div><p>
      Lines 8-10 in <a href="#GetMexRes">Example 2-4</a> indicate this message is a 
-     response to a Get Metadata request, and lines 11-13 indicate that it 
+     response to a GetMetadata request, and lines 11-13 indicate that it 
      is a response to the request in <a href="#GetMexReq">Example 2-3</a>. Lines 
      16-26 contain a single Metadata Section (lines 17-25); line 18 
      indicates that the metadata in this section is of type, or 
      dialect, WS-Policy while line 19 identifies a specific policy 
      document. Line 22 would have contained the policy expressions for the 
-     Web service endpoint to which the Get Metadata request of 
+     Web service endpoint to which the GetMetadata request of 
      <a href="#GetMexReq">Example 2-3</a> was directed.
     </p></div></div><div class="div1">
 <h2><a name="Notation" id="Notation"/>3 Notation</h2><div class="div2">
@@ -597,18 +597,16 @@
      <a href="#WS-Policy">[WS-Policy]</a>) for which a dialect value is defined.
     </p></div><div class="div2">
 <h3><a name="Get-Metadata" id="Get-Metadata"/>6.2 Get Metadata</h3><p>
-     When the metadata for an endpoint is not available or is unknown 
-     and there is no information on how to retrieve it (e.g. an endpoint 
-     reference to a <a href="#WS-Transfer">[WS-Transfer]</a> resource representing 
-     the metadata), a requester MAY send a Get Metadata request message 
-     to that endpoint to retrieve its metadata. A service endpoint MAY 
-     support the Get Metadata request. Observe that, in the case where 
+     A requester MAY send a GetMetadata request message to an endpoint to 
+     retrieve the metadata associated with that endpoint.
+     A service endpoint MAY 
+     support the GetMetadata request. Observe that, in the case where 
      a service endpoint is also a <a href="#WS-Transfer">[WS-Transfer]</a> resource, 
      the <a href="#WS-Transfer">[WS-Transfer]</a> Get operation allows requesters to 
      retrieve the resource representation associated with that endpoint 
      (i.e. the "data"), while the GetMetadata operation can be used to 
      retrieve that endpoint's metadata. The normative outline for a 
-     Get Metadata request is:
+     GetMetadata request is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/02/ws-mex/GetMetadata
 
@@ -664,9 +662,9 @@
      fault codes defined in WS-Addressing 
      <a href="#AddrCore">[WS-Addressing]</a> (e.g., wsa:ActionNotSupported).
     </p><p>
-     If an endpoint accepts a Get Metadata request, it MUST reply with 
-     a Get Metadata response message. The normative outline for a 
-     Get Metadata response is:
+     If an endpoint accepts a GetMetadata request, it MUST reply with 
+     a GetMetadataResponse message. The normative outline for a 
+     GetMetadataResponse is:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
   http://www.w3.org/2009/02/ws-mex/GetMetadataResponse
 
@@ -1027,7 +1025,7 @@
       namespace="http://www.w3.org/2005/08/addressing"
       schemaLocation="http://www.w3.org/2006/03/addressing/ws-addr.xsd"/&gt;
 
-  &lt;!-- Get Metadata request --&gt;
+  &lt;!-- GetMetadata request --&gt;
   &lt;xs:element name='GetMetadata'&gt;
     &lt;xs:complexType&gt;
       &lt;xs:sequence&gt;
@@ -1039,7 +1037,7 @@
     &lt;/xs:complexType&gt;
   &lt;/xs:element&gt;
 
-  &lt;!-- Get Metadata response --&gt;
+  &lt;!-- GetMetadataResponse --&gt;
   &lt;xs:element name='GetMetadataResponse'&gt;
     &lt;xs:complexType&gt;
       &lt;xs:sequence&gt;
@@ -1152,4 +1150,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6500">6500</a></td></tr><tr><td> 2009/08/04 </td><td> DD </td><td> Added resolution of issues
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6719">6719</a>,
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6720">6720</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7194">7194</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=7194">7194</a></td></tr><tr><td> 2009/08/06 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6679">6679</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Thursday, 6 August 2009 17:51:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 6 August 2009 17:51:56 GMT