<?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 is an API?</title>
	<atom:link href="http://federatedsearchblog.com/2009/06/11/what-is-an-api/feed/" rel="self" type="application/rss+xml" />
	<link>http://federatedsearchblog.com/2009/06/11/what-is-an-api/</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: Andy</title>
		<link>http://federatedsearchblog.com/2009/06/11/what-is-an-api/comment-page-1/#comment-27719</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 12 Jun 2009 23:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/?p=592#comment-27719</guid>
		<description>Thanks so much for checking out the post and glad it was clear enough for &#039;non-tech&#039; types.</description>
		<content:encoded><![CDATA[<p>Thanks so much for checking out the post and glad it was clear enough for &#8216;non-tech&#8217; types.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Piotr</title>
		<link>http://federatedsearchblog.com/2009/06/11/what-is-an-api/comment-page-1/#comment-27659</link>
		<dc:creator>Piotr</dc:creator>
		<pubDate>Thu, 11 Jun 2009 15:34:45 +0000</pubDate>
		<guid isPermaLink="false">http://federatedsearchblog.com/?p=592#comment-27659</guid>
		<description>I&#039;ve been poking around a bit with using screen-scraped and API-accessible data to power federated search in museums. Nothing too big or robust -- just sketches really.
For example,
http://museumpipes.wordpress.com/2009/03/15/federated-search-through-pipes/</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been poking around a bit with using screen-scraped and API-accessible data to power federated search in museums. Nothing too big or robust &#8212; just sketches really.<br />
For example,<br />
<a href="http://museumpipes.wordpress.com/2009/03/15/federated-search-through-pipes/" rel="nofollow">http://museumpipes.wordpress.com/2009/03/15/federated-search-through-pipes/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

