<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Delivering data portability.  Let&#8217;s start with managing expectations.</title>
	<atom:link href="http://blog.foldier.com/2008/03/27/delivering-data-portability-lets-start-with-managing-expectations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.foldier.com/2008/03/27/delivering-data-portability-lets-start-with-managing-expectations/</link>
	<description>Search • Share • Relate</description>
	<lastBuildDate>Mon, 08 Mar 2010 17:38:25 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matteo Fabiano</title>
		<link>http://blog.foldier.com/2008/03/27/delivering-data-portability-lets-start-with-managing-expectations/#comment-79</link>
		<dc:creator>Matteo Fabiano</dc:creator>
		<pubDate>Wed, 02 Apr 2008 17:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://foldier.wordpress.com/?p=35#comment-79</guid>
		<description>From the DP.org website FAQ: &quot;DataPortability is not inventing any new standards.&quot; Well, if in fact DP.org&#039;s mission is to &quot;package&quot; a set of existing standards for consumers, businesses, and stakeholders, the project is, at its core a (very ambitious) &quot;communications&quot; project.  Oversimplifying, it is, in the best sense possible, a PR operation.</description>
		<content:encoded><![CDATA[<p>From the DP.org website FAQ: &#8220;DataPortability is not inventing any new standards.&#8221; Well, if in fact DP.org&#8217;s mission is to &#8220;package&#8221; a set of existing standards for consumers, businesses, and stakeholders, the project is, at its core a (very ambitious) &#8220;communications&#8221; project.  Oversimplifying, it is, in the best sense possible, a PR operation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: foldierteam</title>
		<link>http://blog.foldier.com/2008/03/27/delivering-data-portability-lets-start-with-managing-expectations/#comment-75</link>
		<dc:creator>foldierteam</dc:creator>
		<pubDate>Tue, 01 Apr 2008 05:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://foldier.wordpress.com/?p=35#comment-75</guid>
		<description>Trent and Darryl, your points are excellent.  This is definitely as much about exposing ideas and acting deliberately as it is about acting quickly and satisfying the objectives of individual constituencies.</description>
		<content:encoded><![CDATA[<p>Trent and Darryl, your points are excellent.  This is definitely as much about exposing ideas and acting deliberately as it is about acting quickly and satisfying the objectives of individual constituencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darryl Patterson</title>
		<link>http://blog.foldier.com/2008/03/27/delivering-data-portability-lets-start-with-managing-expectations/#comment-69</link>
		<dc:creator>Darryl Patterson</dc:creator>
		<pubDate>Fri, 28 Mar 2008 14:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://foldier.wordpress.com/?p=35#comment-69</guid>
		<description>The goal with this kind of initiative (Data Portability) is to get stakeholders, users, experts, etc involved with the project right from day one. In order to get the awareness that such a project exists, ya gotta use PR; you have to get the word out and get the credible people you need on board.

The ever present issue with building a community around this kind of project so early in the game, is that there will always be a perceived lack of progress. The design &amp; analysis stages of API development are CRUCIAL and TIME CONSUMING! But they are also stages that don&#039;t produce &quot;products&quot; that people can interact with. Google&#039;s Open Social is going through the same issues... Java went through the same in the early 90&#039;s... lots of hype, but the perception that nothing was being delivered.

The &quot;do-ers&quot; get this. The users, no matter how technical they feel they are, usually don&#039;t. The users of the world want to use a product, not read specs and learn APIs. As a result, they tend to complain that there&#039;s no progress, when what they really mean is that there is no &quot;perceived&quot; progress.</description>
		<content:encoded><![CDATA[<p>The goal with this kind of initiative (Data Portability) is to get stakeholders, users, experts, etc involved with the project right from day one. In order to get the awareness that such a project exists, ya gotta use PR; you have to get the word out and get the credible people you need on board.</p>
<p>The ever present issue with building a community around this kind of project so early in the game, is that there will always be a perceived lack of progress. The design &amp; analysis stages of API development are CRUCIAL and TIME CONSUMING! But they are also stages that don&#8217;t produce &#8220;products&#8221; that people can interact with. Google&#8217;s Open Social is going through the same issues&#8230; Java went through the same in the early 90&#8217;s&#8230; lots of hype, but the perception that nothing was being delivered.</p>
<p>The &#8220;do-ers&#8221; get this. The users, no matter how technical they feel they are, usually don&#8217;t. The users of the world want to use a product, not read specs and learn APIs. As a result, they tend to complain that there&#8217;s no progress, when what they really mean is that there is no &#8220;perceived&#8221; progress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Trent Adams</title>
		<link>http://blog.foldier.com/2008/03/27/delivering-data-portability-lets-start-with-managing-expectations/#comment-68</link>
		<dc:creator>J. Trent Adams</dc:creator>
		<pubDate>Fri, 28 Mar 2008 12:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://foldier.wordpress.com/?p=35#comment-68</guid>
		<description>Mary -

Nicely stated.  In a nutshell, the DataPortability Project is struggling with thorny issues and is still learning how to function effectively within a non-centralized, distributed, volunteer environment.

For my part, I&#039;m totally impressed with how the organic nature of the movement has been growing under the nurturing care of the participants.  While we may not be churning out actionable standards or best practices, yet, the &quot;PR&quot; effort appears to be doing a fantastic job of facilitating a much-needed dialog.

At the very least, the DataPortability Project has been an effective catalyst.  Only time will tell, however, what kind of ongoing effect it&#039;ll have.  My guess is that if the active participants can keep up the momentum, the project will continue to flourish and deliver more concrete output.

- Trent

(PS You have a fun flair for the dramatic, making for a great read.)</description>
		<content:encoded><![CDATA[<p>Mary -</p>
<p>Nicely stated.  In a nutshell, the DataPortability Project is struggling with thorny issues and is still learning how to function effectively within a non-centralized, distributed, volunteer environment.</p>
<p>For my part, I&#8217;m totally impressed with how the organic nature of the movement has been growing under the nurturing care of the participants.  While we may not be churning out actionable standards or best practices, yet, the &#8220;PR&#8221; effort appears to be doing a fantastic job of facilitating a much-needed dialog.</p>
<p>At the very least, the DataPortability Project has been an effective catalyst.  Only time will tell, however, what kind of ongoing effect it&#8217;ll have.  My guess is that if the active participants can keep up the momentum, the project will continue to flourish and deliver more concrete output.</p>
<p>- Trent</p>
<p>(PS You have a fun flair for the dramatic, making for a great read.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
