<?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: SPARQL for Flickr: Picture the Possibilities</title>
	<atom:link href="http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/feed/" rel="self" type="application/rss+xml" />
	<link>http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/</link>
	<description>life snapshots</description>
	<lastBuildDate>Fri, 24 Jun 2011 17:13:04 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ~wingerz &#187; Text indexing and query in Boca</title>
		<link>http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/comment-page-1/#comment-4671</link>
		<dc:creator>~wingerz &#187; Text indexing and query in Boca</dc:creator>
		<pubDate>Tue, 06 Feb 2007 15:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/#comment-4671</guid>
		<description>[...] This powerful feature allows SPARQL-aware developers to roll their own APIs. It&#8217;s easy to whip up a search across the all literals for traditional text search behavior. With a little more work, you can craft more sophisticated searches, like one for authors of a paper that mentions a specific search term in the abstract (say, &#8220;march madness&#8221;). [...]</description>
		<content:encoded><![CDATA[<p>[...] This powerful feature allows SPARQL-aware developers to roll their own APIs. It&#8217;s easy to whip up a search across the all literals for traditional text search behavior. With a little more work, you can craft more sophisticated searches, like one for authors of a paper that mentions a specific search term in the abstract (say, &#8220;march madness&#8221;). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ~wingerz &#187; Thoughts on DSLR ownership</title>
		<link>http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/comment-page-1/#comment-3965</link>
		<dc:creator>~wingerz &#187; Thoughts on DSLR ownership</dc:creator>
		<pubDate>Sat, 27 Jan 2007 06:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/#comment-3965</guid>
		<description>[...] Post-processing takes time. I&#8217;ve been shooting in RAW and tweaking each image a bit before converting to JPEG. Also, I need to do a better job of keeping track of metadata so that later on I can export to RDF and query my images with SPARQL. [...]</description>
		<content:encoded><![CDATA[<p>[...] Post-processing takes time. I&#8217;ve been shooting in RAW and tweaking each image a bit before converting to JPEG. Also, I need to do a better job of keeping track of metadata so that later on I can export to RDF and query my images with SPARQL. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: inkel</title>
		<link>http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/comment-page-1/#comment-2054</link>
		<dc:creator>inkel</dc:creator>
		<pubDate>Tue, 19 Dec 2006 18:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/#comment-2054</guid>
		<description>I was wondering the same long time ago, and I even started to write some scripts that transform Flickr data into RDF (mostly for FOAF purposes). A SPARQL endpoint would be wonderful, lots of friends of mine love to take and search photos on Flickr, but as you&#039;ve said, it&#039;s quite difficult to find proper results.

In case you&#039;re interested, the rough english translation of my rants is in http://f14web.com.ar/inkel/2005/08/25/flickr2foaf.en.html

I&#039;m looking at Dan&#039;s link now, seems very interesting.</description>
		<content:encoded><![CDATA[<p>I was wondering the same long time ago, and I even started to write some scripts that transform Flickr data into RDF (mostly for FOAF purposes). A SPARQL endpoint would be wonderful, lots of friends of mine love to take and search photos on Flickr, but as you&#8217;ve said, it&#8217;s quite difficult to find proper results.</p>
<p>In case you&#8217;re interested, the rough english translation of my rants is in <a href="http://f14web.com.ar/inkel/2005/08/25/flickr2foaf.en.html" rel="nofollow">http://f14web.com.ar/inkel/2005/08/25/flickr2foaf.en.html</a></p>
<p>I&#8217;m looking at Dan&#8217;s link now, seems very interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wingerz</title>
		<link>http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/comment-page-1/#comment-2003</link>
		<dc:creator>wingerz</dc:creator>
		<pubDate>Sun, 17 Dec 2006 21:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/#comment-2003</guid>
		<description>Yes, I definitely agree that it would be costly and it probably wouldn&#039;t be practical to deploy a completely open SPARQL endpoint on any site. With keys you could restrict the number of requests over a given time period and track usage patterns. I&#039;m sure it would be valuable from a business standpoint, which could drive interest (and maybe result in more optimization research).

I&#039;m sure IBM won&#039;t complain if all of a sudden there is a huge need for server cycles - will be interesting to see whether exposing this sort of functionality is cost-effective. I guess that&#039;s part of our (the SW community&#039;s) job.

Will take a look at the link; it sounds very interesting.</description>
		<content:encoded><![CDATA[<p>Yes, I definitely agree that it would be costly and it probably wouldn&#8217;t be practical to deploy a completely open SPARQL endpoint on any site. With keys you could restrict the number of requests over a given time period and track usage patterns. I&#8217;m sure it would be valuable from a business standpoint, which could drive interest (and maybe result in more optimization research).</p>
<p>I&#8217;m sure IBM won&#8217;t complain if all of a sudden there is a huge need for server cycles &#8211; will be interesting to see whether exposing this sort of functionality is cost-effective. I guess that&#8217;s part of our (the SW community&#8217;s) job.</p>
<p>Will take a look at the link; it sounds very interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Brickley</title>
		<link>http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/comment-page-1/#comment-2000</link>
		<dc:creator>Dan Brickley</dc:creator>
		<pubDate>Sun, 17 Dec 2006 20:33:39 +0000</pubDate>
		<guid isPermaLink="false">http://wingerz.com/blog/2006/12/17/sparql-for-flickr-picture-the-possibilities/#comment-2000</guid>
		<description>Exposing an unconstrained SPARQL interface could be computationally rather costly. Especially if it got heavily used. But I think you&#039;re right in general: SPARQL over such photo data would be great. I started some experiments in this direction, but based around idea of doing it against a local cache of personal or group data, ... not against the entire mega dataset.

See http://spypixel.com/2006/kml/photos/about.html

This is currently built by taking results from Flickr API, and reshaping them to look like the results of SPARQL queries expressed in JSON. I want to move to using the Perl CPAN Net::Flickr::Backup libraries instead, ... but they don&#039;t yet run against a group pool. Have swapped mails with the module author. If you or anyone you know would be interested to push on this idea further, it could be a fun testbed to collaborate around...</description>
		<content:encoded><![CDATA[<p>Exposing an unconstrained SPARQL interface could be computationally rather costly. Especially if it got heavily used. But I think you&#8217;re right in general: SPARQL over such photo data would be great. I started some experiments in this direction, but based around idea of doing it against a local cache of personal or group data, &#8230; not against the entire mega dataset.</p>
<p>See <a href="http://spypixel.com/2006/kml/photos/about.html" rel="nofollow">http://spypixel.com/2006/kml/photos/about.html</a></p>
<p>This is currently built by taking results from Flickr API, and reshaping them to look like the results of SPARQL queries expressed in JSON. I want to move to using the Perl CPAN Net::Flickr::Backup libraries instead, &#8230; but they don&#8217;t yet run against a group pool. Have swapped mails with the module author. If you or anyone you know would be interested to push on this idea further, it could be a fun testbed to collaborate around&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.440 seconds -->

