Comments on: Enterprise RSS? http://distributedresearch.net/blog/2007/12/12/enterprise-rss Distributed Action Research, communities of practice and social objects by Andy Roberts Fri, 21 Nov 2008 21:11:07 +0000 http://wordpress.org/?v=2.2 By: Andy Roberts http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-11944 Andy Roberts Tue, 01 Jan 2008 13:36:33 +0000 http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-11944 Thanks for all three insights. I'm not well clued up about how secure feeds work but I believe you'd need to be logged into the Virtual Private Network in order for your RSS reader to have any kind of access to the feeds produced in there? As for aggregation and republishing, well I think that can be abstracted beyond the need for any kind mandated software through the use of standard formats, ie OPML. Thanks for all three insights. I’m not well clued up about how secure feeds work but I believe you’d need to be logged into the Virtual Private Network in order for your RSS reader to have any kind of access to the feeds produced in there? As for aggregation and republishing, well I think that can be abstracted beyond the need for any kind mandated software through the use of standard formats, ie OPML.

]]> By: Jamed Dellow http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-9260 Jamed Dellow Fri, 14 Dec 2007 06:31:24 +0000 http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-9260 Enterprise RSS isn't just about the "reader" software, its also about having an RSS server that allows you to tap into the social aspects mentioned by Niall and easy integration with other enterprise systems to generate useful RSS content. The other issue is that in terms of broad support for secure feeds, the RSS world is pretty immature so for the moment an enterprise-based solution is the best way to go. The ideal enterprise solution should also enable multiple access points for consuming RSS feeds (desktop alerts, screen savers, via email client, via instant messaging client, and Web-based client), should work inside and outside the firewall and do it in a way that means you only have to read something once. It shouldn't be about locking you into one interface, but at the moment it might mean a set of mandated tools because of the secure feed limitations. Of course if secure feeds aren't issue, pick what ever reader you like. Enterprise RSS isn’t just about the “reader” software, its also about having an RSS server that allows you to tap into the social aspects mentioned by Niall and easy integration with other enterprise systems to generate useful RSS content. The other issue is that in terms of broad support for secure feeds, the RSS world is pretty immature so for the moment an enterprise-based solution is the best way to go. The ideal enterprise solution should also enable multiple access points for consuming RSS feeds (desktop alerts, screen savers, via email client, via instant messaging client, and Web-based client), should work inside and outside the firewall and do it in a way that means you only have to read something once. It shouldn’t be about locking you into one interface, but at the moment it might mean a set of mandated tools because of the secure feed limitations. Of course if secure feeds aren’t issue, pick what ever reader you like.

]]> By: Tino http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-9193 Tino Thu, 13 Dec 2007 10:59:27 +0000 http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-9193 Where I work is up to the individual to decide which RSS reader (or any other software) he uses. I think that is quite personal and shouldn't be standardized. People are different and give priority to different features. Where I work is up to the individual to decide which RSS reader (or any other software) he uses.
I think that is quite personal and shouldn’t be standardized. People are different and give priority to different features.

]]> By: Niall Cook http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-9118 Niall Cook Wed, 12 Dec 2007 09:01:47 +0000 http://distributedresearch.net/blog/2007/12/12/enterprise-rss#comment-9118 It's a good point Andy (and I say that as someone tasked with "standardising" on an RSS reader for our company in 2008). I think you're right about the personal productivity thing, but the main benefit I see - to both an organisation and its employees - of standardisation is the ability to aggregate. By this I mean the ability for an employee to see what the most popular feeds amongst co-workers are, for instance. Or being able to search other people's feeds and not just their own. Public web readers like Bloglines already do this, and I find it incredibly useful to be able to tap into the "wisdom of the crowd" as well as use it for my own personal benefit. I suspect, however, that most companies are simply looking at standardisation from the point of view of ease of deployment, maintenance and control, and not from the point of view of the end user, and that is a shame. All the personalisation you mention re: structure, layout, styles, etc. can certainly all be accommodated with software that supports custom themes and styles for each person. It’s a good point Andy (and I say that as someone tasked with “standardising” on an RSS reader for our company in 2008). I think you’re right about the personal productivity thing, but the main benefit I see - to both an organisation and its employees - of standardisation is the ability to aggregate.

By this I mean the ability for an employee to see what the most popular feeds amongst co-workers are, for instance. Or being able to search other people’s feeds and not just their own. Public web readers like Bloglines already do this, and I find it incredibly useful to be able to tap into the “wisdom of the crowd” as well as use it for my own personal benefit.

I suspect, however, that most companies are simply looking at standardisation from the point of view of ease of deployment, maintenance and control, and not from the point of view of the end user, and that is a shame.

All the personalisation you mention re: structure, layout, styles, etc. can certainly all be accommodated with software that supports custom themes and styles for each person.

]]>