On Oct 31, 2005, at 4:03 PM, Tim Bray wrote:
On Oct 31, 2005, at 2:03 PM, Luke Arno wrote:
* "Note: deleting a member also removes it from all the collections
to
which it belongs."
I don't think we ought to legislate this.
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". -Tim
It may be the same entry, but it might also be different resources.
For example, a blog system backed by JCR (JSR 170) content repository
would naturally have collections organized by date, category,
arbitrary query, and (most importantly) by version history. The
server will decide what collections are modified by the DELETE
of an entry based on how that collection is defined, with the
latter version history being the one that would violate such
a requirement in APP. Thus, it is over-specification.
In message-based protocols, you should define the sender's
intent and expectations for a given message, not how the
recipient shall change its own state as a result.
....Roy
