<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The DataPortability Project &#187; everfresh</title>
	<atom:link href="http://blog.dataportability.org/tag/everfresh/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dataportability.org</link>
	<description> Connect. Control. Share. Remix.</description>
	<lastBuildDate>Tue, 05 Jul 2011 15:44:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Open Arms: a data portability approach</title>
		<link>http://blog.dataportability.org/2009/05/06/open-arms-a-data-portability-approach/</link>
		<comments>http://blog.dataportability.org/2009/05/06/open-arms-a-data-portability-approach/#comments</comments>
		<pubDate>Wed, 06 May 2009 16:31:54 +0000</pubDate>
		<dc:creator>Phil Wolff</dc:creator>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[data portability]]></category>
		<category><![CDATA[dataportability]]></category>
		<category><![CDATA[dpp]]></category>
		<category><![CDATA[eula]]></category>
		<category><![CDATA[everfresh]]></category>
		<category><![CDATA[gracefulexit]]></category>
		<category><![CDATA[open arms]]></category>
		<category><![CDATA[openarms]]></category>
		<category><![CDATA[task force]]></category>

		<guid isPermaLink="false">http://blog.dataportability.org/?p=228</guid>
		<description><![CDATA[<p></p> <p>Caveat Lector: this is a rough draft of my thinking on what a Portability EULA/ToS should say/do/include. Please comment. In the EULA/ToS task force, we are exploring ways of explaining portability with simple analogies. - Phil </p> <p>We&#8217;ve discussed Graceful Exit, the ability for people to control their departure from a site or <span style="color:#777"> . . . &#8594; Read More: <a href="http://blog.dataportability.org/2009/05/06/open-arms-a-data-portability-approach/">Open Arms: a data portability approach</a></span>]]></description>
			<content:encoded><![CDATA[<p><a title="Open Arms hug by PhilWolff, on Flickr" href="http://www.flickr.com/photos/philwolff/3486993182/"><img style="border-right-width: 0px; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" src="http://farm4.static.flickr.com/3598/3486993182_0e7bf3568d.jpg" border="0" alt="Open Arms hug" width="500" height="333" /></a></p>
<p><em>Caveat Lector: this is a rough draft of my thinking on what a Portability EULA/ToS should say/do/include. Please comment. In the <a href="http://wiki.dataportability.org/x/mIRE">EULA/ToS task force</a>, we are exploring  ways of explaining portability with simple analogies. </em><em>- Phil<br />
</em></p>
<p>We&#8217;ve discussed <a href="http://blog.dataportability.org/index.php/2009/01/the-power-to-fight-eviction/">Graceful Exit</a>, the ability for people to control their departure from a site or service.</p>
<p><strong>Open Arms</strong> starts at the beginning of your relationship with a service. Let&#8217;s summarize it, break it apart, and explain why this is a powerful way to do business.</p>
<h4>Open Arms is a combination of policy and technology.</h4>
<p><strong>The policy says:</strong></p>
<blockquote><p><strong>When you come to our site,<br />
bring all of yourself.<br />
We&#8217;ll help you put it to use<br />
in our context.<br />
We&#8217;ll make it easy to come.<br />
We&#8217;ll keep it safe.<br />
We&#8217;ll respect ownership as you see it. </strong></p>
<p><strong>What you add while you are here<br />
will join your collection<br />
and be portable in turn.</strong></p></blockquote>
<h4>The elements.</h4>
<p><strong>All of yourself. </strong></p>
<p>Bring your identity, your contacts, your history with your contacts, your photos and videos, your playlists, everything digital.</p>
<p>We&#8217;ll ignore what we cannot use.</p>
<p><strong>Put it to use in our context. </strong></p>
<p>Every site has a context.</p>
<ul>
<li>Things it does</li>
<li>Purposes people share</li>
<li>Community standards of behavior.</li>
</ul>
<p>For example:</p>
<ul>
<li>Monster brings work and workers together.</li>
<li>Flickr helps people manage what comes out of their cameras.</li>
<li>YouTube is a community of video.</li>
<li>QuickBooks helps you manage your business.</li>
<li>Chemistry helps you find true love.</li>
<li>Amazon and eBay bring buyers and sellers together.</li>
</ul>
<p>We need your data. These sites could help you do more and do it smarter with more and fresher and truer information from you. Monster could create team job search features if it knew your social graph. Chemistry could be more accurate if it had your music and video playlists.</p>
<p>Our sites are verbs. We do things. The more data you bring, the richer the data, the fresher and more standardized the data, the more we can do, the more creative we can be.</p>
<p>Most people don&#8217;t try new sites because it&#8217;s hard to recreate data. Especially for every site you visit.</p>
<p><strong>Easy. </strong></p>
<p>So for Open Arms to work,  bringing your onlife to each site you join must be fast, simple, easy, and obvious. And correct.</p>
<p><strong>Safe. </strong></p>
<p>We will protect everything you share. We will protect it from damage, theft, natural disaster, financial ruin, legal physical threats, from legal threats, from Martian invasion. As best we can. And we&#8217;ll explain the threats we perceive and how we&#8217;re protecting you and your onlife from them.</p>
<p><strong>Ownership as you see it.</strong></p>
<p>&#8220;Ownership&#8221; is a tricky word: it means one thing to lawyers, something else to most people. Our online and mobile social experiences are a little ahead of the law. So all we can do is try to the right thing for you and for all of our guests.</p>
<p>We&#8217;ll respect that your stuff is only &#8220;mostly&#8221; yours and that you may not have permission to share them with strangers. You may not have permission from the subject of a photo, or their parents. You may have clipped a blog post to share under fair use, but not for general distribution. You may have a confidential email that could endanger lives if leaked.</p>
<p>We will assume everything you bring is private to you and that you will tell us what can be shared, with whom, and under what conditions.</p>
<p>We&#8217;ll make it easy for you to re-use your choices, so you don&#8217;t have to explain yourself everywhere you go.</p>
<p><strong>Portable in turn</strong></p>
<p>Reciprocity works. So we&#8217;re going to share with other sites the part of your onlife you spend with us, as you see fit. So you never feel we&#8217;re holding your data hostage.</p>
<h4>What&#8217;s next?</h4>
<p>So, we&#8217;ve &#8220;Open Arms&#8221; at the start of our relationship and &#8220;Graceful Exit&#8221; at the end. Next up &#8220;Ever Fresh&#8221; in between.</p>
<blockquote style="text-align: center; width: 80%; font-family: monospace;">
<p style="text-align: left"><em>&#8220;</em><a href="http://en.wikipedia.org/wiki/Open_Arms_(Journey_song)"><em>Open Arms</em></a><em>&#8221; written by </em><a href="http://en.wikipedia.org/wiki/Steve_Perry_%28musician%29"><em>Steve Perry</em></a><em> and </em><a href="http://en.wikipedia.org/wiki/Jonathan_Cain"><em>Jonathan Cain</em></a><em>, </em><a href="http://en.wikipedia.org/wiki/Journey_%28band%29"><em>Journey</em></a><em> (1982)</em></p>
<p>Lying beside you, here in the dark<br />
Feeling your heart beat with mind<br />
Softly you whisper, you&#8217;re so sincere<br />
How could our live be so blind<br />
We sailed on together<br />
We drifted apart<br />
And here you are by my side</p>
<p>So now I come to you, with open arms<br />
Nothing to hide, believe what I say<br />
So here I am with open arms<br />
Hoping you&#8217;ll see what your love means to me<br />
Open arms</p>
<p>Living without you, living alone<br />
This empty house seems so cold<br />
Wanting to hold you, wanting you near<br />
How much I wanted you home</p>
<p>But now that you&#8217;ve come back<br />
Turned night into day<br />
I need you to stay.</p>
<p>(chorus)</p></blockquote>
<div id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:ba2f421c-68ed-4a3c-bbe6-ab3d3a9568c5" class="wlWriterEditableSmartContent" style="padding-bottom: 0px; margin: 0px; padding-left: 0px; padding-right: 0px; display: inline; float: none; padding-top: 0px">
<p style="font-size:smaller; background:#f0f0f0; padding:.5em;">tags: <a rel="tag" href="http://technorati.com/tags/dpp">dpp</a>, <a rel="tag" href="http://technorati.com/tags/dataportability">dataportability</a>, <a rel="tag" href="http://technorati.com/tags/openarms">openarms</a>, <a rel="tag" href="http://technorati.com/tags/everfresh">everfresh</a>, <a rel="tag" href="http://technorati.com/tags/gracefulexit">gracefulexit</a></p>
<p style="font-size:smaller"><em>Call me at <a href="skype:+15104554384?call">+1-510-455-4384</a>, <a title="skype:evanwolf?chat" href="skype:evanwolf?chat">Skype me</a>, follow <a href="http://twitter.com/skypejournal">@skypejournal</a> and <a title="twitter" rel="me" href="http://www.twitter.com/evanwolf">@Phil Wolff</a>.<br />
<a title="Skype Journal chat room" rel="me" href="http://tinyurl.com/sjchat">Visit our Skype Journal private roundtable</a>, one of the longest running public Skype chats.</em></p>
</div>
<div class="shr-publisher-228"></div>]]></content:encoded>
			<wfw:commentRss>http://blog.dataportability.org/2009/05/06/open-arms-a-data-portability-approach/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

