From cd08fdf8a954fd8ed0c33f385e6638eb314c05bb Mon Sep 17 00:00:00 2001 From: Wesley Moore Date: Mon, 15 Mar 2010 17:29:30 +1100 Subject: [PATCH] QA /technical/2008/05/death-to-the-feed-uri-scheme/ --- .../technical/2008/05/death-to-the-feed-uri-scheme.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/content/technical/2008/05/death-to-the-feed-uri-scheme.html b/content/technical/2008/05/death-to-the-feed-uri-scheme.html index c02ef15..6fc3e5c 100644 --- a/content/technical/2008/05/death-to-the-feed-uri-scheme.html +++ b/content/technical/2008/05/death-to-the-feed-uri-scheme.html @@ -2,13 +2,14 @@ Can people please stop using the pre-draft RFC. The reasoning behind the proposal was: -
...to provide a straightforward way for end users to subscribe to the data feed for a particular online resource while browsing the World Wide Web. The expectation is that clicking on a hyperlink that points at a "feed" URI will cause the Web browser to invoke the specified handler for the "feed" URI scheme which SHOULD provide the user with information about the data feed as well as the possess the ability to subscribe to the feed.
+> …to provide a straightforward way for end users to subscribe to the data feed for a particular online resource while browsing the World Wide Web. The expectation is that clicking on a hyperlink that points at a "feed" URI will cause the Web browser to invoke the specified handler for the "feed" URI scheme which SHOULD provide the user with information about the data feed as well as the possess the ability to subscribe to the feed. + +Fast forward to 2008 and all the major browsers have support for discovery of feeds specified by the link tag and a user interface to access them. Additionally they are able to auto-detect a feed when specified with the normal http URI scheme. With the built in support the browser is able to launch the appropriate feed reader on the system, be it within the browser or an external application. Thus removing the need for the URI to be specified with the 'feed:' scheme. -Fast forward to 2008 and all the major browsers have support for discovery of feeds specified by the link tag and a user interface to access them. Additionally they are able to auto-detect a feed when specified with the normal http URI scheme. With the built in support the browser is able to launch the appropriate feed reader on the system, be it within the browser or an external application; thus removing the need for the URI to be specified with the 'feed:' scheme. It seems use of the scheme really took off around the release of Safari 2, which included RSS support. When viewing a feed in Safari it presents the URI using the 'feed:' scheme, thus making its use highly visible. - + I understand that using the scheme makes it easy at an operating system level to associate a particular application with the scheme but it should be entirely internal an invisible to the user. The reasons its use irks me is when adding a feed to Google Reader its necessary to copy and paste the link and then remove the 'feed:' at the start. Additionally Firefox removes the colon from http, meaning that has to be replaced too. Okay so I'm lazy but all the hassle can be avoided by simply linking to the feed with the normal 'http:' scheme.