DRSS?. On the OT list, folks have been ranting about RSS. I think what they're ranting about is the way that the various idiosyncrasies of blogs' RSS feeds box them into a corner, in various ways.
The more I think about it, the more I think that the one-RSS-endpoint-per-blog model is just not right. In my limited experience, I've encountered at least 3 different dimensions to RSS:
1) Version: 0.91, 1.0, 2.0, etc.
2) Category: All, technical-only, personal-only, etc.
3) Fidelity: Full content, summaries and links, etc.
Just considering those options, I'd have to expose 3x3x2=18 different RSS endpoints, to satisfy my readers. And that number would grow, as new versions of RSS emerge, or I define new categories, or...
This is madness. RSS is almost always dynamially-generated anyway -- why not generate it in whatever specific format the clients request?
http://www.myblog.com/rss.aspx?version=2.0&;category=technical&fidelity=full
Such a "DRSS" (think: DHTML) scheme would also allow RSS providers to punt questions like "how many items, or how far back into the past, should my feed expose?" back to the readers.
http://www.myblog.com/rss.aspx?version=2.0&;category=technical&fidelity=full&numitems=15
To be sure, a lot of folks are already doing things like this to manage the versioning-madness that is RSS. I'd love to see this convention grow to include support for filtering on categories, fidelity, and history.
[.NET Weblogs]
This is a great idea. If I had time, I would try to cobble together my own blogging platform but I do not have enough... Maybe the next version of Radio could implement this...
10:46:28 AM  - See Also: RSS Metadata Radio
|
