Teo Hui Ming wrote:
Hi James,
quoted from draft-snell-atompub-tombstones-04:
Linked "trash" resources are orthogonal to the at:deleted-entry
element and are intended to provide servers with a way of allowing
clients to recover deleted entries.
Is there a consensus on recovery mechanism that can (or should it?) be
included in tombstones extension?
Not currently. Recovery is going to mean different things to different
applications. For some, the entry will still be in the database and all
that is needed is essentially either a move operation or flipping a bit
from deleted to not-deleted. For others, the data will have been
removed from the datastore completely and the client needs to completely
recreate the entry. For now, I imagine that it would be best to leave
the recovery mechanism undefined and let applications get a bit more
experience with it before we start nailing down any kind of standard or
best practice procedure.
For instance, the entries in a feed may be managed by two
separate authors, one of whom may delete an entry that
the other author wishes to later recover. If a trash feed
is provided, the second author can look for a copy of the
deleted entry there.
In this example, does it imply that a trash feed should contain full
representation copy of entries, so that the second author can simply
retrieve the copy and POST it back to the original collection feed?
Quite possibly. I've left this intentionally vague. Suggestions welcome :-)
- James
