<?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: Is data portability boring?</title>
	<atom:link href="http://blog.twinloops.com/2008/03/07/is-data-portability-boring/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.twinloops.com/2008/03/07/is-data-portability-boring/</link>
	<description>Jan's thoughts on tech</description>
	<pubDate>Mon, 21 May 2012 00:19:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jan Dawson</title>
		<link>http://blog.twinloops.com/2008/03/07/is-data-portability-boring/comment-page-1/#comment-19</link>
		<dc:creator>Jan Dawson</dc:creator>
		<pubDate>Sat, 08 Mar 2008 18:03:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twinloops.com/2008/03/07/is-data-portability-boring/#comment-19</guid>
		<description>Thanks Mike. I have posted on the topic several times previously too, and those posts can be viewed by using the "data portability" category either at the end of the post above or using the links in the sidebar to the right.</description>
		<content:encoded><![CDATA[<p>Thanks Mike. I have posted on the topic several times previously too, and those posts can be viewed by using the &#8220;data portability&#8221; category either at the end of the post above or using the links in the sidebar to the right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Reynolds</title>
		<link>http://blog.twinloops.com/2008/03/07/is-data-portability-boring/comment-page-1/#comment-18</link>
		<dc:creator>Mike Reynolds</dc:creator>
		<pubDate>Fri, 07 Mar 2008 23:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.twinloops.com/2008/03/07/is-data-portability-boring/#comment-18</guid>
		<description>Hi Jan.  I'm one of the co-founders of DataPortability.org and wanted to thank you for your post.

In the last sentence of your post, you hit on the real value of DataPortability.  Via our discussions with industry professionals, there is value in having distributed access to your data.  

That is, you can have one master profile and extended data set which you can access from any DataPortability-compliant site.  So it really gives you a reason to stick around at the sites you like.  It also puts more pressure on the site to offer a valued differentiated product.

Here's a link to a presentation given recently by Charlene Li of Forrester:
http://www.slideshare.net/charleneli/the-future-of-social-networks?src=embed

And you are welcome to stop by and chat with us here if you like:
http://groups.google.com/group/dataportability-public

Cheers,
Mike</description>
		<content:encoded><![CDATA[<p>Hi Jan.  I&#8217;m one of the co-founders of DataPortability.org and wanted to thank you for your post.</p>
<p>In the last sentence of your post, you hit on the real value of DataPortability.  Via our discussions with industry professionals, there is value in having distributed access to your data.  </p>
<p>That is, you can have one master profile and extended data set which you can access from any DataPortability-compliant site.  So it really gives you a reason to stick around at the sites you like.  It also puts more pressure on the site to offer a valued differentiated product.</p>
<p>Here&#8217;s a link to a presentation given recently by Charlene Li of Forrester:<br />
<a href="http://www.slideshare.net/charleneli/the-future-of-social-networks?src=embed" rel="nofollow">http://www.slideshare.net/charleneli/the-future-of-social-networks?src=embed</a></p>
<p>And you are welcome to stop by and chat with us here if you like:<br />
<a href="http://groups.google.com/group/dataportability-public" rel="nofollow">http://groups.google.com/group/dataportability-public</a></p>
<p>Cheers,<br />
Mike</p>
]]></content:encoded>
	</item>
</channel>
</rss>

