I agree with your comment, but this is a big impediment for a lot of developers. I think it's partly conceptual. SOAP libraries will grab a wsdl file and genera

I agree with your comment, but this is a big impediment for a lot of developers. I think it's partly conceptual. SOAP libraries will grab a wsdl file and generate a class with methods for each procedure the service exposes. That makes a lot of developers think something has been made easy for them, but they still have to understand the class interface to know how to talk to the service. REST is the same; you have to understand the interface (resource representations) to know how to talk to the service. REST just skips that middle code generation part where you tightly couple your code to a particular version of the service api. The developers who are looking for a library just want the code generation. I tell people that they've already got the communication stack in place and don't need code generation; what they need is to understand the api and design the classes on their side that will _use_ the api. The http and json stuff gets buried there, not in a client-side facade class.