The title makes me drowsy.
Kevin Burton of Tailrank has some good advice for Digg :

They’re basically reinventing RSS which just shouldn’t be done. The problem isn’t that Digg can’t do a good job inventing a new format - people already understand RSS. There are already tools that parse RSS and there are cool tools like the RSS validator which don’t work for Digg’s API (but would if they used RSS).

I thought I’d check the facts out first since Kevin could be considered a competitor. It’s definitely true that the marginal benefit they might receive from rolling their own XML is clearly not as great as the loss they will incur by not using RSS.

Kevin continues :

Want to see a good RSS API implementation? Check out Tailrank

Well, if you don’t say so yourself! ; )

But really, it’s true that Tailrank has done a fine job using it’s API with standards like REST and RSS to open it’s data up to the developer community.

It’s also nice to make xml-rpc available as an option for certain things or as an alternative.

I haven’t figured out why most REST advocates tend to think in nouns whereas remote procedures usually are verbs.

In his example, Kevin is using verb-like REST calls. So he is a rebel.

I don’t see any problem with it, but I’m open to be enlightened as to why it might be.

2 Comments »

Alex Barnett with a profusion of REST resources .

I’ve been working of some REST APIs lately and have to keep double-checking to make sure I’m not missing something. It’s that easy to implement.

I love xml-rpc, but this has it’s place as well.

REST is a great name for it, much better than “Shampoo”, which is what I would have called it, because it’s like. . . uh . . liquid SOAP .

No Comments »