<?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"
	>
<channel>
	<title>Comments on: Sometimes I wonder</title>
	<atom:link href="http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/feed/" rel="self" type="application/rss+xml" />
	<link>http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/</link>
	<description>Whatever it is, I'm against it!</description>
	<pubDate>Fri, 25 Jul 2008 20:45:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Niklas Derouche</title>
		<link>http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-13</link>
		<dc:creator>Niklas Derouche</dc:creator>
		<pubDate>Wed, 22 Aug 2007 11:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-13</guid>
		<description>I think that might take a lot more time than some. The problem being that there are still very few devices that actually support location on the device level, in most cases the information exist on the network level, in the hands of players that have failed to monetize the resource and are uninterested in letting anyone else do it.</description>
		<content:encoded><![CDATA[<p>I think that might take a lot more time than some. The problem being that there are still very few devices that actually support location on the device level, in most cases the information exist on the network level, in the hands of players that have failed to monetize the resource and are uninterested in letting anyone else do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrik Nilsson</title>
		<link>http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-12</link>
		<dc:creator>Patrik Nilsson</dc:creator>
		<pubDate>Wed, 22 Aug 2007 09:50:47 +0000</pubDate>
		<guid isPermaLink="false">http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-12</guid>
		<description>Mmm... it might take some time, but one important difference compared to identification systems is that there is no existing quagmire of messy location systems...</description>
		<content:encoded><![CDATA[<p>Mmm&#8230; it might take some time, but one important difference compared to identification systems is that there is no existing quagmire of messy location systems&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niklas Derouche</title>
		<link>http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-11</link>
		<dc:creator>Niklas Derouche</dc:creator>
		<pubDate>Wed, 22 Aug 2007 09:42:01 +0000</pubDate>
		<guid isPermaLink="false">http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-11</guid>
		<description>Agreed. But I think the odds of THAT infrastructure emerging by itself is rather slim. Even if the idea is good, it has taken damn near forever for some reasonably efficient identity management schemes to come out and we are still keeping track of who knows how many local username and password combinations anyway. But I certainly agree on the importance of location as a next step in service evolution.</description>
		<content:encoded><![CDATA[<p>Agreed. But I think the odds of THAT infrastructure emerging by itself is rather slim. Even if the idea is good, it has taken damn near forever for some reasonably efficient identity management schemes to come out and we are still keeping track of who knows how many local username and password combinations anyway. But I certainly agree on the importance of location as a next step in service evolution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrik Nilsson</title>
		<link>http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-10</link>
		<dc:creator>Patrik Nilsson</dc:creator>
		<pubDate>Wed, 22 Aug 2007 09:35:21 +0000</pubDate>
		<guid isPermaLink="false">http://bitpipe.wordpress.com/2007/08/22/sometimes-i-wonder/#comment-10</guid>
		<description>Let the location hardware, whatever it happens to be, feed a standards based location server/service. Then let that server/service be where you send the different services that take advantage of location data. Kind of like OpenID - you just provide your location service url. Access control to the data is handled there, once again based on standards, with time limited access, different levels of resolution on your location, etc.

Location will become a big thing in social networks when these kind of services show up. Matching your location with photos from, restaurant tips from, and physical interaction with close by people in your networks.

Patrik</description>
		<content:encoded><![CDATA[<p>Let the location hardware, whatever it happens to be, feed a standards based location server/service. Then let that server/service be where you send the different services that take advantage of location data. Kind of like OpenID - you just provide your location service url. Access control to the data is handled there, once again based on standards, with time limited access, different levels of resolution on your location, etc.</p>
<p>Location will become a big thing in social networks when these kind of services show up. Matching your location with photos from, restaurant tips from, and physical interaction with close by people in your networks.</p>
<p>Patrik</p>
]]></content:encoded>
	</item>
</channel>
</rss>
