<?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: DataPortability looks set to massively increase the value of the Net to users	</title>
	<atom:link href="https://rossdawson.com/dataportability/feed/" rel="self" type="application/rss+xml" />
	<link>https://rossdawson.com/dataportability/</link>
	<description>Keynote speaker &#124; Futurist &#124; Strategy advisor</description>
	<lastBuildDate>Fri, 01 Feb 2008 13:43:52 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Matthias		</title>
		<link>https://rossdawson.com/dataportability/#comment-270</link>

		<dc:creator><![CDATA[Matthias]]></dc:creator>
		<pubDate>Fri, 01 Feb 2008 13:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://rd.wpram.com/?p=454#comment-270</guid>

					<description><![CDATA[I think it is not only a matter of time. It is also a matter of securing and keeping my work. All elements are uploaded, organized, tagged and commented. But what happens when the Web 2.0 application of my choice will be shut down for whatever reason. Maybe I get my material out via an API or export function. But this usually results in an XML file unreadable for humans. When everything is stored in a desktop application, I can keep those application even when the vendor decides to stop it. I can keep it forever or have at least more than enough time to bring the content into new tool. For this disappearing 2.0 tool, I have no influence on the closing schedule.
]]></description>
			<content:encoded><![CDATA[<p>I think it is not only a matter of time. It is also a matter of securing and keeping my work. All elements are uploaded, organized, tagged and commented. But what happens when the Web 2.0 application of my choice will be shut down for whatever reason. Maybe I get my material out via an API or export function. But this usually results in an XML file unreadable for humans. When everything is stored in a desktop application, I can keep those application even when the vendor decides to stop it. I can keep it forever or have at least more than enough time to bring the content into new tool. For this disappearing 2.0 tool, I have no influence on the closing schedule.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
