the fewer data formats that one has to use to consume your service, the better. i would advise going with REST + JSON, and i would emphasize that your API will

the fewer data formats that one has to use to consume your service, the better. i would advise going with REST + JSON, and i would emphasize that your API will live or die based on its documentation. here's a video i found useful that lays out the some basic considerations to keep in mind when designing your API: http://confreaks.net/videos/710-rubyconf2011-advanced-api-design-how-an-awesome-api-can-attract-friends-make-you-rich-and-change-the-world http://confreaks.net/videos/710-rubyconf2011-advanced-api-de...