<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: a random ramble on e-Portfolios</title>
	<link>http://blogs.educationau.edu.au/jleeson/2008/08/26/a-random-ramble-on-e-portfolios/</link>
	<description>a blog by Jerry Leeson</description>
	<pubDate>Wed, 07 Jan 2009 18:33:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Jen</title>
		<link>http://blogs.educationau.edu.au/jleeson/2008/08/26/a-random-ramble-on-e-portfolios/#comment-81485</link>
		<pubDate>Tue, 26 Aug 2008 01:00:03 +0000</pubDate>
		<guid>http://blogs.educationau.edu.au/jleeson/2008/08/26/a-random-ramble-on-e-portfolios/#comment-81485</guid>
					<description>Absolutely - interoperability is key if a portfolio is going to have any use as a lifelong learning tool. A user needs to be able to either move their portfolio around with them, or add bits from different places as their portfolio grows. I think some of this is a web3.0 semantic web kind of application with a widget integration kind of approach. You could have a facebook kind of environment with 'applications' that are all the different components of a portfolio, you could pick and add them to your portfolio, then use privacy settings to decide who can see what. That'd be cool.</description>
		<content:encoded><![CDATA[<p>Absolutely - interoperability is key if a portfolio is going to have any use as a lifelong learning tool. A user needs to be able to either move their portfolio around with them, or add bits from different places as their portfolio grows. I think some of this is a web3.0 semantic web kind of application with a widget integration kind of approach. You could have a facebook kind of environment with &#8216;applications&#8217; that are all the different components of a portfolio, you could pick and add them to your portfolio, then use privacy settings to decide who can see what. That&#8217;d be cool.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
