<?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: The Mobile Search Opportunity, Turning PageRank into PlaceRank</title>
	<atom:link href="http://www.locationawhere.com/15/10/2008/commentary/mobile-search-opportunity-turning/feed" rel="self" type="application/rss+xml" />
	<link>http://www.locationawhere.com/15/10/2008/commentary/mobile-search-opportunity-turning</link>
	<description>Location Matters</description>
	<lastBuildDate>Mon, 26 Jul 2010 00:01:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Eric</title>
		<link>http://www.locationawhere.com/15/10/2008/commentary/mobile-search-opportunity-turning/comment-page-1#comment-27</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Thu, 16 Oct 2008 00:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.locationawhere.com/?p=88#comment-27</guid>
		<description>Thought-provoking post - I like how you illustrate the point of location awareness for both the &quot;consumer&quot; or &quot;searcher&quot; of information and of the source-data (such as the train, or people going to a bar after the game).  My company, BooRah, is looking at this in a similar way -- ultimately, there needs to be aggregation of the location-specific source-data in a format that&#039;s convenient for the location-specific users.  &lt;br/&gt;&lt;br/&gt;First, you can aggregate user-generated content about local places (in our case, restaurants and other local businesses that people frequent), with location and time-specific attributes (ie, a review about a place written on a certain date).  The aggregation of the overall social &quot;buzz&quot; of the place helps to determine it&#039;s popularity - not instantaneously, but over time.  Then, you add geo-aware user search functionality, to produce the most relevant results for the user (see blog.boorah.com for some of our recent announcements along these lines).  Lastly, you add &quot;instantaneous&quot; source-data information to the aggregation index, such as twitter tweets from people currently at these local places, that include opinions (ie, that it&#039;s actually a good place to be!) or reputations in addition to fact-based location information.</description>
		<content:encoded><![CDATA[<p>Thought-provoking post &#8211; I like how you illustrate the point of location awareness for both the &#8220;consumer&#8221; or &#8220;searcher&#8221; of information and of the source-data (such as the train, or people going to a bar after the game).  My company, BooRah, is looking at this in a similar way &#8212; ultimately, there needs to be aggregation of the location-specific source-data in a format that&#8217;s convenient for the location-specific users.  </p>
<p>First, you can aggregate user-generated content about local places (in our case, restaurants and other local businesses that people frequent), with location and time-specific attributes (ie, a review about a place written on a certain date).  The aggregation of the overall social &#8220;buzz&#8221; of the place helps to determine it&#8217;s popularity &#8211; not instantaneously, but over time.  Then, you add geo-aware user search functionality, to produce the most relevant results for the user (see blog.boorah.com for some of our recent announcements along these lines).  Lastly, you add &#8220;instantaneous&#8221; source-data information to the aggregation index, such as twitter tweets from people currently at these local places, that include opinions (ie, that it&#8217;s actually a good place to be!) or reputations in addition to fact-based location information.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
