Linked Data Platform (LDP) is alinked data specification defining a set of integration patterns for buildingRESTfulHTTP services that are capable of read/write ofRDF data.
The Linked Data Platform allows use of RESTful HTTP to consume, create, update and delete both RDF and non-RDF resources.[1] In addition, it defines a set of "container" constructs – buckets into which documents can be added with a relationship between the bucket and the object similar to the relationship between a blog and its constituent blog posts.[2]
LDP evolved from work atIBM's Rational Product Group for application integration. Starting in 2010, IBM looked at linked data forapplication lifecycle management and sought what was an alternative means for read–write linked data.
IBM joined with the W3C in June 2012 to form aW3C working group, which operated until July 2015.[3][4] On 26 February 2015, the W3C Linked Data Platform 1.0 was approved as a W3C Recommendation.[5]
Read–write linked data was previously described usingWebDAV andSPARUL[6] byTim Berners-Lee in his design issues[7][8] that built upon his four principles for linked data.[9]
The Linked Data Platform includes Tim Berners-Lee's four principles, and focuses on thefollowing concepts.[10]
LDP is not a file system, but it uses linked data to produce the kind of information that can be used to create a modern file system abstraction for interacting with HTTP-accessible resources (colloquially referred to as "Web resources").
In contrast, WebDAV is a "set of extensions to the HTTP protocol which allows users to collaboratively edit and manage files on remote web servers".[11]
However, LDP can be used with WebDAV. For example, there are live LDP containers in the wild, identified by linked data URIs, that can also function as WebDAV endpoints (i.e., mountable by any WebDAV compliant user agent).