- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 07 Apr 2009 23:42:27 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv23626
Modified Files:
wseventing.html wseventing.xml
Log Message:
6725
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- wseventing.xml 7 Apr 2009 23:27:41 -0000 1.29
+++ wseventing.xml 7 Apr 2009 23:42:25 -0000 1.30
@@ -117,7 +117,7 @@
Web service (called a "subscriber") to register interest (called
a "subscription") with another Web service (called an "event
source") in receiving messages about events (called
- "notifications" or "event messages"). The subscriber may manage
+ "notifications"). The subscriber may manage
the subscription by interacting with a Web service (called the
"subscription manager") designated by the event source.
</p>
@@ -175,7 +175,7 @@
<item>
<p>
- Allow subscribers to specify how event messages should be delivered.
+ Allow subscribers to specify how notifications should be delivered.
</p>
</item>
@@ -217,14 +217,14 @@
<p>
While the general pattern of asynchronous, event-based
messages is extremely common, different applications often
- require different event message delivery mechanisms. For
+ require different notification delivery mechanisms. For
instance, in some cases a simple asynchronous message is optimal,
while other situations may work better if the event consumer can
- poll for event messages in order to control the flow and timing
- of message arrival. Some consumers will require event messages to
+ poll for notification in order to control the flow and timing
+ of message arrival. Some consumers will require notifications to
be wrapped in a standard "event" SOAP envelope, while others will
prefer messages to be delivered unwrapped. Some consumers may
- require event messages to be delivered reliably, while others may
+ require notifications to be delivered reliably, while others may
be willing to accept best-effort event delivery.
</p>
@@ -676,7 +676,7 @@
<label> Delivery Mode </label>
<def>
<p>
- The mechanism by which event messages are delivered from
+ The mechanism by which notifications are delivered from
the source to the sink.
</p>
</def>
@@ -714,7 +714,7 @@
<label> Push Mode </label>
<def>
<p>
- A delivery mechanism where the source sends event messages
+ A delivery mechanism where the source sends notifications
to the sink as unsolicited, asynchronous SOAP messages.
</p>
</def>
@@ -734,9 +734,8 @@
<label> Subscription Manager </label>
<def>
<p>
- A Web service that accepts requests to manage get the
- status of, renew, and/or delete subscriptions on behalf of an
- event source.
+ A Web service that accepts requests to create, get the status of,
+ renew, and/or delete subscriptions on behalf of an event source.
</p>
</def>
</gitem>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -d -r1.38 -r1.39
--- wseventing.html 7 Apr 2009 23:27:41 -0000 1.38
+++ wseventing.html 7 Apr 2009 23:42:25 -0000 1.39
@@ -101,7 +101,7 @@
Web service (called a "subscriber") to register interest (called
a "subscription") with another Web service (called an "event
source") in receiving messages about events (called
- "notifications" or "event messages"). The subscriber may manage
+ "notifications"). The subscriber may manage
the subscription by interacting with a Web service (called the
"subscription manager") designated by the event source.
</p><p>
@@ -131,7 +131,7 @@
Define how an event source delegates subscription
management to another Web service.
</p></li><li><p>
- Allow subscribers to specify how event messages should be delivered.
+ Allow subscribers to specify how notifications should be delivered.
</p></li><li><p>
Leverage other Web service specifications for secure,
reliable, transacted message delivery.
@@ -150,14 +150,14 @@
<h3><a name="DeliveryModes" id="DeliveryModes"/>2.2 Delivery Modes</h3><p>
While the general pattern of asynchronous, event-based
messages is extremely common, different applications often
- require different event message delivery mechanisms. For
+ require different notification delivery mechanisms. For
instance, in some cases a simple asynchronous message is optimal,
while other situations may work better if the event consumer can
- poll for event messages in order to control the flow and timing
- of message arrival. Some consumers will require event messages to
+ poll for notification in order to control the flow and timing
+ of message arrival. Some consumers will require notifications to
be wrapped in a standard "event" SOAP envelope, while others will
prefer messages to be delivered unwrapped. Some consumers may
- require event messages to be delivered reliably, while others may
+ require notifications to be delivered reliably, while others may
be willing to accept best-effort event delivery.
</p><p>
In order to support this broad variety of event delivery
@@ -394,7 +394,7 @@
</a>.
</p></div><div class="div2">
<h3><a name="terms" id="terms"/>3.4 Terminology</h3><dl><dt class="label"> Delivery Mode </dt><dd><p>
- The mechanism by which event messages are delivered from
+ The mechanism by which notifications are delivered from
the source to the sink.
</p></dd><dt class="label"> Event Source </dt><dd><p>
A Web service that sends notifications and accepts
@@ -404,15 +404,14 @@
</p></dd><dt class="label"> Notification </dt><dd><p>
A one-way message sent to indicate that an event has occurred.
</p></dd><dt class="label"> Push Mode </dt><dd><p>
- A delivery mechanism where the source sends event messages
+ A delivery mechanism where the source sends notifications
to the sink as unsolicited, asynchronous SOAP messages.
</p></dd><dt class="label"> Subscriber </dt><dd><p>
A Web service that sends requests to create, renew, and/or
delete subscriptions.
</p></dd><dt class="label"> Subscription Manager </dt><dd><p>
- A Web service that accepts requests to manage get the
- status of, renew, and/or delete subscriptions on behalf of an
- event source.
+ A Web service that accepts requests to create, get the status of,
+ renew, and/or delete subscriptions on behalf of an event source.
</p></dd></dl></div><div class="div2">
<h3><a name="compliance" id="compliance"/>3.5 Compliance</h3><p>
An implementation is not compliant with this specification if
Received on Tuesday, 7 April 2009 23:42:37 UTC