I agree completely with the sentiment of this article (although the title is perhaps a bit overblown): you shouldn’t need a separate API—that’s what you’re existing URL structure should be.
I’m not entirely sure that content negotiation is the best way to go when it comes to serving up different representations: there’s a real value in being able to paste a URL into a browser window to get back a JSON or XML representation of a resource.
But this is spot-on about the ludicrous over-engineered complexity of most APIs. It’s ridiculous that I can enter a URL into a browser window to get an HTML representation of my latest tweets, but I have to sign up for an API key and jump through OAuth hoops, and agree to display the results in a specific way if I want to get a JSON representation of the same content. Ludicrous!
I was all set to bristle against an attack on the W3C from Alex …but when I actually read the post, I found it hard to disagree with. If anything, this shows just how much Alex cares about the W3C (probably more than most people).
The conversation in the comments is worth reading too.
Some musings from Norman Walsh. I have to say, I’m still not entirely sure why the HTML/XML Task Force exists. The “use cases” described here are vague and handwavey.
A first bash at describing how to write (X)HTML5 documents that can be parsed as XML as well as HTML.
You can know use an API (with BBAuth) to get contact Yahoo account contact details. There really is no excuse now for still using the password anti-pattern.
This is a good straightforward hands-on explanation of Ajax: succinct and clear.
The second part of Gareth's series for Digital Web on APIs. This time he's got some PHP code samples for parsing XML and JSON.
The website for the Fundamentos Web conference provided audio and video files but no RSS feed to enclose them so Nick Dunn has created one for us.
Great explanatory article by James Bennett comparing JSON and XML.
Dave Winer doesn't get JSON.
Simon St. Laurent writes about the victory of JSON over XML in the browser and looks forward to a future filled with XQuery.
Want to indicate that something is happening on a web page, like... oh, I don't know... an Ajax request or something? Here's a cornucopia of animated progress indicators.
My fellow Brightonian geek, Dom, has written an article about using Perl and Ajax.
"...it must degrade well. It must still be accessible. It must be usable. If not, it is a cool useless piece of rubbish for some or many people."
Who knew? The way I do my Ajax is a microformat. AHAH: Asynchronous HTML and HTTP.
Possible ideas for IE's icon for RSS feeds. I like number five.
A nice introduction the XMLHttpRequest object by Cameron Adams.
Weep not, Ethan! SVG lives... possibly in Safari and Dashboard.
An XML format from Google that describes the structure of websites. A semantic sitemap.
Tim Bray on the politics and practicalities of Web services.