<?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: SuperPages.com Trumpets LocalSearch.com Acquisition</title>
	<atom:link href="http://www.domainnamenews.com/editorial/superpagescom-trumpets-localsearchcom-acquisition/870/feed" rel="self" type="application/rss+xml" />
	<link>http://www.domainnamenews.com/editorial/superpagescom-trumpets-localsearchcom-acquisition/870</link>
	<description>News and Views from the Domain Name Industry</description>
	<lastBuildDate>Thu, 09 Feb 2012 18:26:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Domain Parking Shortcomings: Content &#187; Domain Name News</title>
		<link>http://www.domainnamenews.com/editorial/superpagescom-trumpets-localsearchcom-acquisition/870/comment-page-1#comment-9266</link>
		<dc:creator>Domain Parking Shortcomings: Content &#187; Domain Name News</dc:creator>
		<pubDate>Thu, 13 Sep 2007 00:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamenews.com/editorial/superpagescom-trumpets-localsearchcom-acquisition/870#comment-9266</guid>
		<description>[...] data on local domains, and even specifically mentioned where others could purchase local data. Heck SuperPages.com trumpeted their purchase of the LocalSearch.com domain. Why are parking companies just sitting around? Buying local business data may not make sense for [...]</description>
		<content:encoded><![CDATA[<p>[...] data on local domains, and even specifically mentioned where others could purchase local data. Heck SuperPages.com trumpeted their purchase of the LocalSearch.com domain. Why are parking companies just sitting around? Buying local business data may not make sense for [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

