Re: Conditional delete in LDP

> I think the DELETE would be only mainly important if in cases where 
> I would decide not to delete based on the state of the resource. 

which, if I paraphrase to "sometimes might want to", seems fairly 
different from the 'all write requests...DELETE' portion of your original

> shouldn't we move the conditional request phrases from PUT to the 
general section and make it apply to all write requests (at least PUT and 
DELETE) ? 

Thus, it sounds like we know what to do about "generic write" requests ... 
most often you'll be wise to make them conditional.
I'm not sure at this point if you've changed your mind about the Delete 
portion of your original proposal, if you're drifting in that direction 
via the discussion, or are standing behind your original.  Certainly one 
Could use conditional requests at any point; that's just a vacuous 
re-statement of HTTP, on its own.  I have yet to see any (>0) conditional 
delete requests in practice, despite their theoretical possibility, which 
makes me lean in the Delete case towards relying on readers' ability to 
recognize what's possible (even if not explicitly re-stated) based on the 
normative references.  ...at least in the normative spec.  I'm not sure if 
others' experiences are different, however, and that would be useful 
information if they do differ.


Best Regards, John

Voice US 845-435-9470  BluePages
Cloud and Smarter Infrastructure OSLC Lead