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

RE: New URI scheme talk in RSS-land

From: Michael Mealling <michael@neonym.net>
Date: 06 Dec 2003 14:21:32 -0500
To: Dare Obasanjo <dareo@microsoft.com>
Cc: Dan Brickley <danbri@w3.org>, Tim Bray <tbray@textuality.com>, "www-tag @ w3. org" <www-tag@w3.org>
Message-Id: <1070738491.24465.507.camel@blackdell.neonym.net>

On Sat, 2003-12-06 at 13:09, Dare Obasanjo wrote:
> If we have a MIME type that always involves invoking a separate application
> when a user clicks on a feed how does one perform HTTP GETs on the feed to
> view the XML content in their browser then? So does this mean servers have
> to use separate MIME types for the same file or that the assumption is that no one will ever want to click on a feed and see the actual content in their web browser? Both seem like gross hacks to me. 

Whether or not invoking a separate application is the appropriate action
is left to the application developer. It seems what you are after is an
explicit statement that some information bundle describes what is
necessary for a client application to successfully 'subscribe' to a feed
(irregardless of whether or not that is a push or pull operation). This
information bundle is separate from the bundle that is the actual
content of the feed.

IMHO, RSS (and all syndication methods) seem to be simple examples of
what some call web services, albeit a very RESTful one. Complete with
the probably requirement that multiple message patterns be available
(i.e. there is an app for subscribing to an RSS feed via jabber where
the jabber server converts a pull method to push via IM).

With all of the changes coming about with syndication and the forms its
taking, I would think something like WSDL for syndication with its own
MIME type and then using HTTP URIs to get that particular mime type
would be a) sufficient and b) much more powerful.

In many cases when I would see a 'feed:' URI I would not want to
immediately subscribe to it. I would rather have more information about
the feed (prefered update rate, namespace version, payment information,
etc) first. The action of subscribing to it is something that I as the
user initiate based on that packet of information that describes the
feed.

> Then again I don't have the "HTTP URIs can solve every problem" religion so
> this may just be a problem with me. 

Neither do I. But I also think that having to many URI schemes is also a
bad thing, especially when a better solution exists....

-MM
Received on Saturday, 6 December 2003 14:24:16 GMT

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