REST recipe

From BitWorking:

"(...) To build a good REST service you need to answer the following questions:

1. What are the URIs?
2. What's the format?
3. What methods are supported at each URI?
4. What status codes could be returned?

And that's all there is to it. You don't believe me? Good, because it's not true. There's lots more to discuss, like compression, etags, caching, extensibility, idioms, and implementations. See you next month."