Auto-discovery of an OPML index
You (especially if your name is Chris Pirillo ;-) ) will be delighted to learn that there is now an OPML file containing details of all the feeds offered by Tapestry available here. This can be used by the RSS readers to alert you to new feeds, and allows for a more user-friendly subscription mechanism.
I’ve also been looking at adding some form of <link …> tag in order to help the reader programs auto-discover the listing (I struggled with this before). So I had a dig about, and came up with this posting from Adam Kalsey. It seems that Radio Userland uses this kind of thing for published subscriptions:
<link rel=”subscriptions” type=”text/x-opml” title=”Subscriptions” href=”http://radio.weblogs.com/0001015/gems/mySubscriptions.opml”>
However, I’m not entirely happy with describing this as ‘Subscriptions’, though. So I had a look at a reference for the link tag, and I found what I think suits my purposes best: index. So the Tapestry page now contains the following link tag:
<link rel=”index” type=”text/x-opml” title=”Index” href=”http://dwlt.net/tapestry/tapestry.opml” />
What do people think of this? Am I using this correctly? It seems to make the most sense in the context of Tapestry, and I imagine that there will be future requirements where people are offering multiple feeds from one place, so coming up with a standard for this is a Good Thing™. However, I’m happy to go with a consensus, so if the gurus and newsreader authors want to comment, let’s get something working.
Home
About
Writing
Subscribe
Contact
Archives
1 comment
cybarber wrote at 02:40 AM on 15 Oct 2003
Could you make the RSS-RDF files up to spec?
There is no date included among things and what about the guid element?
I would like to link to your OPML file for my experimental XSLT ATOMRSSfeedcombiner but your format is out of specification.
Cybarber