<?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/"
		>
<channel>
	<title>Comments on: Proliferating Portals</title>
	<atom:link href="http://blog.learnlets.com/?feed=rss2&#038;p=1466" rel="self" type="application/rss+xml" />
	<link>http://blog.learnlets.com/?p=1466</link>
	<description>Clark Quinn&#039;s learnings about learning</description>
	<lastBuildDate>Tue, 07 Sep 2010 17:21:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Clark</title>
		<link>http://blog.learnlets.com/?p=1466&#038;cpage=1#comment-88015</link>
		<dc:creator>Clark</dc:creator>
		<pubDate>Thu, 18 Feb 2010 17:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.learnlets.com/?p=1466#comment-88015</guid>
		<description>I think that there is one portal for an organization from the outside, but there might be separate portals for different products or services.  If I&#039;m a subscriber, or a product owner, I might want to go directly to my self-service site.  Really, it&#039;s the way the user wants to think about it.  The one portal might contain the others, but as a customer, I might want to go directly to the page with my account or resources.

Also, within an org, I might be a member of several different communities of practice, and maybe a different combination than others.  So, I&#039;d want to visit the portals that I&#039;m interested in.

However, if you&#039;re saying that you want all your portals pulled into one that you access, some custom Personal Working Environment, I&#039;d agree, with the caveat that it&#039;d be a jumping off point to other places.  In a sense, you do that, with your feeds, bookmarks, etc.</description>
		<content:encoded><![CDATA[<p>I think that there is one portal for an organization from the outside, but there might be separate portals for different products or services.  If I&#8217;m a subscriber, or a product owner, I might want to go directly to my self-service site.  Really, it&#8217;s the way the user wants to think about it.  The one portal might contain the others, but as a customer, I might want to go directly to the page with my account or resources.</p>
<p>Also, within an org, I might be a member of several different communities of practice, and maybe a different combination than others.  So, I&#8217;d want to visit the portals that I&#8217;m interested in.</p>
<p>However, if you&#8217;re saying that you want all your portals pulled into one that you access, some custom Personal Working Environment, I&#8217;d agree, with the caveat that it&#8217;d be a jumping off point to other places.  In a sense, you do that, with your feeds, bookmarks, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen J. Gill</title>
		<link>http://blog.learnlets.com/?p=1466&#038;cpage=1#comment-88010</link>
		<dc:creator>Stephen J. Gill</dc:creator>
		<pubDate>Thu, 18 Feb 2010 13:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.learnlets.com/?p=1466#comment-88010</guid>
		<description>I have always thought about &quot;portals&quot; a little differently: one portal per organization. I think of them as a virtual door to information for and about the organization. From the perspective of a user, I want to go to one inter or intranet site to find the information I need. But I&#039;m not an expert on this and welcome your comments.</description>
		<content:encoded><![CDATA[<p>I have always thought about &#8220;portals&#8221; a little differently: one portal per organization. I think of them as a virtual door to information for and about the organization. From the perspective of a user, I want to go to one inter or intranet site to find the information I need. But I&#8217;m not an expert on this and welcome your comments.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
