<?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: 1 2 3 4 5 6 7 8 9 10 11 12</title>
	<atom:link href="http://www.jasonbirch.com/nodes/2009/10/21/382/1-2-3-4-5-6-7-8-9-10-11-12/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jasonbirch.com/nodes/2009/10/21/382/1-2-3-4-5-6-7-8-9-10-11-12/</link>
	<description>...Jason Birch's geospatial ramblings</description>
	<lastBuildDate>Thu, 21 Jul 2011 11:23:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Jason Birch</title>
		<link>http://www.jasonbirch.com/nodes/2009/10/21/382/1-2-3-4-5-6-7-8-9-10-11-12/comment-page-1/#comment-67208</link>
		<dc:creator>Jason Birch</dc:creator>
		<pubDate>Thu, 22 Oct 2009 15:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasonbirch.com/nodes/?p=382#comment-67208</guid>
		<description>I did make a distinction between the walled gardens (the actual SERPs within Google Maps: Place Pages and Real Estate results) and hosting the content on Google properties.  It&#039;s a fairly fine distinction though.  

Just because there&#039;s an API doesn&#039;t mean that the data is truly on the web or, in other words, just because a garden has a gate doesn&#039;t mean the walls are less effective.  Google could put up a toll-booth or an immigration check-point at any time.  For instance, in the early days of Yahoo Pipes, Google Base access disappeared suddenly.  This was likely due to load issues, but nothing would prevent similar actions from being taken for competitive reasons.

As far as not preventing sites from hosting their own feeds, Google needs to do better than that.  By providing a strong incentive to use a closed infrastructure, Google carries a large enough carrot to strongly affect the behaviour of effort-optimizing small businesses.  If a realtor (or a real estate service firm like Canada Placemarks) has limited resources and only sees benefit (SERP position) from publishing to a closed system then they&#039;ll publish to the closed system, whether it&#039;s a semi-open system like Base or a less-open system like My Maps.

I think it makes business sense for Google to use My Maps and Base (and YouTube, and Picassa, and...) to host data that can be served in SERPs.  Heck, until recently I was advocating that Google use this approach. It&#039;s easier to manage, and it gives Google a competitive advantage in delivering relevant results.  I&#039;m just concerned that this strategy is warping the web.</description>
		<content:encoded><![CDATA[<p>I did make a distinction between the walled gardens (the actual SERPs within Google Maps: Place Pages and Real Estate results) and hosting the content on Google properties.  It&#8217;s a fairly fine distinction though.  </p>
<p>Just because there&#8217;s an API doesn&#8217;t mean that the data is truly on the web or, in other words, just because a garden has a gate doesn&#8217;t mean the walls are less effective.  Google could put up a toll-booth or an immigration check-point at any time.  For instance, in the early days of Yahoo Pipes, Google Base access disappeared suddenly.  This was likely due to load issues, but nothing would prevent similar actions from being taken for competitive reasons.</p>
<p>As far as not preventing sites from hosting their own feeds, Google needs to do better than that.  By providing a strong incentive to use a closed infrastructure, Google carries a large enough carrot to strongly affect the behaviour of effort-optimizing small businesses.  If a realtor (or a real estate service firm like Canada Placemarks) has limited resources and only sees benefit (SERP position) from publishing to a closed system then they&#8217;ll publish to the closed system, whether it&#8217;s a semi-open system like Base or a less-open system like My Maps.</p>
<p>I think it makes business sense for Google to use My Maps and Base (and YouTube, and Picassa, and&#8230;) to host data that can be served in SERPs.  Heck, until recently I was advocating that Google use this approach. It&#8217;s easier to manage, and it gives Google a competitive advantage in delivering relevant results.  I&#8217;m just concerned that this strategy is warping the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mano Marks</title>
		<link>http://www.jasonbirch.com/nodes/2009/10/21/382/1-2-3-4-5-6-7-8-9-10-11-12/comment-page-1/#comment-67207</link>
		<dc:creator>Mano Marks</dc:creator>
		<pubDate>Thu, 22 Oct 2009 12:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasonbirch.com/nodes/?p=382#comment-67207</guid>
		<description>To be fair, your Base example isn&#039;t exactly a walled garden. Anything uploaded to Base can be accessed as a GeoRSS feed, and there&#039;s nothing to prevent the sites from hosting their own feed as well.</description>
		<content:encoded><![CDATA[<p>To be fair, your Base example isn&#8217;t exactly a walled garden. Anything uploaded to Base can be accessed as a GeoRSS feed, and there&#8217;s nothing to prevent the sites from hosting their own feed as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

