James M Snell wrote:
Reviving the Tombstones draft. Consider this a work in progress.
Out of curiostiy, are there any server developers here that are planning (or even just considering) adding tombstone support for something like comment-spam or erasing erroneous posts from a blog? Basically any use-case that might benefit a typical feed reader?
Also, for the record, I should express again my preference for using attributes rather than elements for at least the primary fields. If you need justification:
1. It's a more compact representation, which helps counter the arguments of people that think tombstones shouldn't be clogging up a regular feed or should require clients to issue special headers requesting them. 2. It requires less state information to parse (other client developers may disagree, but this makes a significant difference to me). 3. I suspect people are a lot more likely to get your field names wrong when using elements rather than attributes (using "author" instead of "by", "updated" instead of "when"), especially now that you're proposing putting this in the Atom namespace.
Then again, if nobody here is planning to use this in a way that would be relevant to me, it doesn't really matter what form it takes.
Regards James
