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

WWW/2002/ws/ra/edcopies wseventing.html,1.59,1.60 wseventing.xml,1.51,1.52

From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 26 Jun 2009 13:37:20 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MKBcG-0007qu-0o@lionel-hutz.w3.org>
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv29864

Modified Files:
	wseventing.html wseventing.xml 
Log Message:
typos s/Line/line/g



Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- wseventing.xml	26 Jun 2009 13:25:30 -0000	1.51
+++ wseventing.xml	26 Jun 2009 13:37:17 -0000	1.52
@@ -339,20 +339,20 @@
 
     <p>
      Lines (07-09) in <specref ref="Table1"/> indicate the
-     message is a request to create a subscription, and Line (16)
+     message is a request to create a subscription, and line (16)
      indicates that it is sent to a hypothetical event source of ocean
      events.
     </p>
 
     <p>
-     While Lines (13-15) indicate where a reply should be sent,
-     Lines (20-29) indicate where and how notifications should be
+     While lines (13-15) indicate where a reply should be sent,
+     lines (20-29) indicate where and how notifications should be
      delivered; there is no requirement that these match. The absence
-     of a Mode attribute on Line (20) indicates that notifications
+     of a Mode attribute on line (20) indicates that notifications
      should be delivered using Push mode; that is, they should be
      asynchronously sent as SOAP messages to the endpoint described in
-     lines (21-28). Note that Lines (25-27) illustrate a typical
-     pattern where the event sink lists a reference parameter (Line 26)
+     lines (21-28). Note that lines (25-27) illustrate a typical
+     pattern where the event sink lists a reference parameter (line 26)
      that identifies the subscription and will be included in each
      notification.
     </p>
@@ -399,9 +399,9 @@
     <p>
      Lines (07-09) in <specref ref="Table2"/> indicate this
      message is a response to a request to create a subscription, and
-     Lines (10-12) indicate that it is a response to the request in
-     <specref ref="Table1"/>. Lines (17-26) provide the
-     subscription manager EPR for this subscription, and Line (27)
+     lines (10-12) indicate that it is a response to the request in
+     <specref ref="Table1"/>. lines (17-26) provide the
+     subscription manager EPR for this subscription, and line (27)
      indicates the subscription will expire in 30 hours unless
      renewed.
     </p>
@@ -1255,7 +1255,7 @@
     </example>
 
     <p>
-     Like the request in <specref ref="Table1"/>, Lines
+     Like the request in <specref ref="Table1"/>, lines
      (07-09) of <specref ref="Table4"/> indicate the message is
      a request to create a subscription. Line (19) indicates that it
      is sent to a hypothetical event source of ocean events.
@@ -1263,8 +1263,8 @@
 
     <p>
      Lines (13-18) indicate where to send the response to this
-     request, Lines (23-30) indicate where to send a SubscriptionEnd
-     message if necessary, and Lines (31-34) indicate how and where to
+     request, lines (23-30) indicate where to send a SubscriptionEnd
+     message if necessary, and lines (31-34) indicate how and where to
      send notifications.
     </p>
 
@@ -1322,19 +1322,19 @@
     </example>
 
     <p>
-     Like the response in <specref ref="Table2"/>, Lines
+     Like the response in <specref ref="Table2"/>, lines
      (08-10) of <specref ref="Table5"/> indicate this message is
-     a response to a request to create a subscription, and Lines
+     a response to a request to create a subscription, and lines
      (11-13) indicate that it is a response to the request in 
      <specref ref="Table4"/> . Lines (14-17) indicate the response is
-     sent to the event sink indicated in Lines (13-18) of 
+     sent to the event sink indicated in lines (13-18) of 
      <specref ref="Table4"/>. Lines (21-30) provide the address of the
      subscription manager for this subscription; note that this
      particular response uses the global wse:Identifier element
-     defined by this specification. Finally, Line (31) indicates the
+     defined by this specification. Finally, line (31) indicates the
      subscription will expire on 1 July 2004 unless renewed; there is
      no requirement that this time be necessarily longer or shorter
-     than the requested expiration (Line (41) of 
+     than the requested expiration (line (41) of 
      <specref ref="Table4"/>).
     </p>
    </div2>
@@ -1889,9 +1889,9 @@
     <p>
      Line (08) is the action URI for Subscription End. Lines
      (10-13) indicate the message is sent to the EndTo of the
-     subscribe request (Lines (23-30) in <specref ref="Table4"/>
+     subscribe request (lines (23-30) in <specref ref="Table4"/>
      .). Line (17) indicates the event source is shutting down, and
-     Lines (18-20) indicate that the event source was going off
+     lines (18-20) indicate that the event source was going off
      line.
     </p>
    </div2>
@@ -1963,9 +1963,9 @@
 
    <p>
     Lines (13-15) indicate the message is sent to the endpoint
-    indicated by the subscribe request (Lines (32-39) in
+    indicated by the subscribe request (lines (32-39) in
     <specref ref="Table4"/>). Line (17) matches the filter in the
-    subscribe request (Lines (42-45) in <specref ref="Table4"/>).
+    subscribe request (lines (42-45) in <specref ref="Table4"/>).
    </p>
   </div1>
 

Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -d -r1.59 -r1.60
--- wseventing.html	26 Jun 2009 13:25:30 -0000	1.59
+++ wseventing.html	26 Jun 2009 13:37:17 -0000	1.60
@@ -247,18 +247,18 @@
 (31)   &lt;/s12:Body&gt;
 (32) &lt;/s12:Envelope&gt;</pre></div></div><p>
      Lines (07-09) in <a href="#Table1">Example 2-1</a> indicate the
-     message is a request to create a subscription, and Line (16)
+     message is a request to create a subscription, and line (16)
      indicates that it is sent to a hypothetical event source of ocean
      events.
     </p><p>
-     While Lines (13-15) indicate where a reply should be sent,
-     Lines (20-29) indicate where and how notifications should be
+     While lines (13-15) indicate where a reply should be sent,
+     lines (20-29) indicate where and how notifications should be
      delivered; there is no requirement that these match. The absence
-     of a Mode attribute on Line (20) indicates that notifications
+     of a Mode attribute on line (20) indicates that notifications
      should be delivered using Push mode; that is, they should be
      asynchronously sent as SOAP messages to the endpoint described in
-     lines (21-28). Note that Lines (25-27) illustrate a typical
-     pattern where the event sink lists a reference parameter (Line 26)
+     lines (21-28). Note that lines (25-27) illustrate a typical
+     pattern where the event sink lists a reference parameter (line 26)
      that identifies the subscription and will be included in each
      notification.
     </p><p><a href="#Table2">Example 2-2</a> lists a hypothetical response to the request in
@@ -296,9 +296,9 @@
 (30) &lt;/s12:Envelope&gt;</pre></div></div><p>
      Lines (07-09) in <a href="#Table2">Example 2-2</a> indicate this
      message is a response to a request to create a subscription, and
-     Lines (10-12) indicate that it is a response to the request in
-     <a href="#Table1">Example 2-1</a>. Lines (17-26) provide the
-     subscription manager EPR for this subscription, and Line (27)
+     lines (10-12) indicate that it is a response to the request in
+     <a href="#Table1">Example 2-1</a>. lines (17-26) provide the
+     subscription manager EPR for this subscription, and line (27)
      indicates the subscription will expire in 30 hours unless
      renewed.
     </p></div></div><div class="div1">
@@ -728,14 +728,14 @@
 (45)     &lt;/wse:Subscribe&gt;
 (46)   &lt;/s12:Body&gt;
 (47) &lt;/s12:Envelope&gt;</pre></div></div><p>
-     Like the request in <a href="#Table1">Example 2-1</a>, Lines
+     Like the request in <a href="#Table1">Example 2-1</a>, lines
      (07-09) of <a href="#Table4">Example 4-1</a> indicate the message is
      a request to create a subscription. Line (19) indicates that it
      is sent to a hypothetical event source of ocean events.
     </p><p>
      Lines (13-18) indicate where to send the response to this
-     request, Lines (23-30) indicate where to send a SubscriptionEnd
-     message if necessary, and Lines (31-34) indicate how and where to
+     request, lines (23-30) indicate where to send a SubscriptionEnd
+     message if necessary, and lines (31-34) indicate how and where to
      send notifications.
     </p><p>
      Line (41) indicates the event sink would prefer to have the
@@ -780,19 +780,19 @@
 (32)     &lt;/wse:SubscribeResponse&gt;
 (33)   &lt;/s12:Body&gt;
 (34) &lt;/s12:Envelope&gt;</pre></div></div><p>
-     Like the response in <a href="#Table2">Example 2-2</a>, Lines
+     Like the response in <a href="#Table2">Example 2-2</a>, lines
      (08-10) of <a href="#Table5">Example 4-2</a> indicate this message is
-     a response to a request to create a subscription, and Lines
+     a response to a request to create a subscription, and lines
      (11-13) indicate that it is a response to the request in 
      <a href="#Table4">Example 4-1</a> . Lines (14-17) indicate the response is
-     sent to the event sink indicated in Lines (13-18) of 
+     sent to the event sink indicated in lines (13-18) of 
      <a href="#Table4">Example 4-1</a>. Lines (21-30) provide the address of the
      subscription manager for this subscription; note that this
      particular response uses the global wse:Identifier element
-     defined by this specification. Finally, Line (31) indicates the
+     defined by this specification. Finally, line (31) indicates the
      subscription will expire on 1 July 2004 unless renewed; there is
      no requirement that this time be necessarily longer or shorter
-     than the requested expiration (Line (41) of 
+     than the requested expiration (line (41) of 
      <a href="#Table4">Example 4-1</a>).
     </p></div><div class="div2">
 <h3><a name="Renew" id="Renew"/>4.2 Renew</h3><p>
@@ -1164,9 +1164,9 @@
 (23) &lt;/s12:Envelope&gt;</pre></div></div><p>
      Line (08) is the action URI for Subscription End. Lines
      (10-13) indicate the message is sent to the EndTo of the
-     subscribe request (Lines (23-30) in <a href="#Table4">Example 4-1</a>
+     subscribe request (lines (23-30) in <a href="#Table4">Example 4-1</a>
      .). Line (17) indicates the event source is shutting down, and
-     Lines (18-20) indicate that the event source was going off
+     lines (18-20) indicate that the event source was going off
      line.
     </p></div></div><div class="div1">
 <h2><a name="Notifications" id="Notifications"/>5 Notifications</h2><p>
@@ -1221,9 +1221,9 @@
 (34)   &lt;/s12:Body&gt;
 (35) &lt;/s12:Envelope&gt;</pre></div></div><p>
     Lines (13-15) indicate the message is sent to the endpoint
-    indicated by the subscribe request (Lines (32-39) in
+    indicated by the subscribe request (lines (32-39) in
     <a href="#Table4">Example 4-1</a>). Line (17) matches the filter in the
-    subscribe request (Lines (42-45) in <a href="#Table4">Example 4-1</a>).
+    subscribe request (lines (42-45) in <a href="#Table4">Example 4-1</a>).
    </p></div><div class="div1">
 <h2><a name="Faults" id="Faults"/>6 Faults</h2><p>
     All fault messages defined in this specification MUST be sent
Received on Friday, 26 June 2009 13:37:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 26 June 2009 13:37:30 GMT