But as to feeds themselves doing redirection, that can do it right now. HTTP supports a whole range of robust status codes on a page. You can redirect, move temporarily, indicate dead, really dead and gone and a number of other choices. The problem is several of the RSS readers out there don’t pay attention to this.
So before we reinvent the wheel here, how about taking a look at the functionality already provided in the HTTP specs?
This is also where an RSS feed using RDF modularity could simply setup rdfs:seeAlso and other attributes. But hey, what do I know, I’m only suggesting people actually research the stuff…
]]>rdfs:seeAlso is a good start, but AFAIK it doesn’t offer any way to describe what’s at the other end of the seeAlso: is this pointing to the new location of the feed, or the FOAF file, or an RDFed manifest of other feeds from the site, or what?
]]>Yes, evangelizing the reader developers has been successful. Slowly but surely they’re getting up to speed on all this stuff. It takes time and most of them are doing it as an extension of their own needs. As a result some stuff is slow to improve. But they do generally want to get around to it.
If you want the sophistication of automatic stuff you’re definitely going to want to use a framework.
]]>