But today, for my rss feeds importing and exporting needs, OPML far outshines xoxo.Source: XOXO vs. OPML at DLTQ.org
Yes, there are 6 XOXO outlines on my front page. There are six lists. But I don’t have an easy way to import one of those XOXO outlines in my FeedDemon application in order to receive the latest blog items from those blogs that I link to. If there IS an easy way to do it, please enlighten me.
Ah hah. Here's a use case where I agree OPML has undeniably become king: Exporting and importing feed aggregator subscriptions.
Because Radio UserLand was the first aggregator to really take off—and because OPML is Radio's lingua franca, any new aggregators have needed to speak OPML to facilitate migration. It grew from there, with nearly every aggregator supporting some basic form of OPML import/export for subscription lists. OPML has won the "feed subscription list format war" before there was ever a notion that there might be such a war.
Now, I'm woefully behind on all the buzz connecting OPML with attention. But, my impression so far is that people want to share their subscription list, exported from their aggregator of choice. That comes out as OPML. So then, the reasoning is that because aggregators produce OPML, and aggregators are powerful attention managers, OPML is the lingua franca of attention. Is this about right?
I guess where I go from there is with this: My aggregator's OPML export is private data for interchange between my other aggregators. Today, I'm about as comfortable with sharing my OPML with you as I am sharing QIF files exported from my bank account. Sure, it's an easy export process, but it's not meant for you.
In my OPML, I've got subscriptions that I've paid for, that I've password protected, and that give me details derived from my server logs. I don't want to share that, at least not directly. I've been asked for my OPML by a few people so far, and every time, I need to dig through it and be sure I'm not giving away any secrets. Maybe this is where I'm a bit confused about the attention hype.
*You see, what I do want to share is called a blogroll.* Blogrolls are public declarations of attention, published on blogs.
Since revamping this blog, I haven't yet gotten around to throwing a proper blogroll together, but I'm planning on it. And, when I do share it, it'll be in HTML list form. And when I build it, it may start as an OPML export from my aggregator, but I'll have to spend some time weeding through it.
I guess I don't have a clear picture here yet, but directly shipping around exports from my aggregator subscriptions gives me the willies. And further, basing anything big on OPML gives me the willies too.
Nowadays, sharing things on the web feels like XHTML and microformats to me. OPML for interchange between aggregators is one thing—but on the web at large, sinking deeper roots into OPML and the whole Rube Goldberg array of machinery following behind it feels like a backward step to me.
Maybe microformats are the new XML-geekery, but I don't want a new, "cleaner" XML format—I just want to more cleverly use the format that everyone's been using to share outlines and declarations of attention in blogs.