Common Rest Design Pattern
Resource-Method-Representation

Why
If we think about URLs as being only nouns, no verbs, then we
end up with a URL for every important thing in our site. Those
URLs can then be bookmarked and linked easily. We can change
code behind the scenes without changing the URLs as the URLs
refer to objects that don't change rather than functions that
do.
The model is inherently object-oriented, with every object (at
least those of meaning to the outside world) having a URI and
every object responding to the standard HTTP verbs, GET, PUT,
POST, DELETE. This is object-orientation at the level of the
web, not at the level of a server-side language. That's a very
different thing to what JSP does, where internally the
server-side code may be object-oriented, but the URIs refer to
verbs, so look more procedural or perhaps functional.
The above is from Rob Styles from
Talis You need to read the whole article!
http://architects.dzone.com/news/common-rest-design-pattern
Paul Sadauskas on
RESTful services (very good)