A bit about our Publishing API
When we first sat down to design the APIs for Blogware, we had to choose between adopting a pre-existing API and reinventing the wheel to suit our own purposes. Being the egostical geeks that we are, we desperately sought an excuse to reinvent the wheel, so we looked at all the existing APIs.
Our conclusion was simple. The world didn't really need YABA (Yet-Another-Blogging-API), in fact it could probably do with a few less. As a result, we decided that Blogware needed to conform to the existing status quo transparently. Our approach was straightforward - any application that was built to talk over XML-RPC to a blogging app like MoveableType, Radio, Blogger, etc. should be able to easily have a similar (or the same) conversation with Blogware.
So thats exactly what we built.
Today, we have a tool that is interoperable with all of the major desktop blogging tools from Zempt, w.Bloggar and BlogBuddy - no patches or upgrades required. Further, we also support interoperability with things that you wouldn't suspect we do, like Radio for instance. Blogware lets you mix and match what you use on the desktop to get to the result that you desire. For instance, you can use Blogware and w.Bloggar for your day-to-day entries but still do really cool dynamic pages using OPML and ActiveRenderer via Radio Userland. Heck, you could even upstream your posts from Blogger Pro if you really want.
Anyways, the point of all of this is to simply state that we have not, nor will we, created a standard in our own image just because we could. Application interoperability is a good thing for users. And what's good for users, is good for us.
Happy blogging.
See this post as it first appeared on Blogware.