<?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: Functional Requirements for Segue Replacements</title>
	<atom:link href="http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/feed/" rel="self" type="application/rss+xml" />
	<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/</link>
	<description>We Bring Knowledge to You</description>
	<lastBuildDate>Mon, 29 Apr 2013 18:45:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Alex Chapin</title>
		<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/comment-page-1/#comment-16867</link>
		<dc:creator>Alex Chapin</dc:creator>
		<pubDate>Tue, 20 Apr 2010 20:15:35 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=22809#comment-16867</guid>
		<description><![CDATA[Whatever format we choose for archiving should be as simple as possible so that it can be stored on a server or on CD.]]></description>
		<content:encoded><![CDATA[<p>Whatever format we choose for archiving should be as simple as possible so that it can be stored on a server or on CD.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg Humphrey</title>
		<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/comment-page-1/#comment-16863</link>
		<dc:creator>Gregg Humphrey</dc:creator>
		<pubDate>Tue, 20 Apr 2010 18:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=22809#comment-16863</guid>
		<description><![CDATA[Thanks, Alex
So storage if archived the way you suggest would then be somewhere on our servers as opposed to a CD.  Is that right?]]></description>
		<content:encoded><![CDATA[<p>Thanks, Alex<br />
So storage if archived the way you suggest would then be somewhere on our servers as opposed to a CD.  Is that right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Chapin</title>
		<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/comment-page-1/#comment-16860</link>
		<dc:creator>Alex Chapin</dc:creator>
		<pubDate>Tue, 20 Apr 2010 16:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=22809#comment-16860</guid>
		<description><![CDATA[This is a great tip, thanks.]]></description>
		<content:encoded><![CDATA[<p>This is a great tip, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian McBride</title>
		<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/comment-page-1/#comment-16838</link>
		<dc:creator>Ian McBride</dc:creator>
		<pubDate>Mon, 19 Apr 2010 23:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=22809#comment-16838</guid>
		<description><![CDATA[One thing you might consider is using Acrobat to generate PDF archival copies of web pages. You can point Acrobat at a URL and it will archive the page and any subpages in PDF form, with searchable text, graphics and embedded links.]]></description>
		<content:encoded><![CDATA[<p>One thing you might consider is using Acrobat to generate PDF archival copies of web pages. You can point Acrobat at a URL and it will archive the page and any subpages in PDF form, with searchable text, graphics and embedded links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Chapin</title>
		<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/comment-page-1/#comment-16825</link>
		<dc:creator>Alex Chapin</dc:creator>
		<pubDate>Mon, 19 Apr 2010 13:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=22809#comment-16825</guid>
		<description><![CDATA[Thanks for reminding us of the needs of the Education Studies program.  We were aware that Education Studies e-portfolios need to be available for at least 5 years and remain committed to ensuring this availability for all existing e-portfolios.

To ensure new platforms can also guarantee this availability, I&#039;ve added a section to the functional requirements page about content migration.  One option is to export e-portfolios to &quot;static&quot; HTML, a simple format that can be easily maintained without requiring databases or web applications.  Another option is to be able to export e-portfolios to a widely supported &quot;open standard&quot; XML format that can then be imported into freely available hosted web applications.  Both options would allow us to maintain archival copies and allow students to take their e-portfolios with them and set them up with a service provider of their choosing so they can continue to develop them. 

Hope this makes sense and seems reasonable.  Let me know if you have more questions/concerns.]]></description>
		<content:encoded><![CDATA[<p>Thanks for reminding us of the needs of the Education Studies program.  We were aware that Education Studies e-portfolios need to be available for at least 5 years and remain committed to ensuring this availability for all existing e-portfolios.</p>
<p>To ensure new platforms can also guarantee this availability, I&#8217;ve added a section to the functional requirements page about content migration.  One option is to export e-portfolios to &#8220;static&#8221; HTML, a simple format that can be easily maintained without requiring databases or web applications.  Another option is to be able to export e-portfolios to a widely supported &#8220;open standard&#8221; XML format that can then be imported into freely available hosted web applications.  Both options would allow us to maintain archival copies and allow students to take their e-portfolios with them and set them up with a service provider of their choosing so they can continue to develop them. </p>
<p>Hope this makes sense and seems reasonable.  Let me know if you have more questions/concerns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregg Humphrey</title>
		<link>http://sites.middlebury.edu/lis/2010/04/14/functional-requirements-for-segue-replacements/comment-page-1/#comment-16666</link>
		<dc:creator>Gregg Humphrey</dc:creator>
		<pubDate>Wed, 14 Apr 2010 21:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://sites.middlebury.edu/lis/?p=22809#comment-16666</guid>
		<description><![CDATA[I&#039;m not sure I see retrievable storage capacity on this list.  Our program, Education Studies, has a need (state mandated) to at least save a site for at least five-seven years so that when we are audited we can show what was developed at a given point in time.  I guess saving to disk might be an option if disks are indeed still in use in the future. Ideally, also, students often add to their sites after graduating and thus &quot;accessing after graduating&quot; is also an issue.  Suggesting a way to crawl a site to a platform that charges a fee might a way to do this but we&#039;d still need to have that original work archived.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I see retrievable storage capacity on this list.  Our program, Education Studies, has a need (state mandated) to at least save a site for at least five-seven years so that when we are audited we can show what was developed at a given point in time.  I guess saving to disk might be an option if disks are indeed still in use in the future. Ideally, also, students often add to their sites after graduating and thus &#8220;accessing after graduating&#8221; is also an issue.  Suggesting a way to crawl a site to a platform that charges a fee might a way to do this but we&#8217;d still need to have that original work archived.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
