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."

Hypertext style guide

In my search for knowledge about the World Wide Web, HTTP and The REST architectural style, I found in the w3 site a good style guide by 'El viejo Tim'

URI, URN, URL, URC...

From W3C Note (http://www.w3.org/TR/uri-clarification/):

"The body of documents (RFCs, etc) covering URI architecture, syntax, registration, etc., spans both the classical and contemporary periods. People who are well-versed in URI matters tend to use "URL" and "URI" in ways that seem to be interchangable. Among these experts, this isn't a problem. But among the Internet community at large, it is. People are not convinced that URI and URL mean the same thing, in documents where they (apparently) do. When one sees an RFC that talks about URI schemes (e.g. [RFC 2396]), another that talks about URL schemes (e.g. [RFC 2717]), and yet another that talks of URN schemes ([RFC 2276]) it is natural to wonder what's the difference, and how they relate to one another. While RFC 2396 1.2 attempts to address the distinction between URIs, URLs and URNs, it has not been successful in clearing up the confusion."

More on the subject: http://www.w3.org/Addressing/