Tim Bray wrote: > I think that if an entry shows up in multiple collections, it's still > the same entry, and the semantics of DELETE are "make this resource > go away", so I think that it would be very surprising if we changed > them to "remove from one collection".
The semantics of DELETE are that the resource at the request URI is removed, meaning it woudl return a 4xx status code after that. DELETE doesn't specify anything else. "Note: deleting a member also removes it from all the collections to which it belongs." In operational terms, what does this mean? Does it mean collections MUST NOT refer to linkreledits that are 404? I read that Joe says "Yes, that is currently unspecified and out of scope." Then why the heck is it in the draft? Robert Sayre
