{
"attachments": [],
"comments_archived": true,
"date": "2003-01-21T17:23:01.000Z",
"layout": "post",
"title": "RSS as a more generalized message queue for people",
"wordpress_id": 361,
"wordpress_slug": "ooocib",
"wordpress_url": "http://www.decafbad.com/blog/?p=361",
"year": "2003",
"month": "01",
"day": "21",
"isDir": false,
"slug": "ooocib",
"type": "entry",
"postName": "2003-01-21-ooocib",
"html": "It seems that beyond carrying syndication information, RSS is a very useful and flexible way to get all sorts of application data pushed to a user over time. In the same way that a web browser is a universal canvas upon which limitless services and information can be painted, so (in an albeit much smaller way) an RSS reader/aggregator might also find its place as an inbox for time-related delivery of all sorts of information.
\n\n\n\n\nMy thoughts exactly. Not sure if I've posted here about it, but I know during the whole RSS hubbub this fall, I'd babbled something about RSS being a messaging queue from machines to humans. Or a transport for timely ephemera to people. Or something like that. Basically, I'd like to see RSS, or something like it, used beyond just headlines. This is why I've leaned toward the RDF-in-RSS camp - I want to see lots of things besides titles and excerpts hung off the individual message events, and RDF seems downright nifty to me for this.
\nBut either way, I like the expanded notion of RSS usage as a timestream-oriented stream of messages targeted at subscribed people.
\n\n\n\n\n\nshortname=ooocib
\n\n\n\n",
"body": "It seems that beyond carrying syndication information, RSS is a very useful and flexible way to get all sorts of application data pushed to a user over time. In the same way that a web browser is a universal canvas upon which limitless services and information can be painted, so (in an albeit much smaller way) an RSS reader/aggregator might also find its place as an inbox for time-related delivery of all sorts of information.
\r\nMy thoughts exactly. Not sure if I've posted here about it, but I know during the whole RSS hubbub this fall, I'd babbled something about RSS being a messaging queue from machines to humans. Or a transport for timely ephemera to people. Or something like that. Basically, I'd like to see RSS, or something like it, used beyond just headlines. This is why I've leaned toward the RDF-in-RSS camp - I want to see lots of things besides titles and excerpts hung off the individual message events, and RDF seems downright nifty to me for this.
\r\nBut either way, I like the expanded notion of RSS usage as a timestream-oriented stream of messages targeted at subscribed people.
\r\n\r\nshortname=ooocib\r\n\r\n\r\n ",
"parentPath": "./content/posts/archives/2003",
"path": "2003/01/21/ooocib",
"summary": "It seems that beyond carrying syndication information, RSS is a very useful and flexible way to get all sorts of application data pushed to a user over time. In the same way that a web browser is a universal canvas upon which limitless services and information can be painted, so (in an albeit much smaller way) an RSS reader/aggregator might also find its place as an inbox for time-related delivery of all sorts of information. \n\nSource:DJ's Weblog: The universal canvas and RSS apps .\n\n\n\n\nMy thoughts exactly. Not sure if I've posted here about it, but I know during the whole RSS hubbub this fall, I'd babbled something about RSS being a messaging queue from machines to humans. Or a transport for timely ephemera to people. Or something like that. Basically, I'd like to see RSS, or something like it, used beyond just headlines. This is why I've leaned toward the RDF-in-RSS camp - I want to see lots of things besides titles and excerpts hung off the individual message events, and RDF seems downright nifty to me for this.\nBut either way, I like the expanded notion of RSS usage as a timestream-oriented stream of messages targeted at subscribed people.",
"needsBuild": true,
"prevPostPath": "2003/01/21/ooocia",
"prevPostTitle": "You had 1200 baud? Sheer luxury!",
"nextPostPath": "2003/01/21/ooocic",
"nextPostTitle": "Why Moblog?"
} ![](\"http://www.gravatar.com/avatar.php?gravatar_id=aaa4b3548d4f3ed959cdf1828fa683f2&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Breyten\r\n Rss 2.0 modules are also down right for including information besides description and title.\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=2ac2cffd36ada8c734b90e02a1e5c1ac&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n l.m.orchard\r\n I really need to circle back to look at RSS 2.0 sometime soon. I remember thinking that it looked like a nice compromise on flexibility, albeit with still a few kinks to work out.\r\n\r\nSo far, though, I'm still liking my stay in RDF-land, because once the \"tax\" is paid, all the data just falls nicely into the same pool and the same format. Whereas, although the non-RDF formats are simpler, they're not as useful to me.\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=8d03ba772dd6517c99a46eac05c71f53&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n Ehud\r\n I agree. \r\nFor example, aggregators should be able to show calendars widgets, and syndicate date-based information. One use-case is an RSS feed for a department seminar.\r\n\r\nDoing something like this isn't hard, and there are RDF to Outlook convertors etc. \r\nI wish it would be more widespread.\r\n \r\n \r\n \r\n ![](\"http://www.gravatar.com/avatar.php?gravatar_id=5a70d939a73fa73603f2a9255ab81d21&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\"/)
\r\n BillSeitz\r\n I had similar thoughts. I seems like a pretty logical single format for reading...\r\n\r\nhttp://webseitz.fluxent.com/wiki/UniversalInbox\r\n \r\n \r\n \r\n
Archived Comments
\n\n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=aaa4b3548d4f3ed959cdf1828fa683f2&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nBreyten\n \n\n\n \n\n\nRss 2.0 modules are also down right for including information besides description and title. \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=2ac2cffd36ada8c734b90e02a1e5c1ac&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nl.m.orchard\n \n\n\n \n\n\nI really need to circle back to look at RSS 2.0 sometime soon. I remember thinking that it looked like a nice compromise on flexibility, albeit with still a few kinks to work out.\nSo far, though, I'm still liking my stay in RDF-land, because once the \"tax\" is paid, all the data just falls nicely into the same pool and the same format. Whereas, although the non-RDF formats are simpler, they're not as useful to me. \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=8d03ba772dd6517c99a46eac05c71f53&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nEhud\n \n\n\n \n\n\nI agree. \nFor example, aggregators should be able to show calendars widgets, and syndicate date-based information. One use-case is an RSS feed for a department seminar.\nDoing something like this isn't hard, and there are RDF to Outlook convertors etc. \nI wish it would be more widespread. \n\n\n \n- \n
\n\n![](\"http://www.gravatar.com/avatar.php?gravatar_id=5a70d939a73fa73603f2a9255ab81d21&size=32&default=http://mediacdn.disqus.com/1320279820/images/noavatar32.png\")
\nBillSeitz\n \n\n\n \n\n\nI had similar thoughts. I seems like a pretty logical single format for reading...\nhttp://webseitz.fluxent.com/wiki/UniversalInbox \n\n\n \n
\n\n\n\n
\n
\n
\n