[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Updated Tombstones Draft
James M Snell wrote:
Bill de hOra wrote:
James M Snell wrote:
1. deleted-entry is now part of the Atom namespace
"The Atom namespace is reserved for future forward-compatible revisions
of Atom." RFC4287, 6.2.
The rfc-editor should have picked this up.
Picked what up? The rfc-editor is not involved in the publishing of
I-D's. If this I-D is published as a Standards Track RFC, it would
specifically indicate that it is an update to RFC 4287 and would qualify
as a "forward-compatible revision of Atom". I believe that it's up to
the Area Director to determine whether or not to allow individual
submissions such as this to proceed along that route or whether a WG is
You seem to be assuming this won't get implemented before it gets to
standards track. Until that time, I suggest you revert the namespace. Or
make it clear that you intend to use this to create a forward compatible
revision of Atom.
2. a "trash" link relation is registered to point
to trash feeds.
Aside from what we talked about recently, the document only talks about
deletion in the past tense; there's no deletion mechanism specified.
There's no need to specify a deletion mechanism. A deleted-entry
element indicates that an entry has been removed from the feed and the
trash link relation points to a resource listing the entries that have
been removed. The mechanism used to remove those items is orthogonal to
Without a mechanism (for delete, sync, undelete, etc), how are we
supposed to know whether this metadata is useful or well-designed
outside whatever private application originally needed it? Or how it
interacts with Atompub operations, or some other protocol? Or what
happens when there are multiple trash feeds? Or further extended
metadata? Or where 95% of comments are spam? Or how it interacts with
DELETE/POST? Or whether it can be used for dead letter queuing?
In other posts you've suggested you need something just like this, so
let me suggest if you have a mechanism or a technical reason, at least
document it as an example.