<?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: Hyatt Ponders RSSafari</title>
	<atom:link href="http://nslog.com/2003/01/26/hyatt_ponders_rssafari/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari</link>
	<description>The Weblog of Erik J. Barzeski</description>
	<pubDate>Wed, 07 Jan 2009 02:04:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: James</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-288</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 27 Jan 2003 22:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-288</guid>
		<description>a URL scheme is good, I like those. I hate when the URL scheme takes the form of a protocol scheme, like Apple did with iCal, webcal:// and remotely mounting a disk image, disk://.



My "browser" would understand the URL scheme rss: and do "smart" finding of the RSS feed by checking first to see if it is an rss file then checking the META tag in the file if option one fails, then falling back to common urls like /index.rdf and /index.xml.
</description>
		<content:encoded><![CDATA[<p>a URL scheme is good, I like those. I hate when the URL scheme takes the form of a protocol scheme, like Apple did with iCal, webcal:// and remotely mounting a disk image, disk://.</p>
<p>My "browser" would understand the URL scheme rss: and do "smart" finding of the RSS feed by checking first to see if it is an rss file then checking the META tag in the file if option one fails, then falling back to common urls like /index.rdf and /index.xml.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik J. Barzeski</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-287</link>
		<dc:creator>Erik J. Barzeski</dc:creator>
		<pubDate>Mon, 27 Jan 2003 15:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-287</guid>
		<description>I'm using the term "protocol" loosely here. rss: could be the same protocol underneath as HTTP (which it currently uses), but browsers could be built to understand that links with "rss://" should be passed to an RSS aggregator. That's all I meant. I should have written that more clearly.</description>
		<content:encoded><![CDATA[<p>I'm using the term "protocol" loosely here. rss: could be the same protocol underneath as HTTP (which it currently uses), but browsers could be built to understand that links with "rss://" should be passed to an RSS aggregator. That's all I meant. I should have written that more clearly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-286</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Mon, 27 Jan 2003 14:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-286</guid>
		<description>I would have thougth this would be best handled by Sherlock, both editing and updating</description>
		<content:encoded><![CDATA[<p>I would have thougth this would be best handled by Sherlock, both editing and updating</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-285</link>
		<dc:creator>Shawn</dc:creator>
		<pubDate>Mon, 27 Jan 2003 12:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-285</guid>
		<description>oh dear lord. the thought of nnw *fully* embeded in safari (or any browser) makes me sick.</description>
		<content:encoded><![CDATA[<p>oh dear lord. the thought of nnw *fully* embeded in safari (or any browser) makes me sick.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin A. Burton</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-284</link>
		<dc:creator>Kevin A. Burton</dc:creator>
		<pubDate>Mon, 27 Jan 2003 10:54:56 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-284</guid>
		<description>It isn't a protocol but a URL scheme and you are not the first person who thought of it :-)





From NSLog [1]

My own personal take: rss:// should be a protocol. NNW should grab an RSS link and add the subscription. Simple as that. It happens when I click an rtsp: (QuickTime) link. It happens when I click an aim: (AIM) link. It certainly happens when I click mailto: ftp: http: https: and others. It used to happen when I clicked gopher: links too :-).





In an older NewsMonster attempt at an aggregator in 100% JavaScript under

Mozilla (it was called Bonita) I wrote a view-rss: protocol adapter for Mozilla.



It did exactly this.  You put a URL such as 



view-rss:&lt;a href="http://www.peerfear.org/rss/"&gt;http://www.peerfear.org/rss/&lt;/a&gt;



And then you could view it, subscribe to it, etc.



It could also handle the application/rss+xml media type correctly.



Expect this code to be merged into a future version of NewsMonster.</description>
		<content:encoded><![CDATA[<p>It isn't a protocol but a URL scheme and you are not the first person who thought of it <img src='http://nslog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>From NSLog [1]</p>
<p>My own personal take: rss:// should be a protocol. NNW should grab an RSS link and add the subscription. Simple as that. It happens when I click an rtsp: (QuickTime) link. It happens when I click an aim: (AIM) link. It certainly happens when I click mailto: ftp: http: https: and others. It used to happen when I clicked gopher: links too :-).</p>
<p>In an older NewsMonster attempt at an aggregator in 100% JavaScript under</p>
<p>Mozilla (it was called Bonita) I wrote a view-rss: protocol adapter for Mozilla.</p>
<p>It did exactly this.  You put a URL such as </p>
<p>view-rss:<a href="http://www.peerfear.org/rss/">http://www.peerfear.org/rss/</a></p>
<p>And then you could view it, subscribe to it, etc.</p>
<p>It could also handle the application/rss+xml media type correctly.</p>
<p>Expect this code to be merged into a future version of NewsMonster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nate</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-283</link>
		<dc:creator>nate</dc:creator>
		<pubDate>Mon, 27 Jan 2003 05:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-283</guid>
		<description>I have to agree with James. RSS is just a file with yet another content-type, just like a PDF or an MPG or an MP3 -- doesn't need its own protocol, since it comes over http.</description>
		<content:encoded><![CDATA[<p>I have to agree with James. RSS is just a file with yet another content-type, just like a PDF or an MPG or an MP3 -- doesn't need its own protocol, since it comes over http.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://nslog.com/2003/01/26/hyatt_ponders_rssafari#comment-282</link>
		<dc:creator>James</dc:creator>
		<pubDate>Mon, 27 Jan 2003 05:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2003/01/26/hyatt_ponders_rssafari/#comment-282</guid>
		<description>Why should RSS get its own protocol, unless you want to write a new protocol to handle transfering of RSS HTTP works perfectly fine.</description>
		<content:encoded><![CDATA[<p>Why should RSS get its own protocol, unless you want to write a new protocol to handle transfering of RSS HTTP works perfectly fine.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
