W3C home > Mailing lists > Public > www-tag@w3.org > December 2003

RE: New URI scheme talk in RSS-land

From: Bullard, Claude L (Len) <clbullar@ingr.com>
Date: Fri, 5 Dec 2003 15:27:50 -0600
Message-ID: <15725CF6AFE2F34DB8A5B4770B7334EE03F9F018@hq1.pcmail.ingr.com>
To: 'Tim Bray' <tbray@textuality.com>, "'www-tag@w3.org'" <www-tag@w3.org>

Doesn't that conflate the role of the URI as an 
identifier and its role as a data value to a 
control?  Couldn't they do this by implementing 
a GUI control with event logic?  Why should 
browser vendors implement yetAnotherURIasClickEvent?


From: Tim Bray [mailto:tbray@textuality.com]

RSS feeds are ordinary web resources and have ordinary URIs.  For 
example: http://www.tbray.org/ongoing/ongoing.rss is one, and as the 
scheme suggests, is typically fetched via HTTP and there's lots of 
scope for caching and all the usual helpful HTTP machinery.  However, 
there's a lot of talk in the RSS community recently about wanting a new 
URI scheme, e.g. feed://www.tbray.org/ongoing/ongoing.rss.  The reason 
is that they want to be able to click on one of these things and wake 
up the RSS client to read it and potentially subscribe.  You really 
can't do this with MIME types because the RSS client doesn't need the 
representation, it needs the URI.

Once you've got a new scheme, in popular operating systems it's 
straightforward to cause them to be handed to an app of your choice 
when clicked on.

In general it seems nuts to create a new scheme for URIs that describe 
ordinary HTTP-accessible web resources, but I don't see any other 
obviously-good solutions.
Received on Friday, 5 December 2003 16:27:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:40 UTC