REST or REpresentational State Transfer or RESTful doctrine was invented after the fact to describe what HTTP, the basic protocol of the public web, reducing its design features to a set of URI axioms.
 levels of REST
 narrow REST: HTTP
The W3C sought to get more protocols of that kind developed that would do more useful things and spread everywhere. What HTTP did right, per REST, was to reduce all complex acts the user could take to a very few verbs (GET, PUT, POST, DELETE).
 general REST: verb theory
The ECG and linguists later expanded on REST to advocate, in general, to limit verbs or at least use fewer verbs in user interfaces and protocols: pick a very few verbs that fit your application and make them do as much work as possible, appear as often as you can without overloading them to mean confusing things. Generally understood, this is obvious, but in practice it means expanding the list to more like what one would find in a general purpose programming language and set of protocols required for the infra trades: at least 30 to 50 verbs.
ECG observed that verb/noun/type stability can be seen in verb:patch, verb:lock, verb:redirect and even higher order social description, e.g. verb:troll and politics as usual verb/term/positioning. API design or URI axioms or any other verb:namespace. The Imagine Halifax control terms and eventually all ECG control terms reflect this view.
- "The REST camp claims that when choosing between two grammars, one with customizable verbs (methods) and nouns (UR(I|N|L)s), and the other with a small fixed number of general verbs but customizable nouns, either of the two grammars can express the same thing, but the second grammer has better adoption characteristics among a large group of uncoordinated actors." - Clay Shirky describing The Essence of REpresentational State Transfer
 programming languages
Given that a typical programming language contains about ten to fifty verbs, and that this is much less than the hundreds that exist in even a simple English defining vocabulary, or the thousands that exist in the language in general, programming might be seen as a simplification of natural language. If so, the ECG claims, REST is a simplification of programming.
 according to geeks...
According to the ECG it doesn't only limit verbs but separates verb/noun/type development into three different problems wherever possible. There are better URI axioms that require only operational distinctions.
 ...including GUI geeks
REST may have only peripheral importance to user interfaces, though trolls bitterly dispute that. The ECG for instance advocates eliminating bad spatial metaphor by sticking to the operational distinctions made in REST, e.g. using "get" instead of "go" on a search field, avoiding "move", etc. However, some of HTTP seems wrong given the experience of the web. The ECG analysis of prepositions and ECG naming conventions emphasize that "delete" should just be considered to be another "redirect", else it just creates "404" errors. See verb/noun/type for more on this debate.
 tactics (actions) and patterns (descriptions) learned
- optimizing linguistics, of which REST is an example, which generally advises reducing verbs into deep hierarchies
- Doctrine:troll which advises converging trollish with REST: put, get, post, delete, refresh, redirect, etc. mean the same as in HTTP! Some trolls seek to eventually speak directly to a web server and be understood without error. Rumours say this already happened. See troll ontology for more on the usefulness of REST to trolls.
- 4D capability lets one specify any object at-REST uniquely in all possible worlds. This relates the general principle or verb of rest with its meaning for humans