While the rss/(n)echo debate rambles forward more users are getting involved. Over on the erosblog, Bacchus suggests I use my earmarked $10k to support Violet Blue's RDF, which stands for Real Doll Fantasy. If I can occupy the fourth slot, I might consider :)
6:14:43 PM
In an Open Letter, Steve Kirks writes from a user's perspective: "With the current fervor in the RSS/RDF/WTF groups, the average small business owner wouldn't dare take a chance on a technology investment like this. Imagine six months from now having to replace the software and lose communication with customers. That would give the perception that the *business owner* has a problem with *their* server. Who's going to push the compatible client out to all of the users. For free. And help install it. And answer their questions like: "It used to work before, why did it change?"
5:42:49 PM
Robert Service: "Be master of your petty annoyances and conserve your energies for the big, worthwhile things. It isn't the mountain ahead that wears you out - it's the grain of sand in your shoe."
12:39:02 PM
Marc Canter, a self proclaimed Adam Curry Watcher, takes a stab at answering my question: "Why do I need (n)echo?" Below are the answers with my (new) questions.
1. Semantic blogging. Please go check out what Matt and Paolo did with k-collector . But since it's not 'a standard' (or supported by Userland, Dave or you for that matter) - it went nowhere. With Echo - all blog posts can have topics attached to them.
Case in point, no marketing (and an ambiguous name). I had no idea k-collector was an attempt at a standard. I've looked at it before and couldn't find clear docs explaining what it does, but I presume it's a matching system for titles or posts in the form of 'topics'. is this project now dead? Sounds a bit like an automatic trackback. Perhaps that's why it wasn't adopted by the users.
2. Combine data structure and API into one thing. This will enable folks to move their blog info - from Radio (for instance) to Moveable Type or TypePad.
OK, makes sense, but what does the combination of data structure and API add to this that RSS doesn't already offer? Easier to move to another platform with rpc rather than 'import'? Not at the top of my list.
The most intriguing 'benefit'. How does that work?
I'm still open to being convinced about (n)echo's benefits to users, but am unable to find anyone who can explain this to me. I'd be happy with a side by side comparison of enclosures for rss and point (3) on Marc's list.
There are some good pointers and viewpoints in these comments as well.
11:20:04 AM
I've re-read my original stand on rss and want to retract my statement about not buying default placements where (n)echo is supported. It was written in anger and not thought through properly. It was rather childish and I'm sorry I wrote it. I hope this mea culpa will clear the air for any further rss/(n)echo debate.
12:48:34 AM
.
