Action 89, Issue-6533 Include all safe operations in all specs

• From: Yves Lafon <ylafon@w3.org>
• Date: Fri, 28 Aug 2009 10:16:01 -0400 (EDT)
• To: public-ws-resource-access@w3.org
• Message-ID: <alpine.DEB.1.10.0908281015030.13615@wnl.j3.bet>

The text in WS-T should stay the same (see [1])

However, each operation should state explicitely that it is safe or not, 
so for wst:Get
[
This operation is safe [ref Safeness of Operations].
] (a)
[
This operation is NOT safe [ref wst:Safeness of Operations].
] (b)

* in RT, no new operations are definet (just wst:Get extended but with no 
semantic change).

* in MEX

After the first paragraph of 'GetMetadata', add (a)

* in Eventing

After the first example in 'Subscribe', add (b)
After the first sentence in 'Renew', add (b)
After the first example in 'GetStatus', add (a)
After the first sentence in 'Unsubscribe', add (b)

* in Enumeration

After the first paragraph in 'Enumerate', add (b)
After the first example in 'Pull', add (b)
After the first sentence in 'Renew', add (b)
After the first example in 'GetStatus', add (a)
After the first example in 'Release', add (b)


[1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0040.html

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves

Received on Friday, 28 August 2009 14:16:13 UTC