Re: [syndication] Re: locating syndication feeds

[Morbus Iff <morbus@disobey.com>]

Mark,

I'd be interested to hear about your candidate for doing the below. Another 
thing too, for clarity wise, you'll talking about locating feeds *after 
finding a site you want a feed for* as opposed to locating a feed *amongst 
a large list of found feeds*.

> It should be syndication format-agnostic

How future forward and boringly backward should this be? Technically, any 
format could be syndicated - csv, pipe, and so on and so forth.

>* Futhermore, it should support the communication of multiple,
>  alternate feed formats for a particular resource

Agreed. Again, not knowing what your candidate is, I'm looking at 
everything as "something you can stick in an HTML page". The number one 
concern is this "something" has to be small and innocuous - majors aren't 
going to give up screen real estate for something that's still relatively 
small and unknown. I like the orange XML button myself - Mike Krus furthers 
it with a blue one (signifying a NiF.com version of the feed).

>* It should support discovery by both people who are browsing the
>  site (the 'find the feed for this page' scenario) and automated
>  processes (the 'syndication spider' and 'browser automatic feed
>  location' scenarios)

Good idea. Hmm. I wonder - has anyone ever tried to search for xml.gif via 
a search engine? If it could be formated in a way that the engines would 
pick it up (perhaps a more unique filename, alt tag formatting, or 
whatever, that'd be nifty too.

>* It should allow feeds to be sent to aggregators both on the client
>  machine, or located at an arbitrary URI on the network

So, clicking on this magic candidate would allow people to add it to their 
NiF.com listing, or via their localized Radio Userland / AmphetaDesk / 
Headline Viewer client? How will the candidate future save itself as new 
clients appear?

>* It should be easy to integrate the mechanism into already deployed
>  web browsers

Which means that it also has to fall under the Bobby disability guidelines.

>* It should not require the storage of state or preferences in a
>  centralized registry or location; the only participants in
>  interactions should be the server where the channel is hosted, the
>  browser, and the target aggregator (on the client or on the

Agreed.


--
Morbus Iff ( .sig on other machine. )
http://www.disobey.com/ && http://www.gamegrene.com/
"where's there's a will, there's a morbus ready to collect!"