how to know that something was DELETEd

hello all.

as you might have seen in the conversation with graham klyne, we have a
potentially interesting use case for us. it's nicely in line with most
things we're doing, but might give us a good opportunity to validate the
design against a real-world example. most importantly, they need something
(if i did understand it correctly) that is feedy, but uses RDF. that's us,
to some extent, but also a bit different because it may draw us in the
direction of a more feedy design, with defined metadata properties (such
as updated timestamps), and support to easily expose interactions with LDP
resources (create/update/delete interactions) in the LDP container. if we
have richard's sorting, then at least we can order by timestamp and expose
members in a "last-updated-first" way. however, this still does not solve
the problem of how to represent DELETE interactions. it took a long time
for feedland to get to this part of the picture
(http://tools.ietf.org/html/rfc6721 is just half a year old), but it's
actually essential for any kind of "sync" scenario where a consumer of a
container wants to use it as a way for how to keep its local state
synchronized.

so my question is: should we add this to uses cases? i could check back
with graham and make sure i got it right the second time, and then write
down the scenario. we could also mark it as "optional" or "advanced". but
it might be nice to keep it around, also so that we can start coordinating
efforts across w3c groups.

cheers,

dret.

Received on Wednesday, 27 March 2013 17:42:18 UTC