ACTION-25: Determine format we can use for syndication and aggregation of event information

The two main options are:
* activity streams
* rss feeds

Most tools provide RSS feeds, only few provide activity streams. That’s not an issue for homegrown tools where we can easily produce one or the other; it might be more problematic for other tools.

For the consuming part, it sounds like wp-lifestream would be flexible enough to parse both or either of these http://www.enthropia.com/labs/wp-lifestream/

An open question would thus be:
* do we hack around wp-lifestream to associate sources with type of activities
* or do we try adding activity streams to the tools that haven't them yet via plugins?

After more thinking, since we want to be able to query the events for metrics, we will need to store it, and so we probably shouldn’t focus on formats that would directly consumed.

It would probably be better to store events in a database (whose schema would possibly follow the model developed for activity streams).

(IanJ and I have been discussion how extensible that model should be, but I think we should start with the most simple model, and only make it extensible once proven)

[dom]: results of our thinking at http://www.w3.org/community/council/wiki/ActivityTracking

[dom]: follow up write up in ACTION-53

[dom]: follow up write up in ACTION-56 (not 53)