More Cooks in the Feed Stew Kitchen
I've talked before about why I like Atom. It's because it's the fixed point around which all the rest can crystallise...
One, that by using Atom as input format, you could simplify entry into this black-box system and use it, for example, on the receiving end of a UNIX pipe. Content on the source could be either straight Atom or come in some other form that would require transforming it into Atom, but that'd be easy to do, since transforming XML is pretty easy these days.
Two, that by using Atom as the output format you'd have the same flexibility. To generate a feed if you wanted, or transform it into something else, say, a weblog.
So, first I discover Urchin, and now I read this. I tell ya, this is an idea that's catching. Granted, Urchin's all about RSS, and atomflow and dbagg3 are all about Atom, but the spirit's the same:
Feeds go into a searchable stew, come back out as new synthetic feeds. What comes out looks like what goes in, and there's a well-defined spec behind it. Sprinkle in the elegance of loosely coupled UNIX pipelines and filters, REST interfaces, and XML tech like XSLT for munging, and you've got the makings of the next generation of syndication and XML feeds.
I guess maybe I should start checking into this Java stuff again, since smart guys like Diego and Matt are making noises I like, over in that sandbox. Well, at least I'll have things like Jython, Beanshell, and Groovy to toy with over there. And it's not like I haven't played with Java before.
So who else has something like this brewing?