<?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: Twitter uses WOEIDs &#8211; why you should care</title>
	<atom:link href="http://code.davidjanes.com/blog/2009/11/14/twitter-use-woeids/feed/" rel="self" type="application/rss+xml" />
	<link>http://code.davidjanes.com/blog/2009/11/14/twitter-use-woeids/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 12 Jul 2010 16:41:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Janes</title>
		<link>http://code.davidjanes.com/blog/2009/11/14/twitter-use-woeids/comment-page-1/#comment-7577</link>
		<dc:creator>David Janes</dc:creator>
		<pubDate>Mon, 16 Nov 2009 14:28:38 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=608#comment-7577</guid>
		<description>The WOEIDs for everything is certainly tying into a lot of things I&#039;ve been thinking about recently, especially with regards to OpenData and cities. It would be nice if there was a standard way that cities (etc) could grab a million WOEIDs and define them in a standard way for property lines, municipal areas, etc. so now everyone has a common vocabulary/IDs for talking about places. Sort of a Google Transit-like idea, but for identifying places in cities. Then of course we have to consider issues such as what&#039;s the relationship of a business to it&#039;s property lines, businesses opening and closing, and so forth. Or am I reading to much into this?</description>
		<content:encoded><![CDATA[<p>The WOEIDs for everything is certainly tying into a lot of things I&#8217;ve been thinking about recently, especially with regards to OpenData and cities. It would be nice if there was a standard way that cities (etc) could grab a million WOEIDs and define them in a standard way for property lines, municipal areas, etc. so now everyone has a common vocabulary/IDs for talking about places. Sort of a Google Transit-like idea, but for identifying places in cities. Then of course we have to consider issues such as what&#8217;s the relationship of a business to it&#8217;s property lines, businesses opening and closing, and so forth. Or am I reading to much into this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Gale</title>
		<link>http://code.davidjanes.com/blog/2009/11/14/twitter-use-woeids/comment-page-1/#comment-7502</link>
		<dc:creator>Gary Gale</dc:creator>
		<pubDate>Sat, 14 Nov 2009 11:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://code.davidjanes.com/blog/?p=608#comment-7502</guid>
		<description>Thanks for the post David; we think this is a significant announcement on the part of Twitter and we&#039;re really happy to see any and all uses of WOEIDs. When it comes to &quot;dynamically/crowd defined&quot; WOEIDs ... that needs a publicly accessible way to create and manage WOEIDs. We don&#039;t have such an API platform ... yet. But watch out for announcements on this towards the middle of next year.</description>
		<content:encoded><![CDATA[<p>Thanks for the post David; we think this is a significant announcement on the part of Twitter and we&#8217;re really happy to see any and all uses of WOEIDs. When it comes to &#8220;dynamically/crowd defined&#8221; WOEIDs &#8230; that needs a publicly accessible way to create and manage WOEIDs. We don&#8217;t have such an API platform &#8230; yet. But watch out for announcements on this towards the middle of next year.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
