Richardson Maturity Model: steps toward the glory of REST
martinfowler.com
martinfowler.com
When you look at a wsdl file, it tells you both where the service is located, as well as the structure of the data that one must send to it. I haven't been able to find an equivalent for the second part in the REST world. Anyone know?
Ideally you would get different kinds of responses for the same resource by using the Accept header, so that browsers get text/html but your app gets application/xml or whatever you asked for. Unfortunately everyone seems to be following Rails' lead of just appending extensions onto the end of URLs — if you're lucky they'll use HATEOAS, but they usually just expect you to concatenate strings on your end using foreknowledge.