<?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: Could foursquare empower people to break commercial advantage?</title>
	<atom:link href="http://citizensheep.com/blog/2009/11/24/could-foursquare-empower-people-to-break-commercial-advantage/feed/" rel="self" type="application/rss+xml" />
	<link>http://citizensheep.com/blog/2009/11/24/could-foursquare-empower-people-to-break-commercial-advantage/</link>
	<description>Michael Grimes lives in Birmingham (UK). This is his blog about anything that he fancies.</description>
	<lastBuildDate>Wed, 18 Apr 2012 15:50:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Michael</title>
		<link>http://citizensheep.com/blog/2009/11/24/could-foursquare-empower-people-to-break-commercial-advantage/comment-page-1/#comment-11890</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 02 Dec 2009 11:23:13 +0000</pubDate>
		<guid isPermaLink="false">http://citizensheep.com/blog/?p=1990#comment-11890</guid>
		<description>&lt;p&gt;PS: I didn&#039;t mean to suggest you were saying that we &lt;em&gt;should &lt;/em&gt;wait for a better solution!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>PS: I didn&#8217;t mean to suggest you were saying that we <em>should </em>wait for a better solution!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://citizensheep.com/blog/2009/11/24/could-foursquare-empower-people-to-break-commercial-advantage/comment-page-1/#comment-11889</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 02 Dec 2009 11:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://citizensheep.com/blog/?p=1990#comment-11889</guid>
		<description>&lt;p&gt;Adrian, I agree completely. But I do think we should be encouraging the use of these tools to leave this sort of information, rather than waiting for a better solution.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Adrian, I agree completely. But I do think we should be encouraging the use of these tools to leave this sort of information, rather than waiting for a better solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Short</title>
		<link>http://citizensheep.com/blog/2009/11/24/could-foursquare-empower-people-to-break-commercial-advantage/comment-page-1/#comment-11883</link>
		<dc:creator>Adrian Short</dc:creator>
		<pubDate>Wed, 02 Dec 2009 10:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://citizensheep.com/blog/?p=1990#comment-11883</guid>
		<description>While it might be a temporary solution and thus better than nothing, ultimately we want to move beyond proprietary services for urban annotation or any other type of content.

It&#039;s really just a content + metadata + search problem.

Your content about a place could be a blog post, tweet, Facebook status update, photo, Boo, or whatever.
The metadata needs to record the location and have the semantic that the content is &lt;em&gt;about&lt;/em&gt; the place, not simply recorded/posted &lt;em&gt;in&lt;/em&gt; the place.

After that it&#039;s just a case of having appropriate search tools that will pull up all the content tagged at that location. &lt;a href=&quot;http://blog.twitter.com/2009/11/think-globally-tweet-locally.html&quot; rel=&quot;nofollow&quot;&gt;Twitter&#039;s new geolocation API&lt;/a&gt; is a step forward and works with Foursquare and other location-based services.

An alternative approach that doesn&#039;t rely on accurately determining the user&#039;s location is to give every thing a unique ID (possibly a URI), make that ID readable visually and/or with a barcode/RFID and allow people to use that ID as metadata for content.

eg. this post is about http://things.demo/brindleyplace-atm</description>
		<content:encoded><![CDATA[<p>While it might be a temporary solution and thus better than nothing, ultimately we want to move beyond proprietary services for urban annotation or any other type of content.</p>
<p>It&#8217;s really just a content + metadata + search problem.</p>
<p>Your content about a place could be a blog post, tweet, Facebook status update, photo, Boo, or whatever.<br />
The metadata needs to record the location and have the semantic that the content is <em>about</em> the place, not simply recorded/posted <em>in</em> the place.</p>
<p>After that it&#8217;s just a case of having appropriate search tools that will pull up all the content tagged at that location. <a href="http://blog.twitter.com/2009/11/think-globally-tweet-locally.html" rel="nofollow">Twitter&#8217;s new geolocation API</a> is a step forward and works with Foursquare and other location-based services.</p>
<p>An alternative approach that doesn&#8217;t rely on accurately determining the user&#8217;s location is to give every thing a unique ID (possibly a URI), make that ID readable visually and/or with a barcode/RFID and allow people to use that ID as metadata for content.</p>
<p>eg. this post is about <a href="http://things.demo/brindleyplace-atm" rel="nofollow">http://things.demo/brindleyplace-atm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

