lifestream: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
Jeremy Keith put lifestreaming on the map with his [http://adactio.com/extras/stream/ Lifestream demo application], which he blogged about [http://adactio.com/journal/1202/ here]. | Jeremy Keith put lifestreaming on the map with his [http://adactio.com/extras/stream/ Lifestream demo application], which he blogged about [http://adactio.com/journal/1202/ here]. | ||
The practice of syndicating and then aggregating content into one stream is a useful one as more and more | The practice of syndicating and then aggregating content into one stream is a useful one as more and more services crop up that allow us to do things that translate well into syndication formats. | ||
There are two questions intially to be resolved: | There are two questions intially to be resolved: | ||
Revision as of 00:49, 23 October 2007
Lifestream
Jeremy Keith put lifestreaming on the map with his Lifestream demo application, which he blogged about here.
The practice of syndicating and then aggregating content into one stream is a useful one as more and more services crop up that allow us to do things that translate well into syndication formats.
There are two questions intially to be resolved:
- how can chronological microformats at the distributed sources be best used to feed into lifestreams (i.e. via hAtom, hCalendar)?
- how should lifestreams themselves be best marked up (using a combination of hAtom and hCalendar or one or the other)?
In Jeremy's Real-World example (and subsequent derivatives) a combination has been used. Is this the best path forward? Are there other ideas, especially for semantically linking to the types of services that appear in one's stream?