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

RE: New URI scheme talk in RSS-land

From: Dare Obasanjo <dareo@microsoft.com>
Date: Fri, 5 Dec 2003 13:51:25 -0800
Message-ID: <830178CE7378FC40BC6F1DDADCFDD1D1D5178A@RED-MSG-31.redmond.corp.microsoft.com>
To: <algermissen@acm.org>, "Tim Bray" <tbray@textuality.com>
Cc: <www-tag@w3.org>

MIME type based dispatch doesn't work in this case because the browser dispatches the representation to the waiting client but not the URI. In this case the only thing of interest to the client is the URI so MIME type based dispatch does not solve this problem. That is the purpose of the analogy to the mailto: protocol. 
 
-- 
PITHY WORDS OF WISDOM
Blessed are the meek for they shall inherit the Earth, minus 40% inheritance tax. 

________________________________

From: www-tag-request@w3.org on behalf of Jan Algermissen
Sent: Fri 12/5/2003 1:45 PM
To: Tim Bray
Cc: 'www-tag@w3.org'
Subject: Re: New URI scheme talk in RSS-land




Tim Bray wrote:
>
> 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

Hmm...this confuses me - isnt't dispatching to the right application
one of the primary uses/purposes of mime-types?

> because the RSS client doesn't need the
> representation, it needs the URI.

What do you mean by "it needs the URI"?


Jan




--
Jan Algermissen                           http://www.topicmapping.com
Consultant & Programmer                   http://www.gooseworks.org
Received on Friday, 5 December 2003 16:53:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:23 GMT