- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 07 Nov 2009 05:09:53 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv5365
Modified Files:
wseventing.html wseventing.xml
Log Message:
8167
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.118
retrieving revision 1.119
diff -u -d -r1.118 -r1.119
--- wseventing.xml 7 Nov 2009 05:08:05 -0000 1.118
+++ wseventing.xml 7 Nov 2009 05:09:51 -0000 1.119
@@ -330,12 +330,12 @@
</p>
<p>
- While lines (13-15) indicate where a reply SHOULD be sent,
- lines (20-29) indicate where and how notifications MUST be
+ While lines (13-15) indicate where a reply is sent,
+ lines (20-29) indicate where and how notifications are to be
delivered; there is no requirement that these match. The absence
of any extensions to the wse:Delivery or wse:NotifyTo elements
indicates that notifications
- MUST be sent as SOAP messages to the endpoint described in
+ are 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)
that identifies the subscription and will be included in each
@@ -4679,6 +4679,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8166">8166</loc>
</td>
</tr>
+ <tr>
+ <td> 2009/11/06 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8167">8167</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -d -r1.125 -r1.126
--- wseventing.html 7 Nov 2009 05:08:05 -0000 1.125
+++ wseventing.html 7 Nov 2009 05:09:51 -0000 1.126
@@ -250,12 +250,12 @@
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 MUST be
+ While lines (13-15) indicate where a reply is sent,
+ lines (20-29) indicate where and how notifications are to be
delivered; there is no requirement that these match. The absence
of any extensions to the wse:Delivery or wse:NotifyTo elements
indicates that notifications
- MUST be sent as SOAP messages to the endpoint described in
+ are 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)
that identifies the subscription and will be included in each
@@ -2632,4 +2632,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8170">8170</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8162">8162</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8163">8163</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8166">8166</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=8166">8166</a></td></tr><tr><td> 2009/11/06 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8167">8167</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Saturday, 7 November 2009 05:09:55 UTC