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

WWW/2002/ws/ra/edcopies wseventing.html,1.100,1.101 wseventing.xml,1.92,1.93

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Tue, 13 Oct 2009 17:43:14 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MxlP0-0001lu-E1@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv6744

Modified Files:
	wseventing.html wseventing.xml 
Log Message:
s/subscribing event sink/subscriber/g
Thanks to the oasis wsdd wg!



Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -d -r1.92 -r1.93
--- wseventing.xml	6 Oct 2009 16:42:03 -0000	1.92
+++ wseventing.xml	13 Oct 2009 17:43:12 -0000	1.93
@@ -1663,13 +1663,13 @@
 
     <p>
      Though subscriptions expire eventually, to minimize resources,
-     the subscribing event sink SHOULD explicitly delete a
+     the subscriber SHOULD explicitly delete a
      subscription when it no longer wants notifications associated
      with the subscription.
     </p>
 
     <p>
-     To explicitly delete a subscription, a subscribing event sink
+     To explicitly delete a subscription, a subscriber 
      sends a request of the following form to the subscription
      manager:
     </p>
@@ -1941,7 +1941,7 @@
    </p>
 
    <p>
-    However, if a subscribing event sink wishes to have
+    However, if a subscriber wishes to have
     notifications specifically marked, it MAY specify literal SOAP
     header blocks in the Subscribe request, in the
     /s:Envelope/s:Body/wse:Subscribe/wse:Delivery/wse:NotifyTo/wsa:ReferenceParameters

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -d -r1.100 -r1.101
--- wseventing.html	6 Oct 2009 16:42:03 -0000	1.100
+++ wseventing.html	13 Oct 2009 17:43:12 -0000	1.101
@@ -1022,11 +1022,11 @@
     </p></div><div class="div2">
 <h3><a name="Unsubscribe" id="Unsubscribe"/>4.4 Unsubscribe</h3><p>
      Though subscriptions expire eventually, to minimize resources,
-     the subscribing event sink SHOULD explicitly delete a
+     the subscriber SHOULD explicitly delete a
      subscription when it no longer wants notifications associated
      with the subscription.
     </p><p>
-     To explicitly delete a subscription, a subscribing event sink
+     To explicitly delete a subscription, a subscriber 
      sends a request of the following form to the subscription
      manager:
     </p><div class="exampleOuter"><div class="exampleInner"><pre><b>[Action]</b>
@@ -1201,7 +1201,7 @@
     This specification does not constrain notifications because
     any message MAY be a notification.
    </p><p>
-    However, if a subscribing event sink wishes to have
+    However, if a subscriber wishes to have
     notifications specifically marked, it MAY specify literal SOAP
     header blocks in the Subscribe request, in the
     /s:Envelope/s:Body/wse:Subscribe/wse:Delivery/wse:NotifyTo/wsa:ReferenceParameters
Received on Tuesday, 13 October 2009 17:43:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 13 October 2009 17:43:16 GMT