From Ajax Patterns
You say in your text: "REST is a standard which addresses these concerns. Just about any collection of services can be presented as a RESTful API, and by doing so, it gains the advantage of a familiar, intuitive, style."
According to the link that you provide  REST is not a standard but an architecural style. Quotes from the xfront site: "REST is not a standard. You will not see the W3C putting out a REST specification. You will not see IBM or Microsoft or Sun selling a REST developer's toolkit. Why? Because REST is just an architectural style. You can't bottle up that style."
The standards used HTTP, URL, XML/HTML/GIF/JPEG/etc (Resource Representations), text/xml, text/html, image/gif, image/jpeg, etc (MIME Types)
Thanks for pointing it out. I stand corrected, bad choice of wording. User:Mahemoff
--- Couldn't find any mention in the article, but RESTful services should not perform data modification based purely on GET requests. Should such a request be embedded in the HREF of a standard HTML anchor tag, there is the potential of "friendly fire" by browser or proxy pre-fetching, search bots, etc. --RichardTallent