Boosted: Should we rebrand REST?
In this blogpost I argue the case for consigning the term "REST API" to history. In its place we should adopt the terms "HTTP API" and "hypermedia API", which better differentiate two distinctive design conventions for the programmatic interfaces of web services.
Fielding's thesis was a kind of retrospective on the design decisions that led to the World Wide Web — a distributed hypermedia-driven information retrieval system — becoming the runaway success it was.
I've read about Fielding's REST dissertation (never actually read the dissertation itself), but this is an interesting way to think about it. I've tried to explain the ideas behind REST to colleagues before, but I don't think I've ever been successful. Describing it with the Web as an example of the architecture makes it much more tangible.