<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>PebblePad Publications</title>
<description>A selection of publications on e-Portfolios. e-Learning and related topics</description>
<link>http://www.pebblepad.co.uk/servicedata/rss/publications/rss.xml</link>
<lastBuildDate>Thu, 12 Nov 2009 10:35:11 GMT</lastBuildDate>
<copyright>Copyright: (C) Pebble Learning, see http://www.pebblepad.co.uk/terms_of_use.htm for terms and conditions</copyright>
<docs>http://www.pebblepad.co.uk/servicedata/rss/publications/</docs>
<atom:link href="http://www.pebblepad.co.uk/servicedata/rss/publications/rss.xml" rel="self" type="application/rss+xml" />
<image>
<title>PebblePad Publications</title>
<url>http://www.pebblepad.co.uk/img/publication_icon.gif</url>
<link>http://www.pebblepad.co.uk/servicedata/rss/publications/rss.xml</link>
</image>
<item>
<title><![CDATA[What is not an eportfolio]]></title>
<description><![CDATA[by Shane Sutherland Synopsis: There exists a measure of obfuscation and equivocation in the theory and practice of eportfolio. The former resulting, at least in part, from the plethora of technical
projects adding to the extant vocabulary thin model domain mapping identity
management IMSeP interoperability transferability etc. The latter arises from the
very word itself, used variously to describe inputs outputs processes tools and
functions. I will attempt then, in the remaining 1000 words or so, to provide some
clarity – or further muddy the waters – by defining what is not an ePortfolio. I hope
that in so doing we will arrive at a clearer sense of what is an eportfolio.]]></description>
<link><![CDATA[http://www.pebblepad.co.uk/cs_feed.asp?opType=getPublicationRSS&rssid=9]]></link>
<guid><![CDATA[http://www.pebblepad.co.uk/cs_feed.asp?opType=getPublicationRSS&rssid=9]]></guid>
</item>
</channel>
</rss>
