Originally published on: 2/26/2006 7:41:18 PM
What gets called "documentation" varies quite a bit. There are usually several different types:
Unfortunately, the document that gets pointed to as the "API documentation" for the Metaweblog API is in the last category. It's a fine article, but as API documentation, it's really quite sad. I'm used to the detail that the PHP documentation has. When I'm busy implementing the spec, I need to know all of the details. I want to see examples.
For instance, when it tells me to pass in a "struct" without telling me the exact structure of that struct, it's a frustrating experience.
So, when looking for better docs, I noticed that the new MSN Spaces implementation happened to come with MSDN-style documentation and that Microsoft made a great move in choosing an open API (the same one I'm working with), but even better, they improved the documentation as they did it. I'm not generally a fan of Microsoft, but I'm also a pragmatist and tech agnostic and aim to use what works above any religious affiliation.
So, if you would like to understand the API or if you are Dave Winer and you're thinking of writing docs that will help people spread the standard you've come up with, go read theirs.