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

WWW/2002/ws/ra/edcopies wsenum.xml,1.87,1.88 wseventing.xml,1.131,1.132 wsmex.xml,1.79,1.80 wst.xml,1.86,1.87

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 01 Dec 2009 23:55:31 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1NFcZ9-0003Zn-SG@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv13659

Modified Files:
	wsenum.xml wseventing.xml wsmex.xml wst.xml 
Log Message:
8201


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -d -r1.86 -r1.87
--- wst.xml	17 Nov 2009 22:05:23 -0000	1.86
+++ wst.xml	1 Dec 2009 23:55:29 -0000	1.87
@@ -465,12 +465,6 @@
      by this specification.
     </p>
         
-    <p>
-     A compliant SOAP Node that implements a resource MUST
-     provide the Get operation as defined in this specification, and MAY provide
-     the Put and Delete operations.
-    </p>
-
    </div2>
   </div1>
 
@@ -479,8 +473,11 @@
 
       <div2 id="Get">
         <head>Get</head>
-        <p>This specification defines one Web service operation (Get) for fetching a
-one-time snapshot of the representation of a resource.</p>
+        <p>
+         This specification defines one Web service operation (Get) for 
+         fetching a one-time snapshot of the representation of a resource.
+         This operation MUST be supported by compliant WS-Transfer resources.
+        </p>
         <p>The Get request message MUST be of the following form:</p>
         <example>
           <eg><kw>[Action]</kw>
@@ -661,8 +658,9 @@
         <head>Put</head>
         <p>
          This specification defines one Web service operation (Put) for 
-         updating a resource by providing a replacement representation. A 
-         resource MAY accept updates that provide different XML 
+         updating a resource by providing a replacement representation. 
+         This operation MAY be supported by compliant WS-Transfer resources.
+         A resource MAY accept updates that provide different XML 
          representations than that returned by the resource; in such a 
          case, the semantics of the update operation is defined by
          the resource.
@@ -885,8 +883,11 @@
       </div2>
       <div2 id="Delete">
         <head>Delete</head>
-        <p>This specification defines one Web service operation (Delete) for deleting
-a resource in its entirety.</p>
+        <p>
+         This specification defines one Web service operation (Delete) for 
+         deleting a resource in its entirety.
+         This operation MAY be supported by compliant WS-Transfer resources.
+        </p>
         <p>The Delete request message MUST be of the following form:</p>
         <example>
           <eg><kw>[Action]</kw>
@@ -1036,8 +1037,12 @@
       <head>Resource Factory Operations</head>
       <div2 id="Factory_Create">
         <head>Create</head>
-        <p>This specification defines one Web service operation (Create) for creating
-    a resource and providing its initial representation. In some cases, the
+        <p>
+         This specification defines one Web service operation (Create) for 
+         creating a resource and providing its initial representation. 
+         This operation MAY be supported by compliant WS-Transfer resource
+         factories.
+         In some cases, the
     initial representation MAY constitute the representation of a logical
     constructor for the resource and can thus differ structurally from the
     representation returned by Get or the one required by Put. This is because
@@ -2484,6 +2489,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</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=8201">8201</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -d -r1.131 -r1.132
--- wseventing.xml	17 Nov 2009 22:05:22 -0000	1.131
+++ wseventing.xml	1 Dec 2009 23:55:29 -0000	1.132
@@ -819,7 +819,9 @@
 
     <p>
      To create a subscription, a subscriber sends a request message
-     of the following form to an event source:
+     to an event source.  This operation MUST be supported by
+     compliant event sources.
+     The message MUST be of the following form:
     </p>
 
     <example>
@@ -1375,13 +1377,11 @@
     <head>Renew</head>
 
     <p>
-     To update the expiration for a subscription, subscription
-     managers MUST support requests to renew subscriptions.
-    </p>
-
-    <p>
-     To renew a subscription, the subscriber sends a request of the
-     following form to the subscription manager:
+     To update, or renew, the expiration for a subscription, a
+     subscriber sends a Renew request message to the subscription
+     manager.
+     This operation MUST be supported by compliant subscription managers.
+     The Renew request message message MUST be of the following form:
     </p>
 
     <example>
@@ -1533,7 +1533,9 @@
 
     <p>
      To get the status of a subscription, the subscriber sends a
-     request of the following form to the subscription manager:
+     GetStatus request message to the subscription manager.
+     This operation MUST be supported by compliant subscription managers.
+     The GetStatus request MUST be of the following form:
     </p>
     
     <example>
@@ -1681,8 +1683,9 @@
 
     <p>
      To explicitly delete a subscription, a subscriber 
-     sends a request of the following form to the subscription
-     manager:
+     sends an Unsubscribe request message to the subscription manager.
+     This operation MUST be supported by compliant subscription managers.
+     The Unsubscribe request message MUST be of the following form:
     </p>
 
     <example>
@@ -1802,11 +1805,14 @@
 
     <p>
      If the event source terminates a subscription unexpectedly,
-     SubscriptionEnd SOAP message SHOULD be sent to
+     a SubscriptionEnd SOAP message SHOULD be sent to
      the endpoint reference indicated when the subscription was
      created (see <specref ref="Subscribe"/>). 
      This endpoint reference MUST refer to an endpoint that supports the 
-     SubscriptionEndPortType portType.
+     SubscriptionEndPortType portType.  Support for including the
+     EndTo EPR in a Subscribe request message
+     (and implicitly the sending of the SubscriptionEnd message)
+     MUST be supported by compliant event sources.
      The message MUST be of the following form:
     </p>
 
@@ -4674,6 +4680,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8285">8285</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=8201">8201</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -d -r1.79 -r1.80
--- wsmex.xml	1 Dec 2009 22:23:50 -0000	1.79
+++ wsmex.xml	1 Dec 2009 23:55:29 -0000	1.80
@@ -781,7 +781,7 @@
     resources. A Web service endpoint MAY also support direct retrieval 
     of metadata by requesters using a GetMetadata operation directed 
     to the Web service endpoint itself, as described in 
-    <specref ref="Get-Metadata"/>.
+    <specref ref="GetMetadata"/>.
    </p> 
 
    <p>
@@ -914,7 +914,7 @@
      </tr>
      <tr>
       <td> http://www.w3.org/&wsmex.nsprefix;/ws-mex/Dialects/ws-mex-all </td> 
-      <td> None.  [Defined in this specification for use in GetMetadata requests.  See <specref ref='Get-Metadata'/>.] </td> 
+      <td> None.  [Defined in this specification for use in GetMetadata requests.  See <specref ref='GetMetadata'/>.] </td> 
      </tr>
     </tbody>
    </table>
@@ -1085,14 +1085,14 @@
     </p>
    </div2>
    
-   <div2 id="Get-Metadata">
+   <div2 id="GetMetadata">
     <head>Get Metadata</head>
 
     <p>
      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 
+     This operation MAY be supported by compliant service endpoints.
+     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 
@@ -2511,6 +2511,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8203">8203</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=8201">8201</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- wsenum.xml	17 Nov 2009 21:00:39 -0000	1.87
+++ wsenum.xml	1 Dec 2009 23:55:29 -0000	1.88
@@ -630,7 +630,8 @@
     <head>Enumerate</head>
 
     <p>
-     Data sources MUST support the Enumerate operation to start an enumeration.
+     This specification defines the Enumerate operation to start an enumeration.
+     This operation MUST be supported by compliant data sources.
      A data source MAY provide other mechanisms for starting an enumeration and
      receiving an enumeration context.
     </p>
@@ -1053,9 +1054,10 @@
     <head>Pull</head>
 
     <p>
-     The Pull operation is initiated by sending a
-     Pull request message to the data source. The Pull request message
-     MUST be of the following form:
+     The Pull operation is initiated by sending a Pull request message to 
+     the data source. 
+     This operation MUST be supported by compliant data sources.
+     The Pull request message MUST be of the following form:
     </p>
 
     <example>
@@ -1362,13 +1364,10 @@
     <head>Renew</head>
 
     <p>
-     Data sources MUST support requests to renew
-     enumerations.
-    </p>
-
-    <p>
-     To renew an enumeration, the consumer sends a
-     request of the following form to the data source:
+     To update, or renew, the expiration for an enumeration, a Renew
+     request message is sent to the data source.
+     This operation MUST be supported by compliant data sources.
+     The Renew request message MUST be of the following form:
     </p>
 
     <example>
@@ -1468,8 +1467,9 @@
 
     <p>
      To get the status of an enumeration, the
-     consumer sends a request of the following form to the data
-     source:
+     consumer sends a GetStatus request message to the data source.
+     This operation MUST be supported by compliant data sources.
+     The message MUST be of the following form:
     </p>
 
     <example>
@@ -1528,8 +1528,9 @@
 
     <p>
      The Release operation is initiated by sending a
-     Release request message to the data source. The Release request
-     message MUST be of the following form:
+     Release request message to the data source. 
+     This operation MUST be supported by compliant data sources.
+     The Release request message MUST be of the following form:
     </p>
 
     <example>
@@ -1673,8 +1674,11 @@
      If the data source terminates an enumeration
      unexpectedly, the data source SHOULD send an EnumerationEnd SOAP
      message to the endpoint reference indicated when the enumeration
-     was created (see <specref ref="Enumerate"/>). The message MUST be of the
-     following form:
+     was created (see <specref ref="Enumerate"/>). 
+     Support for including the EndTo EPR in a Enumerate request message
+     (and implicitly the sending of the EnumerationEnd message) MUST
+     be supported by compliant data sources.
+     The message MUST be of the following form:
     </p>
 
     <example>
@@ -3493,6 +3497,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8280">8280</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=8201">8201</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Tuesday, 1 December 2009 23:55:33 GMT

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