On Thu, 3 Jan 2008, James M Snell wrote:
Bill de hOra wrote:
[snip]
Please explain why the tombstone markup has been placed in the Atom
The reasons are simple:
1. This is a generic capability that is applicable to a broad range of
application cases. That is, it is not application or implementation
specific.
2. Implementors are already starting to face issues with supporting a
broad and growing number of extension namespaces.
I don't mean to kick a sleeping dog, but it seems like the ideal way to
keep delete capability (agreed that it's broadly applicable) in the Atom
namespace is for tombstones to be atom:entry and "marked-for-deletion" to
be an atom:category.
--peter keane
