<?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: RSS is an API for Content</title>
	<atom:link href="http://www.nivi.com/blog/article/rss-is-an-api-for-content/feed" rel="self" type="application/rss+xml" />
	<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content</link>
	<description>my personal blog</description>
	<lastBuildDate>Sun, 13 Dec 2009 19:02:35 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Victor Ganic</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-440085</link>
		<dc:creator>Victor Ganic</dc:creator>
		<pubDate>Sun, 13 Jan 2008 16:10:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-440085</guid>
		<description>&lt;p&gt;Greg G. makes a good point in post #4. RSS does not employ the granularity that is commonplace in a well targeted API. This does not always have to be the case; RSS &quot;overloaded&quot; with RDF syntax or additional (and permissible) markup. It has been done before in RSS 1.0, and it is being done now with RSS 2.0 with Dublin Core Metadata.&lt;/p&gt;

&lt;p&gt;RDX is an experimental example of this that, in theory, could provide site specific actions and/or information. Web forecasts have been excitedly predicting a future where websites have automated functionality. RDF is a proven way of integrating semantic technology into a site where other programs can understand it. This is, after all, one of the goals of using an API.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Greg G. makes a good point in post #4. RSS does not employ the granularity that is commonplace in a well targeted API. This does not always have to be the case; RSS &#8220;overloaded&#8221; with RDF syntax or additional (and permissible) markup. It has been done before in RSS 1.0, and it is being done now with RSS 2.0 with Dublin Core Metadata.</p>

<p>RDX is an experimental example of this that, in theory, could provide site specific actions and/or information. Web forecasts have been excitedly predicting a future where websites have automated functionality. RDF is a proven way of integrating semantic technology into a site where other programs can understand it. This is, after all, one of the goals of using an API.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Parisista</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1287</link>
		<dc:creator>Parisista</dc:creator>
		<pubDate>Thu, 08 Sep 2005 01:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1287</guid>
		<description></description>
		<content:encoded><![CDATA[<p><strong>RSS is a Data Model not an API</strong></p>

<p>Just saw Nivi&#8217;s post on RSS is an API. Agreed RSS gives you access to a web site’s data just like an API gives you access to a web site’s computing power. But, RSS is just the data model which encapsulates the bits and pieces of information in the for&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nollind Whachell</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1284</link>
		<dc:creator>Nollind Whachell</dc:creator>
		<pubDate>Thu, 08 Sep 2005 00:59:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1284</guid>
		<description>&lt;p&gt;Sorry error above, I meant to say &quot;obviously you can&#039;t see all of the readers comments&quot; in one feed.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sorry error above, I meant to say &#8220;obviously you can&#8217;t see all of the readers comments&#8221; in one feed.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Nollind Whachell</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1283</link>
		<dc:creator>Nollind Whachell</dc:creator>
		<pubDate>Thu, 08 Sep 2005 00:58:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1283</guid>
		<description>&lt;p&gt;Hyperlinks help us to see the relationships between communities but RSS/Feeds actually allow these communities to fully connect with one another.&lt;/p&gt;

&lt;p&gt;&quot;Fire Brown&quot; Community Aggregation&lt;/p&gt;

&lt;p&gt;For example, everyone is pissed off that FEMA Chief Michael Brown hasn&#039;t been fired yet. Well using a RSS feed aggregator, you could get a bunch of sites to setup a new blank blog with just one post on it entitled FIRE BROWN with a description saying add your name in the comments if you want Brown fired. Then you collect all of the comment RSS feeds from those various sites and aggregate them into one large feed using a web RSS aggregator like FeedDigest. Then grab the javascript for the aggregated feed and put that up on another page for people to view. There you go, now you&#039;ve got the collective people speaking.&lt;/p&gt;

&lt;p&gt;Now obviously you can see all of the readers comments at once due to the way feeds are displayed but I just found out today that FeedDigest does archive their full feeds and those feeds are searchable as well! It&#039;s too bad feeds are item limit because if they weren&#039;t then everyone could see the entire feed data and even more so they could distribute the full listing of names on any site!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hyperlinks help us to see the relationships between communities but RSS/Feeds actually allow these communities to fully connect with one another.</p>

<p>&#8220;Fire Brown&#8221; Community Aggregation</p>

<p>For example, everyone is pissed off that FEMA Chief Michael Brown hasn&#8217;t been fired yet. Well using a RSS feed aggregator, you could get a bunch of sites to setup a new blank blog with just one post on it entitled FIRE BROWN with a description saying add your name in the comments if you want Brown fired. Then you collect all of the comment RSS feeds from those various sites and aggregate them into one large feed using a web RSS aggregator like FeedDigest. Then grab the javascript for the aggregated feed and put that up on another page for people to view. There you go, now you&#8217;ve got the collective people speaking.</p>

<p>Now obviously you can see all of the readers comments at once due to the way feeds are displayed but I just found out today that FeedDigest does archive their full feeds and those feeds are searchable as well! It&#8217;s too bad feeds are item limit because if they weren&#8217;t then everyone could see the entire feed data and even more so they could distribute the full listing of names on any site!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Barnett blog</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1262</link>
		<dc:creator>Alex Barnett blog</dc:creator>
		<pubDate>Wed, 07 Sep 2005 06:47:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1262</guid>
		<description>&lt;p&gt;&lt;strong&gt;RSS is like an API for content&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Nivi:&lt;/p&gt;

&lt;p&gt;&quot;RSS is like an API for content. RSS gives you access
to a web siteâ€™s data just like an API...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>RSS is like an API for content</strong></p>

<p>Nivi:</p>

<p>&#8220;RSS is like an API for content. RSS gives you access
to a web siteâ€™s data just like an API&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Gershman</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1258</link>
		<dc:creator>Greg Gershman</dc:creator>
		<pubDate>Wed, 07 Sep 2005 04:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1258</guid>
		<description>&lt;p&gt;Is RSS an API, or more of a model of content?  I would view an API as the interface into a system, the parameters (or feeds) I need to know about in order to access the content.  RSS is, at its core, an abstraction of what a piece of web content is, which is why it works so well in so many cases.&lt;/p&gt;

&lt;p&gt;Incidentally, we built our search platform as an RSS-modeled API; Blogdigger&#039;s entire system and data store is accessible via RSS.  The API part comes in the form of the various ways of getting at the data (by keyword, site, links, location, media, etc.).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Is RSS an API, or more of a model of content?  I would view an API as the interface into a system, the parameters (or feeds) I need to know about in order to access the content.  RSS is, at its core, an abstraction of what a piece of web content is, which is why it works so well in so many cases.</p>

<p>Incidentally, we built our search platform as an RSS-modeled API; Blogdigger&#8217;s entire system and data store is accessible via RSS.  The API part comes in the form of the various ways of getting at the data (by keyword, site, links, location, media, etc.).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: SocialTwister</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1196</link>
		<dc:creator>SocialTwister</dc:creator>
		<pubDate>Tue, 06 Sep 2005 17:12:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1196</guid>
		<description>&lt;p&gt;&lt;strong&gt;RSS as API - Ideas Travel In Small Circles&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Last week I was meeting with my friends over at Corante. We were engaged in a day-long session on how we will be rolling out new technology and services to the public over the next few months. One of the...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>RSS as API &#8211; Ideas Travel In Small Circles</strong></p>

<p>Last week I was meeting with my friends over at Corante. We were engaged in a day-long session on how we will be rolling out new technology and services to the public over the next few months. One of the&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Roland Tanglao's Weblog</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1175</link>
		<dc:creator>Roland Tanglao's Weblog</dc:creator>
		<pubDate>Tue, 06 Sep 2005 06:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1175</guid>
		<description>&lt;p&gt;&lt;strong&gt;links for 2005-09-06&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Nivi : RSS is an API for Content Amen, a simple API that u don&#039;t have to be a programmer to play with! - &quot;Most important, RSS gives you access to your data that you have locked up on...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>links for 2005-09-06</strong></p>

<p>Nivi : RSS is an API for Content Amen, a simple API that u don&#8217;t have to be a programmer to play with! &#8211; &#8220;Most important, RSS gives you access to your data that you have locked up on&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: akimoto</title>
		<link>http://www.nivi.com/blog/article/rss-is-an-api-for-content/comment-page-1#comment-1152</link>
		<dc:creator>akimoto</dc:creator>
		<pubDate>Tue, 06 Sep 2005 02:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.nivi.com/blog/article/rss-is-an-api-for-content/#comment-1152</guid>
		<description>&lt;p&gt;Is not other user&#039;s reviews already available by Amazon Web Service 4.0? If so, converting them into RSS, if necessary, is not a big issue.&lt;/p&gt;

&lt;p&gt;I have not checked how Amazon made a deal with its customers about the re-distribution of those reviews.
(just because lazy to read it all)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Is not other user&#8217;s reviews already available by Amazon Web Service 4.0? If so, converting them into RSS, if necessary, is not a big issue.</p>

<p>I have not checked how Amazon made a deal with its customers about the re-distribution of those reviews.
(just because lazy to read it all)</p>]]></content:encoded>
	</item>
</channel>
</rss>
