Delete activities are important if the feed data are used to aggreate activities from various web venues/site.
MySpace has implemented "Tombstone'ing" when a user takes a delete action as described at: http://wiki.developer.myspace.com/index.php?title=ActivityStream_Queries#FeedSync
Use Case 1: Search
- All social activities of one or more web venues (create, modify, delete, tag, rate, view etc.) are provided as activity streams
- The Enterprise Search engine reads the feed and update the search index (in real time).
- If an information object is deleted from the web venue, the search enginge can remove the information object from the search collection
Real Live Example : Sun's SunSpace Enterprise search
Use Case 2: Social activity aggregation and evaluation
- All social activities of one or more web venues (create, modify, delete, tag, rate, view etc.) are provided as activity streams
- A Social service reads the feed and calculates a social value for a social activity
- Based on the sum of the social values for an information, person or group, the social service provides ranking and statistical information.
- A set of widgets are used to display the valued data
- If an information,person or group gets deleted from a web venue it gets removed from the social services
(Example: An blog post is ranked in the top 10 blog post widget. The author removes the blog post. The blog post gets removed from the ranking widget)

Real Live Example : SunSpace and Community Equity
Example: Delete a notice
<entry>
<title>Notice deleted</title>
<id>tag:mb.sunsolutioncenter.de,2009-10-10:/1/notice/51/196</id>
<link rel="alternate" href="http://mb.sunsolutioncenter.de/index.php/notice/51"/>
<published>2009-12-08T22:14:43+00:00</published>
<updated>2009-12-08T22:14:43+00:00</updated>
<author>
<name>pr9510</name>
<uri>http://mb.sunsolutioncenter.de/index.php/pr9510</uri>
</author>
<activity:verb>http://example.org/schema/1.0/delete</activity:verb>
<content type="html">Notice deleted</content>
<activity:object>
<activity:object-type>http://activitystrea.ms/schema/1.0/note</activity:object-type>
<content>Notice deleted</content>
<published>2009-12-08T22:14:43+00:00</published>
<link rel="permalink" type="text/html" href="http://mb.sunsolutioncenter.de/index.php/notice/51"/>
</activity:object>
</entry>
Forum Reference: link
Comments (3)
Monica Keller said
at 10:20 am on Sep 5, 2009
Just to be clear the spec and activities in general should focus on representing positive actions. FeedSync is only necessary to keep in sync repositories of the same data
Peter Reiser said
at 8:41 am on Sep 7, 2009
Why focusing on positive actions only? There are clear use cases (e.g dynamic search index updates , aggregated social reputation system etc.) were we need to know if a content type, tag or user is deleted.
Monica Keller said
at 10:00 am on Sep 7, 2009
Because you don't see activities of the form "Monica is no longer friends with Dan". In fact syndicating pubicly deletes can draw more attention to these than intended. Look at the picture she deleted ! We dont want systems capitalizing misfortunes. This spec covers public syndication so that is why we chose not to focus on negative actions. Users woud hate it.
Having said that there are multiple use cases this spec does not cover but since its based on atom we can use atom extensions like feedsync to address.
You don't have permission to comment on this page.