Most people are doing RPC-on-HTTP and call it REST, probably for the better in many ways. I personally believe that the Verb/Noun/Resource part of rest is perf

Most people are doing RPC-on-HTTP and call it REST, probably for the better in many ways. I personally believe that the Verb/Noun/Resource part of rest is perfectly avoidable, while I believe that including URLs/URLs fragment/URLs-like object in responses is good. HTTP is a very complex message passing transport layer, API should separately use the platform (HTTP caches/proxies/verbs/headers) and its main messaging feature (URL + body); so just set the right headers and verbs (GET/POST are enough) and pipe JSON/whatever around (obviously this is for APIs, websites need to use the WWW/HTTP/HTML platform, not just the HTTP platform)