<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Remember Portals? How Can You Forget?</title>
	<atom:link href="http://www.fastforwardblog.com/2010/06/30/remember-portals-how-can-you-forget/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fastforwardblog.com/2010/06/30/remember-portals-how-can-you-forget/</link>
	<description></description>
	<lastBuildDate>Fri, 28 Oct 2011 01:28:22 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Larry Hawes</title>
		<link>http://www.fastforwardblog.com/2010/06/30/remember-portals-how-can-you-forget/comment-page-1/#comment-299294</link>
		<dc:creator>Larry Hawes</dc:creator>
		<pubDate>Thu, 01 Jul 2010 19:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.fastforwardblog.com/?p=5051#comment-299294</guid>
		<description>It is interesting to note that the &quot;home&quot; pages of most existing E2.0 software suites strongly resemble portals. E2.0 suites aggregate information from various sources into a single interface populated by various widgets, just like portals. However, E2.0 suites have not been able to supply the same level of profile-driven information personalization that portals provide.

Perhaps the most glaring example is the activity stream that has become the visual and functional centerpiece of most E2.0 suites. Users must manually filter the stream to isolate updates from specific individuals, groups, applications, etc. If the activity stream were embedded in a portal, the personalization technology in the portal framework could automatically filter the stream for the individual, based on current work context. 

So until E2.0 suites offer better personalization functionality, portals infused with collaboration functionality may offer a better alternative for knowledge workers drowning in information.</description>
		<content:encoded><![CDATA[<p>It is interesting to note that the &#8220;home&#8221; pages of most existing E2.0 software suites strongly resemble portals. E2.0 suites aggregate information from various sources into a single interface populated by various widgets, just like portals. However, E2.0 suites have not been able to supply the same level of profile-driven information personalization that portals provide.</p>
<p>Perhaps the most glaring example is the activity stream that has become the visual and functional centerpiece of most E2.0 suites. Users must manually filter the stream to isolate updates from specific individuals, groups, applications, etc. If the activity stream were embedded in a portal, the personalization technology in the portal framework could automatically filter the stream for the individual, based on current work context. </p>
<p>So until E2.0 suites offer better personalization functionality, portals infused with collaboration functionality may offer a better alternative for knowledge workers drowning in information.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

