<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Why Flickr Doesn&#8217;t Do FOAF</title>
	<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/</link>
	<description>Semantic Web, Ruby on Rails, and Massive Data</description>
	<pubDate>Sat, 11 Oct 2008 02:56:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: Nodalities &#187; Blog Archive &#187; This Week&#8217;s Semantic Web</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-595</link>
		<dc:creator>Nodalities &#187; Blog Archive &#187; This Week&#8217;s Semantic Web</dc:creator>
		<pubDate>Thu, 17 Apr 2008 16:52:24 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-595</guid>
		<description>[...] Why Flickr Doesn’t Do FOAF - [timbl: So do you think Flickr could be persuaded to source FOAF? dajobe: maybe  ] [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Why Flickr Doesn’t Do FOAF - [timbl: So do you think Flickr could be persuaded to source FOAF? dajobe: maybe  ] [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex.</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-556</link>
		<dc:creator>Alex.</dc:creator>
		<pubDate>Tue, 25 Mar 2008 10:00:48 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-556</guid>
		<description>Richard, thanks for pointing the SHA1 output. I took care of respecting users' privacy with the export service, so there's indeed something wrong, eitheir with the script, or with the Flickr API. I'll check and update the exporter to fix this.</description>
		<content:encoded><![CDATA[<p>Richard, thanks for pointing the SHA1 output. I took care of respecting users&#8217; privacy with the export service, so there&#8217;s indeed something wrong, eitheir with the script, or with the Flickr API. I&#8217;ll check and update the exporter to fix this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-550</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 24 Mar 2008 21:21:18 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-550</guid>
		<description>Looks like Flickr added the mbox_sha1sum property!  That's a good step in the right direction.</description>
		<content:encoded><![CDATA[<p>Looks like Flickr added the mbox_sha1sum property!  That&#8217;s a good step in the right direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cyganiak</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-549</link>
		<dc:creator>Richard Cyganiak</dc:creator>
		<pubDate>Mon, 24 Mar 2008 21:10:21 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-549</guid>
		<description>Alexandre Passant has a &lt;a href="http://apassant.net/blog/2007/12/18/rdf-export-of-flickr-profiles-with-foaf-and-sioc/" rel="nofollow"&gt;quite complete Flickr-to-FOAF export service&lt;/a&gt; that generates FOAF for all Flickr users. It dynamically generates a FOAF profile by interrogating the Flickr API for user details. And apparently, it always includes the SHA1, even if the user doesn't show his email address in his profile …</description>
		<content:encoded><![CDATA[<p>Alexandre Passant has a <a href="http://apassant.net/blog/2007/12/18/rdf-export-of-flickr-profiles-with-foaf-and-sioc/" rel="nofollow">quite complete Flickr-to-FOAF export service</a> that generates FOAF for all Flickr users. It dynamically generates a FOAF profile by interrogating the Flickr API for user details. And apparently, it always includes the SHA1, even if the user doesn&#8217;t show his email address in his profile …</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-547</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 24 Mar 2008 18:12:40 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-547</guid>
		<description>Yes, Flickr has switched totally over to Yahoo! IDs.

I can control who sees my photos in a fairly granular manner.  I should be able to control who sees my account info, yes?</description>
		<content:encoded><![CDATA[<p>Yes, Flickr has switched totally over to Yahoo! IDs.</p>
<p>I can control who sees my photos in a fairly granular manner.  I should be able to control who sees my account info, yes?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-545</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Mon, 24 Mar 2008 16:43:59 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-545</guid>
		<description>Cool that you asked this back then.

I came over to say what Dave said! Although the DataPortability group may not actually have achieved anything concrete yet, its mere existence suggests something of a sea change.

btw, doesn't Flickr now use Yahoo! IDs?</description>
		<content:encoded><![CDATA[<p>Cool that you asked this back then.</p>
<p>I came over to say what Dave said! Although the DataPortability group may not actually have achieved anything concrete yet, its mere existence suggests something of a sea change.</p>
<p>btw, doesn&#8217;t Flickr now use Yahoo! IDs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Eden</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-542</link>
		<dc:creator>Anthony Eden</dc:creator>
		<pubDate>Mon, 24 Mar 2008 10:40:52 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-542</guid>
		<description>Perhaps a new email to Flickr is warranted? As you've pointed out, it is possible to use an opt-in policy to improve the privacy aspects, so that's not much of reason. There's a growing push for data portability and it just seems logical that the owner of the email address should decide what they want to do with it.

Flickr used to innovate, but these days they seem to have stagnated quite a bit. They're still a useful service though.</description>
		<content:encoded><![CDATA[<p>Perhaps a new email to Flickr is warranted? As you&#8217;ve pointed out, it is possible to use an opt-in policy to improve the privacy aspects, so that&#8217;s not much of reason. There&#8217;s a growing push for data portability and it just seems logical that the owner of the email address should decide what they want to do with it.</p>
<p>Flickr used to innovate, but these days they seem to have stagnated quite a bit. They&#8217;re still a useful service though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-538</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 24 Mar 2008 02:40:09 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-538</guid>
		<description>No doubt 4 years ago was a long time.  I'd love to hear the official Flickr response to "when are you going to export FOAF?"</description>
		<content:encoded><![CDATA[<p>No doubt 4 years ago was a long time.  I&#8217;d love to hear the official Flickr response to &#8220;when are you going to export FOAF?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Beckett</title>
		<link>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-537</link>
		<dc:creator>Dave Beckett</dc:creator>
		<pubDate>Mon, 24 Mar 2008 00:10:51 +0000</pubDate>
		<guid>http://www.semergence.com/2008/03/23/why-flickr-doesnt-do-foaf/#comment-537</guid>
		<description>Four years ago is a lifetime in internet apps.  It's before Flickr was acquired and before OpenID, OpenAuth etc. so the landscape has changed.  But still, good reasons need to be given.</description>
		<content:encoded><![CDATA[<p>Four years ago is a lifetime in internet apps.  It&#8217;s before Flickr was acquired and before OpenID, OpenAuth etc. so the landscape has changed.  But still, good reasons need to be given.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
