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

WWW/2002/ws/ra/edcopies wsenum.html,1.58,1.59 wsenum.xml,1.49,1.50 wseventing.html,1.81,1.82 wseventing.xml,1.72,1.73 wsmex.html,1.56,1.57 wsmex.xml,1.45,1.46 wst.html,1.57,1.58 wst.xml,1.53,1.54

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 02 Sep 2009 13:35:00 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MipzI-0000TU-76@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv1721

Modified Files:
	wsenum.html wsenum.xml wseventing.html wseventing.xml 
	wsmex.html wsmex.xml wst.html wst.xml 
Log Message:
6533


Index: wst.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.xml,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -d -r1.53 -r1.54
--- wst.xml	2 Sep 2009 11:36:57 -0000	1.53
+++ wst.xml	2 Sep 2009 13:34:58 -0000	1.54
@@ -569,6 +569,14 @@
          Other components of the outline above are not further constrained 
          by this specification.
         </p>
+
+        <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 
+         protocol error that might get unnoticed, resending the same request 
+         can be done automatically.
+        </p>
+
         <p>
          The following shows a sample SOAP envelope containing a Get 
          request:
@@ -2089,6 +2097,13 @@
             <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
           </td>
         </tr>
+        <tr>
+          <td> 2009/09/02 </td>
+          <td> DD </td>
+          <td> Added resolution of issue 
+            <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</loc>
+          </td>
+        </tr>
       </tbody>
      </table>
     </div1>

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -d -r1.81 -r1.82
--- wseventing.html	2 Sep 2009 12:51:39 -0000	1.81
+++ wseventing.html	2 Sep 2009 13:34:57 -0000	1.82
@@ -82,13 +82,13 @@
 </p>
 <h3><a name="appendices" id="appendices"/>Appendices</h3><p class="toc">A <a href="#Advertising">Advertising Event Information</a><br/>
 &nbsp;&nbsp;&nbsp;A.1 <a href="#ETypes">Event Types &amp; Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2461">Retrieving Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2475">Bindings for Event Descriptions</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2480">Binding for Unwrapped Notifications</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2498">Binding for Wrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.1 <a href="#iddiv3_1_2463">Retrieving Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2 <a href="#iddiv3_1_2477">Bindings for Event Descriptions</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.1 <a href="#iddiv4_1_2482">Binding for Unwrapped Notifications</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.1.2.2 <a href="#iddiv4_1_2500">Binding for Wrapped Notifications</a><br/>
 &nbsp;&nbsp;&nbsp;A.2 <a href="#NWSDL">Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2525">Retrieving Notification WSDLs</a><br/>
-&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2539">Multiple Event Information Metadata Sections</a><br/>
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A.2.1 <a href="#iddiv3_1_2527">Retrieving Notification WSDLs</a><br/>
+&nbsp;&nbsp;&nbsp;A.3 <a href="#iddiv2_1_2541">Multiple Event Information Metadata Sections</a><br/>
 B <a href="#Schema">XML Schema</a><br/>
 C <a href="#WSDL">WSDL</a><br/>
 D <a href="#wrappedWSDL">WSDL for Standard Wrapped Delivery</a><br/>
@@ -932,6 +932,11 @@
      a response to a renew request (see <a href="#Renew"><b>4.2 Renew</b></a>).
      Other components of the outline above are not further
      constrained by this specification.
+    </p><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
+     protocol error that might get unnoticed, resending the same request
+     can be done automatically.
     </p><p><a href="#Table8">Example 4-5</a> lists a hypothetical request to get the 
      status of the subscription created in <a href="#Table5">Example 4-2</a>.
     </p><div class="exampleOuter">
@@ -1684,7 +1689,7 @@
      serve as a description of the Event Type used in 
      <a href="#Table1">Example 2-1</a> and <a href="#EDExample">Example A-1</a>. 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2453" id="idexample_1_2453"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
+<div class="exampleHeader"><a name="idexample_1_2455" id="idexample_1_2455"/>Example A-2: EventDescriptions</div><div class="exampleInner"><pre>(01) &lt;wse:EventDescriptions 
 (02)        targetNamepace="http://www.example.org/oceanwatch/notifications"
 (03)        xmlns:wse="http://www.w3.org/2009/02/ws-evt"
 (04)        xmlns:ow="http://www.example.org/oceanwatch"&gt;
@@ -1704,7 +1709,7 @@
      GED for this Event Type is defined on line (08) as being of type 
      "{http://www.example.org/oceanwatch}:WindReportType". 
     </p><div class="div3">
-<h4><a name="iddiv3_1_2461" id="iddiv3_1_2461"/>A.1.1 Retrieving Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2463" id="iddiv3_1_2463"/>A.1.1 Retrieving Event Descriptions</h4><p>
       Although there are many ways in which an Event Source can make its 
       EventDescriptions available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1715,7 +1720,7 @@
       be equal to the value of its wse:EventDescriptions/@targetNamespace. An 
       Event Source MUST NOT have more than one EventDescriptions document.
      </p></div><div class="div3">
-<h4><a name="iddiv3_1_2475" id="iddiv3_1_2475"/>A.1.2 Bindings for Event Descriptions</h4><p>
+<h4><a name="iddiv3_1_2477" id="iddiv3_1_2477"/>A.1.2 Bindings for Event Descriptions</h4><p>
       For any Notification Format it SHOULD be possible to determine how a 
       given wse:eventType will appear on the wire as a Notification in a 
       Subscription created with that format. The following sections define 
@@ -1727,7 +1732,7 @@
       Format, implementations MAY provide a Notification WSDL (see below) 
       that explicitly describes the Notification operations. 
      </p><div class="div4">
-<h5><a name="iddiv4_1_2480" id="iddiv4_1_2480"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2482" id="iddiv4_1_2482"/>A.1.2.1 Binding for Unwrapped Notifications</h5><p>
        The information about an Event Type contained in the wse:eventType 
        element binds to a Unwrapped Notification for that type as follows:
       </p><ul><li><p>
@@ -1741,7 +1746,7 @@
          of the wse:eventType element corresponding to the type of the 
          Event being transmitted.
         </p></li></ul></div><div class="div4">
-<h5><a name="iddiv4_1_2498" id="iddiv4_1_2498"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
+<h5><a name="iddiv4_1_2500" id="iddiv4_1_2500"/>A.1.2.2 Binding for Wrapped Notifications</h5><p>
        The information about a Event Type contained in the eventType element 
        binds to a Wrapped Notification for that type as follows: 
       </p><ul><li><p>
@@ -1765,7 +1770,7 @@
      successful Subscribe request that used a particular Format URI. The 
      following is an example of a Notification WSDL: 
     </p><div class="exampleOuter">
-<div class="exampleHeader"><a name="idexample_1_2519" id="idexample_1_2519"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
+<div class="exampleHeader"><a name="idexample_1_2521" id="idexample_1_2521"/>Example A-3: Notification WSDL</div><div class="exampleInner"><pre>(01) &lt;wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
 (02)                   targetNamespace="http://www.example.org/oceanwatch/notifications"
 (03)                   xmlns:xs="http://www.w3.org/2001/XMLSchema"
 (04)                   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
@@ -1800,7 +1805,7 @@
 (33)     &lt;/wsdl:operation&gt;
 (34)   &lt;/wsdl:binding&gt;
 (35) &lt;/wsdl:definitions&gt;</pre></div></div><div class="div3">
-<h4><a name="iddiv3_1_2525" id="iddiv3_1_2525"/>A.2.1 Retrieving Notification WSDLs</h4><p>
+<h4><a name="iddiv3_1_2527" id="iddiv3_1_2527"/>A.2.1 Retrieving Notification WSDLs</h4><p>
       Although there are many ways in which an Event Source can make 
       Notification WSDLs available, this specification RECOMMENDS the use of 
       the mechanisms described in WS-MetadataExchange <a href="#MEX">[WS-MetadataExchange]</a>.
@@ -1816,7 +1821,7 @@
       Format URI/@Identifier, there MUST NOT exist more than one 
       Notification WSDL document. 
      </p></div></div><div class="div2">
-<h3><a name="iddiv2_1_2539" id="iddiv2_1_2539"/>A.3 Multiple Event Information Metadata Sections</h3><p>
+<h3><a name="iddiv2_1_2541" id="iddiv2_1_2541"/>A.3 Multiple Event Information Metadata Sections</h3><p>
      When WS-MetadataExchange is used to retrieve metadata about an Event 
      Source, recipients of mex:Metadata elements that contain Metadata 
      Sections with both the 
@@ -2314,4 +2319,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7160">7160</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6700">6700</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401">6401</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=6401">6401</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wst.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wst.html,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -d -r1.57 -r1.58
--- wst.html	2 Sep 2009 11:36:57 -0000	1.57
+++ wst.html	2 Sep 2009 13:34:58 -0000	1.58
@@ -285,6 +285,11 @@
          Other components of the outline above are not further constrained 
          by this specification.
         </p><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 
+         protocol error that might get unnoticed, resending the same request 
+         can be done automatically.
+        </p><p>
          The following shows a sample SOAP envelope containing a Get 
          request:
         </p><div class="exampleOuter"><div class="exampleInner"><pre>&lt;s:Envelope  
@@ -1170,4 +1175,5 @@
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
             <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6704">6704</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
-            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</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=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+            <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsmex.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -d -r1.45 -r1.46
--- wsmex.xml	2 Sep 2009 11:36:57 -0000	1.45
+++ wsmex.xml	2 Sep 2009 13:34:58 -0000	1.46
@@ -1251,6 +1251,14 @@
       </def>
      </gitem>
     </glist>
+
+    <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
+     protocol error that might get unnoticed, resending the same request
+     can be done automatically.
+    </p>
+
    </div2>
   </div1>
   
@@ -2122,6 +2130,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsenum.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.html,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -d -r1.58 -r1.59
--- wsenum.html	2 Sep 2009 11:36:56 -0000	1.58
+++ wsenum.html	2 Sep 2009 13:34:57 -0000	1.59
@@ -904,6 +904,11 @@
      constrained as for a response to a renew request 
      (see <a href="#Renew"><b>3.3 Renew</b></a>). Other components of the outline above are 
      not further constrained by this specification.
+    </p><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
+     protocol error that might get unnoticed, resending the same request
+     can be done automatically.
     </p></div><div class="div2">
 <h3><a name="Release" id="Release"/>3.5 Release</h3><p>
      The Release operation is initiated by sending a
@@ -1715,4 +1720,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7235">7235</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6427">6427</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6701">6701</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</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=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wsenum.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsenum.xml,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -d -r1.49 -r1.50
--- wsenum.xml	2 Sep 2009 11:36:57 -0000	1.49
+++ wsenum.xml	2 Sep 2009 13:34:57 -0000	1.50
@@ -1488,6 +1488,13 @@
      (see <specref ref="Renew"/>). Other components of the outline above are 
      not further constrained by this specification.
     </p>
+
+    <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
+     protocol error that might get unnoticed, resending the same request
+     can be done automatically.
+    </p>
    </div2>
 
    <div2 id="Release">
@@ -3043,6 +3050,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>

Index: wsmex.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wsmex.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -d -r1.56 -r1.57
--- wsmex.html	2 Sep 2009 11:36:57 -0000	1.56
+++ wsmex.html	2 Sep 2009 13:34:57 -0000	1.57
@@ -691,7 +691,12 @@
     </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.
-       </p></dd></dl></div></div><div class="div1">
+       </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
+     protocol error that might get unnoticed, resending the same request
+     can be done automatically.
+    </p></div></div><div class="div1">
 <h2><a name="Metadata-in-Endpoint-References" id="Metadata-in-Endpoint-References"/>7 Metadata in Endpoint References</h2><p><a href="#Retrieving-Metadata"><b>6 Retrieving Metadata</b></a> describes two mechanisms that 
     allow requesters to retrieve ("pull metadata") Web services metadata 
     from an endpoint (GetMetadata) or a metadata resource 
@@ -1180,4 +1185,5 @@
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7365">7365</a></td></tr><tr><td> 2009/08/25 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=7270">7270</a></td></tr><tr><td> 2009/09/01 </td><td> DD </td><td> Added resolution of issue 
        <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6702">6702</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
-       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6694">6694</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=6694">6694</a></td></tr><tr><td> 2009/09/02 </td><td> DD </td><td> Added resolution of issue 
+       <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file

Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -d -r1.72 -r1.73
--- wseventing.xml	2 Sep 2009 12:51:39 -0000	1.72
+++ wseventing.xml	2 Sep 2009 13:34:57 -0000	1.73
@@ -1519,6 +1519,13 @@
     </p>
 
     <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
+     protocol error that might get unnoticed, resending the same request
+     can be done automatically.
+    </p>
+
+    <p>
      <specref ref="Table8"/> lists a hypothetical request to get the 
      status of the subscription created in <specref ref="Table5"/>.
     </p>
@@ -4098,6 +4105,13 @@
        <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6401">6401</loc>
       </td>
      </tr>
+     <tr>
+      <td> 2009/09/02 </td>
+      <td> DD </td>
+      <td> Added resolution of issue 
+       <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533">6533</loc>
+      </td>
+     </tr>
     </tbody>
    </table>
   </div1>
Received on Wednesday, 2 September 2009 13:35:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 2 September 2009 13:35:09 GMT