On Wed, May 19, 2010 at 10:58 PM, Bob Wyman <[email protected]> wrote:.
> I would strongly encourage you to ensure that deleted-entry is symmetrical
> with atom:entry and that it is available in all contexts (i.e. both within
> and without a Feed Document) that an Atom entry is. Just as we can have
> Entry Documents, we should be able to have Deleted-entry Documents.
+1
I could well imagine wanting to return a Tombstone as the message body
for a 403 Gone response for a resource that I know has been deleted. I
guess I had been reading the following pretty liberally:
"""
The at:deleted-entry element MAY appear as a child of atom:feed to
represent an Atom Entry that has been removed from a feed.
deletedEntry = element at:deleted-entry {
atomCommonAttributes,
attribute ref { atomUri },
attribute when { atomDateConstruct },
( element at:by { atomPersonConstruct}?,
& element at:comment {atomTextConstruct}?,
& element atom:link*,
& element atom:source?,
& extensionElement* )
}
"""
Does the MAY prevent at:deleted-entry being used outside the context
of a atom:feed?
//Ed
[1] http://tools.ietf.org/html/rfc2616#section-10.4.11
