<?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: What a mess!</title>
	<atom:link href="http://federatedsearchblog.com/2010/01/29/what-a-mess/feed/" rel="self" type="application/rss+xml" />
	<link>http://federatedsearchblog.com/2010/01/29/what-a-mess/</link>
	<description>Covers topics related to federated search and the deep web</description>
	<lastBuildDate>Mon, 30 Jan 2012 05:01:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: EBSCO refuses to supply content to Ex Libris aggregated search &#171; Bibliographic Wilderness</title>
		<link>http://federatedsearchblog.com/2010/01/29/what-a-mess/comment-page-1/#comment-74404</link>
		<dc:creator>EBSCO refuses to supply content to Ex Libris aggregated search &#171; Bibliographic Wilderness</dc:creator>
		<pubDate>Sat, 22 Jan 2011 18:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/?p=1119#comment-74404</guid>
		<description>[...] other sources. That makes sense, because EBSCO is an aggregator, not an original publisher. However, we know that behind the scenes EBSCO is trying to get more and more publishers to give them exclusi..., such that publishers content won&#8217;t even be indexed anywhere but EBSCO.  The goal would seem [...]</description>
		<content:encoded><![CDATA[<p>[...] other sources. That makes sense, because EBSCO is an aggregator, not an original publisher. However, we know that behind the scenes EBSCO is trying to get more and more publishers to give them exclusi&#8230;, such that publishers content won&#8217;t even be indexed anywhere but EBSCO.  The goal would seem [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

