I've hated being a USER of APIs built on frameworks that output multiple APIs, like SOAP/REST/XMLRPC all at once. You end up with unnatural APIs in the 'REST'

I've hated being a USER of APIs built on frameworks that output multiple APIs, like SOAP/REST/XMLRPC all at once. You end up with unnatural APIs in the 'REST' api. Don't get caught up in the details of 'rest', focus on developing the API for your users -- think about what Calls they need to make, make it simple, document it!, give examples, keep the output formats sane (xml and json are done easily now days), and you'll be miles ahead of most web services.