- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 28 Aug 2009 14:38:27 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6533 --- Comment #6 from Yves Lafon <ylafon@w3.org> 2009-08-28 14:38:27 --- proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0082.html << 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 >> -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 28 August 2009 14:51:55 UTC