W3C-LINKED-DATA-PLATFORM
W3C LDP Linked Data Platform CRUD HTTP API.
Definition
LDP concepts: (1) LDP Resource (LDPR): RDF resource represented via HTTP Content-Type application/rdf+xml / text/turtle / application/ld+json / application/n-triples ; CRUD via HTTP GET (retrieve), PUT (update), DELETE. (2) LDP Container (LDPC): special resource maintaining membership relationships with its LDP-Resources contained ; sub-types: Basic Container (members ldp:contains), Direct Container (relationship type + membership constant subject), Indirect Container (advanced). (3) LDP Non-RDF Source (LDP-NR): binary resources (images, PDFs) hosted in LDP container. HTTP verbs: POST on container creates new resource, GET retrieves, PATCH updates partially via SPARQL Update query, etag-based optimistic concurrency control, ldp:member ldp:contains predicates auto-managed. Adoption: Solid project (Inrupt company Tim Berners-Lee), some academic Linked Data publishers, IBM Concert (deprecated), Fedora Commons digital repository, Apache Marmotta (defunct).
Origin
W3C Linked Data Platform Working Group 2012 ; LDP 1.0 W3C Recommendation 26 February 2015 ; WG closed 2015.
Example in context
Solid Pod (Tim Berners-Lee Solid project) hosts user's personal data: LDP container /alice/photos/ contains LDP-Resources individual photos (Turtle metadata + JPG binary LDP-NR), Solid apps CRUD via HTTP GET/POST/PATCH ; alice grants permissions specific apps via WAC ACLs.
Related terms
- W3C JSON-LD 1.1 — possible format.