Re: [syndication] XSL stylesheet for RSS (all versions)

["Mark Nottingham" <mnot@mnot.net>]

I think we can make it rewarding to type the data, by desiging
applications that take advantage of it (e.g., discovery through LINKs and
conneg, etc.).

The one thing that I found that *requires* a media type (and the reason
that I went down this path in the first place) is browser support for a
RSS aggregator - i.e., the user clicks on a link, the browser notes that
it's application/rss+xml, dispatches to a local app, which then sucks it
in / redirects it to a URI for processing. This is the only
aggregator-agnostic way to do subscription.

I'd do a demo, but my programming skills don't extend to desktop app sort
of things... Hmm, perhaps a little Python script...


----- Original Message -----
From: "Bill Kearney" <wkearney99@hotmail.com>
To: <syndication@yahoogroups.com>
Sent: Thursday, July 18, 2002 11:47 AM
Subject: Re: [syndication] XSL stylesheet for RSS (all versions)


> > Don't take this negatively, but that would be really silly.
> > A URI protocol for retrievable/modifiable items is the network
handshaking
> > to interact with the resource - and RSS resources just need GET, PUT,
> > DELETE - which are handled just fine by HTTP.
>
> Indeed, the HTTP transport does well handle the delivery of the RSS
documents.
> I'm not suggesting that change.  There is the possiblity of using other
> transports like the many freenets for RSS distribution as well.  Using
an rss://
> protocol handler would presume to impede their use as well.
>
> > You mentioned the need 'to prepend something on the URL to indicate
that it
> > needs to be parsed locally'
> > What did you mean by that - there may be something fishy going on or
maybe
> > something in HTTP that already does what you want.
>
> Herein lies one problem, the servers delivering the RSS documents
aren't,
> generally, doing much about content negotiaton or file typing.  It would
be a
> *great* thing to see them start doing it but it's not something well
implemented
> at the present time.  To get them to start doing this is going to be a
rather
> difficult task, especially without serious commitment on genuine content
type
> standardization.  As if it's not hard enough getting them to make
compliant XML,
> getting them to do content typing might seem like a lot to ask (with
little
> reward).
>
> -Bill Kearney
>
>
>
> Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
>
>