In what do consist the misunderstandings about the "REST" word and its meaning
<p>It is not always easy to figure out what is really a RESTful application and/or api, because there is a sort of misunderstanding about the REpresentational State Transfer architectural style meaning and scopes.</p>
<p>Initially, I was quite in trouble with what, the adjective &quot;REpresentational&quot; of the acronym REST, referred to. This was because &quot;representational state&quot; sounded to me not so well...</p>
<p>Further, I was impressed also by a <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven" rel="nofollow noreferrer">blog post</a> of the author of this architectural style, Roy Fielding, where he is a lot disappointed about the frequent misunderstanding that api based on http verbs are RESTful, in particular he complaints about the coupling among client and server of these api regarding their names and data structures.</p>
<p>I want to try to give only a theoric explanation about REST arch. style and I'd like to know other points of view.</p>