Dave Winer: Also, I realize there's a need for a RSS module
for redirection. I noted that Jon Udell needed it, and that Rogers
Cadenhead needs it now. Not everyone can control their server
enough to program an HTTP-level redirect. Would someone like to
propose a module? It should be easy to program Radio to support it
and we can evangelize it to other aggregators. This could be a
first experience at really working together, with no flames. What
do you think? Is it time??
If Dave wants to see whether or not it will be possible to work
together, he certainly has found an interesting test to do it
on.
As Jon
Udell discovered, a solution already exists which is
simplicity onto itself. Channel
elements have an "about" element which specify where the rss
feed can be found. If present and different, then readers
should follow.
What makes this test case interesting is the namespace
that this attribute is defined in.
This should be interesting to watch.
Sam, your last sentence cracks me up. :)
An RSS-based redirect is better, because although some people can temp-redirect (302), much fewer can perm-redirect (301). An RSS-based redirect lets set the semantics to be a permanent move, which you can't really assume for a 302. IMHO.
Sam wants to use the rdf:about attribute on the channel item to redirect RSS feeds, but I doubt it will fly, for several reasons on both sides of the fence....
[more]
According to NewsMonster's blog, there's a minor problem with my feed. NewsMonster seems to want to render both the <content:encoded> and <xhtml:body> elements. At this point, I'd just as soon drop <content:encoded>. And I probably will....
Sam wants to use the rdf:about attribute on the channel item to redirect RSS feeds, but I doubt it will fly, for several reasons on both sides of the fence....