<?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: OpenSocial and Address Book 2.0: Putting People into the Protocol</title>
	<atom:link href="http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<lastBuildDate>Tue, 18 Jan 2011 00:50:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Volatile (ie., highly dynamic) supergraphs &#171; Utterances of a Zimboe</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-98475</link>
		<dc:creator>Volatile (ie., highly dynamic) supergraphs &#171; Utterances of a Zimboe</dc:creator>
		<pubDate>Sun, 27 Jan 2008 15:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-98475</guid>
		<description>[...] (ie., highly dynamic)&#160;supergraphs  Update: Chris Messina had similar thoughts a month earlier: In fact, it’s no longer even in your best interest to store data about people [...]</description>
		<content:encoded><![CDATA[<p>[...] (ie., highly dynamic)&nbsp;supergraphs  Update: Chris Messina had similar thoughts a month earlier: In fact, it’s no longer even in your best interest to store data about people [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: It&#8217;s about interaction stupid! &#171; Alexander van Elsas&#8217;s Weblog on new media &#38; technologies and their effect on social behavior</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-97168</link>
		<dc:creator>It&#8217;s about interaction stupid! &#171; Alexander van Elsas&#8217;s Weblog on new media &#38; technologies and their effect on social behavior</dc:creator>
		<pubDate>Tue, 27 Nov 2007 09:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-97168</guid>
		<description>[...] that it solves the current issues with data portability and privacy automatically. It&#8217;s what Chris Messina calls the citizens web, I prefer calling it the user centric web. If user value is the core of your business model, then [...]</description>
		<content:encoded><![CDATA[<p>[...] that it solves the current issues with data portability and privacy automatically. It&#8217;s what Chris Messina calls the citizens web, I prefer calling it the user centric web. If user value is the core of your business model, then [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I never knew &#187; Blog Archive &#187; Google Open Social</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-97134</link>
		<dc:creator>I never knew &#187; Blog Archive &#187; Google Open Social</dc:creator>
		<pubDate>Sun, 25 Nov 2007 22:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-97134</guid>
		<description>[...] Imagine this: imagine designing a web service where you don’t store the permanent records of facets of people, but instead you simply build services that serve people. In fact, it’s no longer even in your best interest to store data about people long term because, in fact, the data ages so rapidly that it’s next to useless to try to keep up with it. Instead, it’s about looking across the data that someone makes transactionally available to you (for a split second) and offering up the best service given what you’ve observed when similar fingerprint-profiles have come to your system in the past. It’s not so much about owning or storing Address Book 2.0 as much as being ready when all the people that populate the decentralized Address Book 2.0 concept come knocking at your door.&#8212;Opensocial and address book 20 putting people into the protocol [...]</description>
		<content:encoded><![CDATA[<p>[...] Imagine this: imagine designing a web service where you don’t store the permanent records of facets of people, but instead you simply build services that serve people. In fact, it’s no longer even in your best interest to store data about people long term because, in fact, the data ages so rapidly that it’s next to useless to try to keep up with it. Instead, it’s about looking across the data that someone makes transactionally available to you (for a split second) and offering up the best service given what you’ve observed when similar fingerprint-profiles have come to your system in the past. It’s not so much about owning or storing Address Book 2.0 as much as being ready when all the people that populate the decentralized Address Book 2.0 concept come knocking at your door.&#8212;Opensocial and address book 20 putting people into the protocol [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roop says &#187; Blog Archive &#187; Is Open Social, Open Friend?</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96501</link>
		<dc:creator>Roop says &#187; Blog Archive &#187; Is Open Social, Open Friend?</dc:creator>
		<pubDate>Tue, 13 Nov 2007 00:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96501</guid>
		<description>[...] Google announces OpenSocial. I have watched the video, read over the spec, and even read other people&#8217;s interpretation of what OpenSocial is or could be, but I am still not sure it is open [...]</description>
		<content:encoded><![CDATA[<p>[...] Google announces OpenSocial. I have watched the video, read over the spec, and even read other people&#8217;s interpretation of what OpenSocial is or could be, but I am still not sure it is open [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96425</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Wed, 07 Nov 2007 04:37:42 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96425</guid>
		<description>Hey Chris, great writeup. I&#039;d be interested in hearing your viewpoint on OpenSocial now that it&#039;s had a bit of time to stew.

I completely agree with your idea about &quot;creating services for people&quot;. Our grandchildren will think maintaining multiple profiles is as ridiculous and tedious as &quot;balancing your checkbook.&quot;</description>
		<content:encoded><![CDATA[<p>Hey Chris, great writeup. I&#8217;d be interested in hearing your viewpoint on OpenSocial now that it&#8217;s had a bit of time to stew.</p>
<p>I completely agree with your idea about &#8220;creating services for people&#8221;. Our grandchildren will think maintaining multiple profiles is as ridiculous and tedious as &#8220;balancing your checkbook.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf Skyberg</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96424</link>
		<dc:creator>Rolf Skyberg</dc:creator>
		<pubDate>Wed, 07 Nov 2007 04:35:09 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96424</guid>
		<description>Hey Chris-

Now that OpenSocial has been stewing for a while in the public sphere, I&#039;d love to get your take on what it&#039;s all about and whether it lives up to the hype.

BTW, I completely agree with your &quot;just build services for people&quot; argument. Our grandchildren aren&#039;t going to put up with maintaining more than a few &quot;profiles&quot;.</description>
		<content:encoded><![CDATA[<p>Hey Chris-</p>
<p>Now that OpenSocial has been stewing for a while in the public sphere, I&#8217;d love to get your take on what it&#8217;s all about and whether it lives up to the hype.</p>
<p>BTW, I completely agree with your &#8220;just build services for people&#8221; argument. Our grandchildren aren&#8217;t going to put up with maintaining more than a few &#8220;profiles&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flailing Wildly &#187; Blog Archive &#187;</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96364</link>
		<dc:creator>Flailing Wildly &#187; Blog Archive &#187;</dc:creator>
		<pubDate>Mon, 05 Nov 2007 17:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96364</guid>
		<description>[...] Last year, I co-founded a company by the name of Foleeo (which will likely change names because of Palm&#8217;s Foleo) that is working on a solution to the ever-increasing rift between record labels, movie studios, and people like you and me who want to get music, movies, and TV shows under far more reasonable terms. But like Google with search, that&#8217;s simply where we&#8217;re starting. We&#8217;re also working on what I (very esoterically) refer to the &#8220;citizen-centric social anti-network&#8221;. Many of the ideas behind this venture were recently described my Chris Messina in a much more eloquent manner: [...]</description>
		<content:encoded><![CDATA[<p>[...] Last year, I co-founded a company by the name of Foleeo (which will likely change names because of Palm&#8217;s Foleo) that is working on a solution to the ever-increasing rift between record labels, movie studios, and people like you and me who want to get music, movies, and TV shows under far more reasonable terms. But like Google with search, that&#8217;s simply where we&#8217;re starting. We&#8217;re also working on what I (very esoterically) refer to the &#8220;citizen-centric social anti-network&#8221;. Many of the ideas behind this venture were recently described my Chris Messina in a much more eloquent manner: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scattershooting at Like It Matters</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96355</link>
		<dc:creator>Scattershooting at Like It Matters</dc:creator>
		<pubDate>Mon, 05 Nov 2007 13:25:11 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96355</guid>
		<description>[...] FactoryJoe:  Putting people into the protocol. [...]</description>
		<content:encoded><![CDATA[<p>[...] FactoryJoe:  Putting people into the protocol. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Power to the widgets</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96340</link>
		<dc:creator>Power to the widgets</dc:creator>
		<pubDate>Sun, 04 Nov 2007 12:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96340</guid>
		<description>[...] weeks announcement about Google OpenSocial. Several sources have discussed it&#8217;s potential impact.  It&#8217;s not me, it&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] weeks announcement about Google OpenSocial. Several sources have discussed it&#8217;s potential impact.  It&#8217;s not me, it&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/comment-page-1/#comment-96324</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Fri, 02 Nov 2007 17:00:07 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/2007/10/31/opensocial-and-address-book-20-putting-people-into-the-protocol/#comment-96324</guid>
		<description>@John: You raise a good point, but I suppose I&#039;m imagining a semi-distant future where the transfer costs of data moves to almost nil, so that you can multiple original sources of data strewn about and still be able to access and make calculations on that data on the fly. 

I also imagine that your identity provider will both store and federate a lot of data on your behalf, controlling access with revokable OAuth tokens and OpenID-set permissions. It&#039;ll be no different than your credit card today -- where a bank stores and &quot;federates&quot; money to the places where you make payments or take out money from ATMs. (Hence a post I&#039;m writing called &quot;Data Capital&quot;). 

In any case, we&#039;re a long ways off from what I&#039;m talking about, but in a citizen-centric web, you get to choose who has access to your data and for how long because you choose your identity provider (hopefully, wisely).

@Chris Jay: I agree... we&#039;re essentially countering the problem that siloed-email servers had decades ago when they didn&#039;t intermingle. Since social networks are essentially glorified email-sending machines, it&#039;s only logical that we begin to be able to send messages (and other types of data and functionality) betwixt them.

As for using specific URIs for different identities, this is &lt;em&gt;exactly&lt;/em&gt; how it&#039;s supposed to work! And I&#039;m glad that you make that point, because that, again, is how you&#039;ll be able to slice your identit[ies] and keep them distinct, but also under your own control. OpenID does provide for personas, but if you want to maintain completely separate identities, you can do so with uncorroborated identifiers.</description>
		<content:encoded><![CDATA[<p>@John: You raise a good point, but I suppose I&#8217;m imagining a semi-distant future where the transfer costs of data moves to almost nil, so that you can multiple original sources of data strewn about and still be able to access and make calculations on that data on the fly. </p>
<p>I also imagine that your identity provider will both store and federate a lot of data on your behalf, controlling access with revokable OAuth tokens and OpenID-set permissions. It&#8217;ll be no different than your credit card today &#8212; where a bank stores and &#8220;federates&#8221; money to the places where you make payments or take out money from ATMs. (Hence a post I&#8217;m writing called &#8220;Data Capital&#8221;). </p>
<p>In any case, we&#8217;re a long ways off from what I&#8217;m talking about, but in a citizen-centric web, you get to choose who has access to your data and for how long because you choose your identity provider (hopefully, wisely).</p>
<p>@Chris Jay: I agree&#8230; we&#8217;re essentially countering the problem that siloed-email servers had decades ago when they didn&#8217;t intermingle. Since social networks are essentially glorified email-sending machines, it&#8217;s only logical that we begin to be able to send messages (and other types of data and functionality) betwixt them.</p>
<p>As for using specific URIs for different identities, this is <em>exactly</em> how it&#8217;s supposed to work! And I&#8217;m glad that you make that point, because that, again, is how you&#8217;ll be able to slice your identit[ies] and keep them distinct, but also under your own control. OpenID does provide for personas, but if you want to maintain completely separate identities, you can do so with uncorroborated identifiers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

