- From: Doug Davis via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 10 Feb 2010 00:57:31 +0000
- To: public-ws-resource-access-notifications@w3.org
Update of /w3ccvs/WWW/2002/ws/ra/edcopies
In directory hutz:/tmp/cvs-serv25433
Modified Files:
wseventing.html wseventing.xml
Log Message:
8271
Index: wseventing.xml
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.xml,v
retrieving revision 1.154
retrieving revision 1.155
diff -u -d -r1.154 -r1.155
--- wseventing.xml 10 Feb 2010 00:48:11 -0000 1.154
+++ wseventing.xml 10 Feb 2010 00:57:29 -0000 1.155
@@ -259,7 +259,7 @@
be useful to delegate the management of a subscription to another
Web service. To support this flexibility, the response to a
subscription request to an event source will include the EPR of a
- service that the subscriber MAY interact with to manage this
+ service that the subscriber can interact with to manage this
subscription. This EPR MUST be the target for future requests
to renew or cancel the subscription. It can address the same Web
service (Address and ReferenceParameters) as the event source
@@ -2266,7 +2266,7 @@
<p>
This fault MUST be generated when a Subscribe request specifies a filter
- dialect that the event source does not support. OPTIONALLY, this
+ dialect that the event source does not support. This
fault MAY contain a list of supported filter dialect IRIs in the
Detail property.
</p>
@@ -2306,7 +2306,7 @@
<p>
This fault MUST be generated when a Subscribe request specifies a delivery
- format that is not supported by the event source. OPTIONALLY, this
+ format that is not supported by the event source. This
fault MAY contain a list of supported delivery format IRIs in the
Detail property.
</p>
@@ -2501,10 +2501,10 @@
</p>
<p>
- Different security mechanisms MAY be desired depending on the
+ Different security mechanisms might be desired depending on the
frequency of messages. For example, for infrequent messages,
- public key technologies MAY be adequate for integrity and
- confidentiality. However, for high-frequency events, it MAY be
+ public key technologies might be adequate for integrity and
+ confidentiality. However, for high-frequency events, it could be
more performant to establish a security context for the events
using the mechanisms described in WS-Trust
<bibref ref="WSTrust"/> and WS-SecureConversation
@@ -4893,6 +4893,13 @@
<loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</loc>
</td>
</tr>
+ <tr>
+ <td> 2010/02/09 </td>
+ <td> DD </td>
+ <td> Added resolution of issue
+ <loc href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271">8271</loc>
+ </td>
+ </tr>
</tbody>
</table>
</div1>
Index: wseventing.html
===================================================================
RCS file: /w3ccvs/WWW/2002/ws/ra/edcopies/wseventing.html,v
retrieving revision 1.161
retrieving revision 1.162
diff -u -d -r1.161 -r1.162
--- wseventing.html 10 Feb 2010 00:47:43 -0000 1.161
+++ wseventing.html 10 Feb 2010 00:57:29 -0000 1.162
@@ -196,7 +196,7 @@
be useful to delegate the management of a subscription to another
Web service. To support this flexibility, the response to a
subscription request to an event source will include the EPR of a
- service that the subscriber MAY interact with to manage this
+ service that the subscriber can interact with to manage this
subscription. This EPR MUST be the target for future requests
to renew or cancel the subscription. It can address the same Web
service (Address and ReferenceParameters) as the event source
@@ -1351,7 +1351,7 @@
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringNotSupported</td></tr><tr><td><b>[Reason]</b></td><td>Filtering is not supported.</td></tr><tr><td><b>[Detail]</b></td><td><em>none</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="FilteringRequestedUnavailable" id="FilteringRequestedUnavailable"/>6.6 FilteringRequestedUnavailable</h3><p>
This fault MUST be generated when a Subscribe request specifies a filter
- dialect that the event source does not support. OPTIONALLY, this
+ dialect that the event source does not support. This
fault MAY contain a list of supported filter dialect IRIs in the
Detail property.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:FilteringRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested filter dialect is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
@@ -1360,7 +1360,7 @@
receiver</em></td></tr></tbody></table></div><div class="div2">
<h3><a name="DeliveryFormatRequestedUnavailable" id="DeliveryFormatRequestedUnavailable"/>6.7 DeliveryFormatRequestUnavailable</h3><p>
This fault MUST be generated when a Subscribe request specifies a delivery
- format that is not supported by the event source. OPTIONALLY, this
+ format that is not supported by the event source. This
fault MAY contain a list of supported delivery format IRIs in the
Detail property.
</p><table border="1"><tbody><tr><td><b>[Code]</b></td><td>s12:Sender</td></tr><tr><td><b>[Subcode]</b></td><td>wse:DeliveryFormatRequestedUnavailable</td></tr><tr><td><b>[Reason]</b></td><td>The requested delivery format is not supported.</td></tr><tr><td><b>[Detail]</b></td><td>
@@ -1398,10 +1398,10 @@
bodies, the <code><s12:Body></code> element SHOULD be
signed so content cannot be added in transit.
</p><p>
- Different security mechanisms MAY be desired depending on the
+ Different security mechanisms might be desired depending on the
frequency of messages. For example, for infrequent messages,
- public key technologies MAY be adequate for integrity and
- confidentiality. However, for high-frequency events, it MAY be
+ public key technologies might be adequate for integrity and
+ confidentiality. However, for high-frequency events, it could be
more performant to establish a security context for the events
using the mechanisms described in WS-Trust
<a href="#WSTrust">[WS-Trust]</a> and WS-SecureConversation
@@ -2633,4 +2633,5 @@
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8196">8196</a></td></tr><tr><td> 2010/02/05 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=6435">6435</a></td></tr><tr><td> 2010/02/08 </td><td> DD </td><td> Added resolution of issue
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8901">8901</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
- <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160">8160</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=8160">8160</a></td></tr><tr><td> 2010/02/09 </td><td> DD </td><td> Added resolution of issue
+ <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=8271">8271</a></td></tr></tbody></table></div></div></body></html>
\ No newline at end of file
Received on Wednesday, 10 February 2010 00:57:33 UTC