This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7774 - @mode in ws-frag is harmful
Summary: @mode in ws-frag is harmful
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Fragment (show other bugs)
Version: FPWD
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Yves Lafon
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-30 16:02 UTC by Yves Lafon
Modified: 2010-03-17 10:59 UTC (History)
1 user (show)

See Also:

Attachments

Description Yves Lafon 2009-09-30 16:02:16 UTC 
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).
Comment 4 Robert Freund 2010-01-26 22:39:19 UTC 
Resolved with comment #3