<?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: What REST is really about&#8230;</title>
	<atom:link href="http://crschmidt.net/blog/275/what-rest-is-really-about/feed/" rel="self" type="application/rss+xml" />
	<link>http://crschmidt.net/blog/275/what-rest-is-really-about/</link>
	<description>Ramblings of a GIS Hacker</description>
	<pubDate>Wed, 03 Dec 2008 21:45:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Tim Caro-Bruce</title>
		<link>http://crschmidt.net/blog/275/what-rest-is-really-about/#comment-18937</link>
		<dc:creator>Tim Caro-Bruce</dc:creator>
		<pubDate>Tue, 09 Oct 2007 18:01:51 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/275/what-rest-is-really-about/#comment-18937</guid>
		<description>Hear, hear.  At the GeoData BOF at FOSS4G2007, discussion centered around how to build a public geo data repository using the resources available to OSGeo.  

Many of the requirements for such a system started to sound like solved problems:  identifiers describing where data could be found (some sort of Uniform Resource Locator, perhaps?), distributed storage (like 10 million webservers?), and lastly, a Google-esque search over the data.  What if the Google for geographic data is...The Google?

It's understandable and necessary that old school GIS types get worked up about arcane projections and metadata specifications and so on.  But geo data isn't all that special -- as you say, what works well for the web will work for geo too.

One concern with having Google index the web's geo data is that they will never make their index available.  That's true, but perhaps there's the real opportunity for an OSGeo-backed initiative: a geo-centric crawling effort with a publicly accessible index.</description>
		<content:encoded><![CDATA[<p>Hear, hear.  At the GeoData BOF at FOSS4G2007, discussion centered around how to build a public geo data repository using the resources available to OSGeo.  </p>
<p>Many of the requirements for such a system started to sound like solved problems:  identifiers describing where data could be found (some sort of Uniform Resource Locator, perhaps?), distributed storage (like 10 million webservers?), and lastly, a Google-esque search over the data.  What if the Google for geographic data is&#8230;The Google?</p>
<p>It&#8217;s understandable and necessary that old school GIS types get worked up about arcane projections and metadata specifications and so on.  But geo data isn&#8217;t all that special &#8212; as you say, what works well for the web will work for geo too.</p>
<p>One concern with having Google index the web&#8217;s geo data is that they will never make their index available.  That&#8217;s true, but perhaps there&#8217;s the real opportunity for an OSGeo-backed initiative: a geo-centric crawling effort with a publicly accessible index.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
