diff --git a/feed.xml b/feed.xml index 64da543..ce3e2d7 100644 --- a/feed.xml +++ b/feed.xml @@ -2269,6 +2269,46 @@ return <type id="{$i}" name="{$type}" count="{$count}" />
So I can now say that I have walked onto a highway to write an XQuery script, while watching a cyclist pass by while shouting "The road is ours! The world belongs to us!" This is a very… interesting day.
]]> + +I particularly like the URL of this namespace.
+ +The specification includes various considerations on ensuring that the entry was indeed deleted by the feed's authors and not someone else, as well as supporting the aggregation of deleted entries from multiple feeds into one. It is also possible to have a separate XML file that only contains the <deleted-entry>
tag, which would have a MIME type of application/atomdeleted+xml
, with an extension of .atomdeleted
. Do check out the RFC if you want to learn more.
Of course, this is totally unreliable, since any reader that does not support this namespace will ignore it completely, and some potentially evil readers might even highlight the entry as needing to become another example of the Streisand effect. But in some applications, such as automated processing of Atom feeds for synchronizing some data, knowing for sure that something has been removed can be useful.
+I searched for code that was referencing this namespace and found that a few YouTube Atom feed parsers do handle deleted-entry
elements, so it might be possible that YouTube uses those tags. See here and here.
Nothing stops you from adding <at:deleted-entry>
elements to RSS feeds as well, just like how other Atom extensions can already be used there. But most feed readers will skip over this namespace in Atom feeds, so it is likely that almost nobody will support this on RSS feeds.
And if you were expecting actual tombstones from this namespace, well do know that RSS feeds for obituaries are a thing. You're welcome.
+ ]]>