Specifically what infrastructure? I could understand that there is some decent infrastructure reuse (caching, etc) but other than that there wouldn't be muchWell, it would be, from my point of view, because I can use the associated RSS infrastructure, most of which doesn't care how many modules we throw at it but chugs happily anyway.advantage.
Oh, I've got a ton of infrastructure:Parsers, aggregators, locators, scrapers, readers, cachers, tutorials, creators, databases, query systems, the list goes on and on. Why redo all of this for no good reason?
I sure don't want to.
I'm suggesting we use RSS as a starting point, and add to it. Obviously, itis not the end of the game.I just want to stay agnostic right now... I hear what you are saying but I think we should define requirements and if RSS looks good we can go with it. I just don't want to get into format wars until we know what we are building :)
Well, I thought we both knew what we're building... that's why we're having this discussion, no? And you also outlined the basic requirements before. It's not like you've invented this idea, as the subject line says, this is the next step for OCS. Folks know what we need, and I'm proposing an easy way to get at it.
-- [ "Aaron Swartz" ; <mailto:me@aaronsw.com> ; <http://www.aaronsw.com/> ]