Lesson plan
REST
REST (Representational State Transfer) is a software architectural style that was created in 2000 to guide the development of the World Wide Web. REST is defined as a set of six constraints for the ideal architecture of a distributed, Internet-scale hypermedia system such as the Web: Client/Server, Stateless, Cache, Uniform Interface, Layered System, and Code on Demand. (See The six constraints, below.) The motivation for these six constraints is to grant the system desirable properties such as modularity, scalability, latency-reduction, security, and compatibility with legacy systems. (See Implied architectural properties.) REST has been used to create stateless, reliable, web-based applications. An application that adheres to the REST architectural constraints may be informally described as RESTful, although this term is more commonly associated with the design of HTTP-based APIs and what are widely considered best practices regarding the "commands" (HTTP methods) a resource responds to, while having little to do with REST as originally formulated—and is often even at odds with the concept.
Article summary
REST (Representational State Transfer) is a software architectural style that was created in 2000 to guide the development of the World Wide Web. REST is defined as a set of six constraints for the ideal architecture of a distributed, Internet-scale hypermedia system such as the Web: Client/Server, Stateless, Cache, Uniform Interface, Layered System, and Code on Demand. (See The six constraints, below.) The motivation for these six constraints is to grant the system desirable properties such as modularity, scalability, latency-reduction, security, and compatibility with legacy systems. (See Implied architectural properties.) REST has been used to create stateless, reliable, web-based applications. An application that adheres to the REST architectural constraints may be informally described as RESTful, although this term is more commonly associated with the design of HTTP-based APIs and what are widely considered best practices regarding the "commands" (HTTP methods) a resource responds to, while having little to do with REST as originally formulated—and is often even at odds with the concept.
Key claims
- date of death: 1999 — source: Wikipedia, revision 1353621950, retrieved 2026-10-20 · confidence 0.95
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- The record states that the date of death is "1999". What evidence would count against this claim?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
- Wikipedia, “REST”, revision 1353621950, retrieved 2026-10-20 https://en.wikipedia.org/w/index.php?oldid=1353621950
Key claims and bibliography are generated from the same tracked claims and sources as the article page.