RDF-REST
A Unifying Framework for
Web APIs and Linked Data
Q&R 2013 - 2nd july
Outline
- History and Rationale
- Design
- Benefits
- Perspectives
A kernel for trace-based systems (kTBS)
Use HTTP (and linked data)
Use it the right way
REST
- REpresentational State Transfer
- Roy Fielding's thesis (2000)
- architectural style of the Web
REST constraints
- client-server
- stateless
- cache
- uniform interface
- layered system
- code on demand (optional)
Impedance mismatch
- OO
- differentiation through interface
- REST
- uniform interface
- differentiation through representations
Uniform interface (rings any bell?)
RDF-REST interface
Use HTTP verbs as methods
- reduces impedance mismatch
- encourages RESTful design
Use RDF graphs as representations
- flexible and unambiguous (URIs)
- encourages linked data
Linked Data Platform (LDP)
Conclusion
- architecture encouraging software quality of REST services
- including linked data services
- possibly LDP services
- available implementation
Many thanks to
- Olivier Aubert
- Françoise Conil
- Amélie Cordier
- Lionel Medini
- Erik Wilde
- Mike Amundsen
- probably many others...