7774 2009-09-30 16:02:16 +0000 @mode in ws-frag is harmful 2010-03-17 10:59:09 +0000 1 1 1 Unclassified WS-Resource Access Fragment FPWD PC All CLOSED REMIND P2 normal --- 1 ylafon ylafon dug public-ws-resource-access-notifications oldest_to_newest 27949 0 ylafon 2009-09-30 16:02:16 +0000 I have a question about the introduction of 'mode' in fragment PUT mode has three different values: http://www.w3.org/2009/02/ws-fra/Modes/Replace http://www.w3.org/2009/02/ws-fra/Modes/Insert and http://www.w3.org/2009/02/ws-fra/Modes/Remove Put+Remove sounds awfully like a Delete, and Put+Insert looks also awfully like a Create. (and Put+Replace looks like... a Put) So why adding another axis of extensibility to duplicate what's already there? (see discussion at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/thread.html#msg88 ) Proposal: Get rid of '@mode' and use Create(Frag) Delete(Frag), like it's done for Put(Frag). 31149 1 dug 2010-01-20 13:01:06 +0000 Proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/0100.html 31170 2 dug 2010-01-22 14:59:51 +0000 Proposal: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/att-0112/wst-7774.html 31181 3 dug 2010-01-23 03:37:05 +0000 http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/att-0123/wst-7774.html 31253 4 bob 2010-01-26 22:39:19 +0000 Resolved with comment #3