--- a/ldp-primer/ldp-primer.html Mon Sep 08 12:44:59 2014 -0400
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,904 +0,0 @@
-<?xml version='1.0' encoding='UTF-8' ?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" prefix="td: http://www.w3.org/2006/03/test-description# tn: http://ldp.example.org/NewTestDefinitions# ht: http://www.w3.org/2011/http#">
-
-<head>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Linked Data Platform 1.0 Primer</title>
- <style type="text/css">
- div.syntaxmenu {
- border: 1px dotted black;
- padding: 0 0 0 0.5em;
- margin: 0em;
- }
- div.code {
- font-family: monospace;
- font-size: 110%;
- }
- th {
- text-align: left;
- }
- td {
- vertical-align: top;
- padding-right: 2em;
- }
- td.col1 {
- width: 300px;
- }
- </style>
- <script type="text/javascript">
- var displayed = [];
- displayed["turtle"] = 1;
- displayed["jsonld"] = 0;
-
- function primerOnLoad() {
- setTimeout(function () {
- display('turtle', '');
- set_display_by_id('hide-ts', '');
- set_display_by_id('show-ts', 'none');
- display('jsonld', 'none');
- set_display_by_id('hide-js', 'none');
- set_display_by_id('show-js', '');
- }, 3000)
- }
-
- function display(syntax, status) {
- var howmany = 0;
- if (status == 'none') {
- displayed[syntax] = 0;
- } else {
- displayed[syntax] = 1;
- }
- for (i in displayed) {
- howmany = howmany + displayed[i];
- }
- set_display_by_class('div', syntax, status);
- if (howmany == 1) {
- set_display_by_class('b', 'syntax-head', 'none');
- } else {
- set_display_by_class('b', 'syntax-head', '');
- }
- }
-
- function getElementsByClassName(oElm, strTagName, oClassNames) {
- var arrElements = (!(!(strTagName == "*") || !(oElm.all))) ? oElm.all : oElm.getElementsByTagName(strTagName);
- var arrReturnElements = new Array();
- var arrRegExpClassNames = new Array();
- if (typeof oClassNames == "object") {
- for (var i = 0; !(i >= oClassNames.length); i++) { /*>*/
- arrRegExpClassNames.push(new RegExp("(^|\\s)" + oClassNames[i].replace(/\-/g, "\\-") + "(\\s|$)"));
- }
- } else {
- arrRegExpClassNames.push(new RegExp("(^|\\s)" + oClassNames.replace(/\-/g, "\\-") + "(\\s|$)"));
- }
- var oElement;
- var bMatchesAll;
- for (var j = 0; !(j >= arrElements.length); j++) { /*>*/
- oElement = arrElements[j];
- bMatchesAll = true;
- for (var k = 0; !(k >= arrRegExpClassNames.length); k++) { /*>*/
- if (!arrRegExpClassNames[k].test(oElement.className)) {
- bMatchesAll = false;
- break;
- }
- }
- if (bMatchesAll) {
- arrReturnElements.push(oElement);
- }
- }
- return (arrReturnElements)
- }
-
- function set_display_by_class(el, cls, newValue) {
- var e = getElementsByClassName(document, el, cls);
- if (e != null) {
- for (var i = 0; !(i >= e.length); i++) {
- e[i].style.display = newValue;
- }
- }
- }
-
- function set_display_by_id(id, newValue) {
- var e = document.getElementById(id);
- if (e != null) {
- e.style.display = newValue;
- }
- }
- </script>
- <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
- <script class='remove'>
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "ldp-primer",
- // TODO: Confirm short name
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- // subtitle : "an excellent document",
-
- // if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- // copyrightStart: "2005"
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- //previousPublishDate: "2013-03-07",
- //previousMaturity: "FPWD",
- //previousURI: "http://www.w3.org/TR/2013/WD-ldp-20130307/",
-
- // if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://www.w3.org/2012/ldp/hg/ldp-primer/ldp-primer.html",
-
- // if this is a LCWD, uncomment and set the end of its review period
- // lcEnd: "2009-08-05",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- //extraCSS: ["https://dvcs.w3.org/hg/ldpwg/css/respec.css"],
-
- // editors, add as many as you like
- // only "name" is required
- editors: [{
- name: "Nandana Mihindukulasooriya",
- url: "http://mayor2.dia.fi.upm.es/oeg-upm/index.php/en/universitystaff/290-nandana",
- company: "Ontology Engineering Group, Universidad Politécnica de Madrid",
- companyURL: "http://www.oeg-upm.net/"
- }, {
- name: "Roger Menday",
- url: "#",
- company: "Fujitsu Laboratories of Europe Limited, London",
- companyURL: "#"
- }, ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- //authors: [
- // { name: "Your Name", url: "http://example.org/",
- // company: "Your Company", companyURL: "http://example.com/" },
- //],
-
- // name of the WG
- wg: "Linked Data Platform Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2012/ldp",
-
- // name (without the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-ldp-comments",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "http://www.w3.org/2004/01/pp-impl/55082/status",
- doRDFa: "1.1",
- localBiblio: {
- "LDP-BP": {
- title: "LDP Best Practices and Guidelines",
- href: "http://www.w3.org/2012/ldp/hg/ldp-bp/ldp-bp.html",
- authors: [
- "Cody Burleson",
- "Miguel Esteban Gutiérrez",
- "Nandana Mihindukulasooriya"
- ],
- status: "WD",
- deliveredBy: [
- "http://www.w3.org/2012/ldp/"
- ],
- publisher: "W3C"
- },
- "LDP-TESTS": {
- title: "Linked Data Platform 1.0 Test Cases",
- href: "http://www.w3.org/2012/ldp/hg/tests/ldp-testsuite.html",
- authors: [
- "Raúl García-Castro",
- "Fernando Serena",
- "Steve Speicher"
- ],
- status: "WD",
- deliveredBy: [
- "http://www.w3.org/2012/ldp/"
- ],
- publisher: "W3C"
- }
- }
- };
- // Replaces HTML characters (brackets and quotes) with legal HTML representations
- // The following example would include a code example from another file and then
- // call this function to make the included code renderable in a browser.
- //
- // <pre class='example' data-include='include-rdf-type.ttl' data-oninclude='fixCode'></pre>
-
- function fixCode(r, content) {
- var result = content;
- result = result.replace(/</g, "<").replace(/>/g, ">");
- result = result.replace(/'/g, "'").replace(/"/g, """);
- var ss = result.split('---')
- var s1 = "<div class='turtle' style='font-family: sans-serif;'>Turtle:</div><div class='turtle'><pre>" + ss[0] + "</pre></div>";
- var s2 = "<div class='jsonld' style='font-family: sans-serif;'>JSON-LD:</div><div class='jsonld'><pre>" + ss[1] + "</pre></div>";
- return s1 + s2;
- }
-
- function highlight(r, content) {
- return '<span style="background-color:#ccffcc">' + content + '</span>';
- }
- </script>
-</head>
-
-<body onLoad="primerOnLoad()">
-
- <section id='abstract'>
- This primer provides an introduction to the Linked Data Platform (LDP), with examples illustrating the principal concepts such as the notion of an LDP resource and the LDP container and how they can be used by Web clients.
- Two sample scenarios show how an LDP client can interact with a LDP server in the context of a read-write Linked Data application i.e. how to use HTTP for accessing, updating, creating and deleting resources from servers that expose their resources as Linked Data.
- </section>
-
- <section id='sotd'>
- <p>
- This is the first draft of LDP Primer Note from the <a href="http://www.w3.org/2012/ldp">W3C LDP working group</a>.
- </p>
- </section>
-
- <section id="intro-section">
- <h1 id="intro">Introduction</h1>
-
- <p>
- The term "Linked Data" [[LINKED-DATA]] refers to an approach to publishing data that puts linking at the heart of the notion of data, and uses the linking technologies provided by the Web to enable the weaving of a global distributed database.
- By naming real world entities - be they web resources, physical objects such as the Eiffel Tower, or even more abstract things such as relations or concepts - with http(s) URLs, whose meaning can be determined by dereferencing the document at that URL, and by using the relational framework provided by RDF, data can be published and linked in the same way web pages can.
- The Linked Data Protocol specifies how web applications can, using the HTTP protocol, find resources and follow links, publish new resources, edit and delete existing ones.
- </p>
- <p>
- The Primer aims to provide introductory examples and guidance in the use of the LDP protocol, in accordance with best practices [[LDP-BP]].
- For a systematic description of the protocol the reader should consult the normative LDP reference [[LDP]].
- For an overview of the use cases for LDP and the elicited requirements that guided its design, the reader should consult the LDP Use Cases and Requirements [[LDP-UCR]]; for best practices and guidelines, the reader should consult the LDP Best Practices and Guidelines document [[LDP-BP]].
- </p>
-
- <b id="conventions">Conventions Used in This Document</b>
-
- <p>The examples in this guide are given as a serialization of RDF graphs using the Turtle [[turtle]] and JSON-LD [[json-ld]] syntaxes of RDF.</p>
-
- <div class="syntaxmenu">
- <p>The buttons below can be used to show or hide the available syntaxes.</p>
- <form>
- <p>
- <input id="hide-ts" onclick="display('turtle', 'none'); set_display_by_id('hide-ts', 'none'); set_display_by_id('show-ts', ''); return false;" type="button" value="Hide Turtle Syntax" />
- <input id="show-ts" onclick="display('turtle', ''); set_display_by_id('hide-ts', ''); set_display_by_id('show-ts', 'none'); return false;" style="display:none" type="button" value="Show Turtle Syntax" />
- <input id="hide-js" onclick="display('jsonld','none'); set_display_by_id('hide-js', 'none'); set_display_by_id('show-js', ''); return false;" type="button" value="Hide JSON-LD Syntax" />
- <input id="show-js" onclick="display('jsonld',''); set_display_by_id('hide-js', ''); set_display_by_id('show-js', 'none'); return false;" style="display:none" type="button" value="Show JSON-lD Syntax" />
- </p>
- </form>
- </div>
-
- <!--p>The JSON-LD examples refer to the following (external) context document:</p>
- <pre style="word-wrap: break-word; white-space: pre-wrap;">
- {
- "@context":
- {
- "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
- "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
- "owl": "http://www.w3.org/2002/07/owl#",
- "ldp": "http://www.w3.org/ns/ldp#",
- "xsd": "http://www.w3.org/2001/XMLSchema#",
- "dcterms": "http://purl.org/dc/terms/",
- "foaf": "http://xmlns.com/foaf/0.1/",
- "wdrs": "http://www.w3.org/2007/05/powder-s#",
- "bt": "http://example.org/vocab/bugtracker#"
- }
- }
- </pre-->
- <p>
-
- </p>
-
- <h2>LDP concepts in a glance</h2>
-
- <p>
- A server hosting Linked Data Platform Resources (LDPRs) may manage two kinds of LDPRs: those resources whose state is represented using RDF (called LDP RDF Sources (LDP-RSs)), and those using other formats (called LDP Non-RDF Sources (LDP-NRs)) such as HTML files, images, other binary files, etc. Resoures respond to retrieval operations using HTTP GET. Often a description conveyed in the response document will describe a specific domain entity; Status, Friendship, Product, Order, Bug, etc. On the other hand, it might contain a description of a number of different concepts. The links contained in the descriptions lead to the subsequent discovery and processing of other resources. Affordances offered by the server make discoverable the forward paths in the application. Together the resources, links and associated affordances together specify what might be termed the API.
- </p>
- <blockquote>
- <p>Types of LDPRs:
- <img src="images/resources.png" />
- </p>
- </blockquote>
- <p>
- The LDP protocol covers read and write interactions with Resources. Writable aspects include creation of new resources (using POST or PUT), updates (using PUT or PATCH), and deletion of resources. Resource creation is an essential feature providing structured creation of resources. Affordances published by the server show that some Resources can be used to create other Resources. This common pattern is often seen in cases where one resource is be made up of a number of others, e.g. a Document Store consists of Documents, a Bug Tracker consists of Bug Reports, a Photo Album consists of Photos, the Net Worth of a person consists of Assets and Liabilities. LDP defines creation for a special kind of Resource called a Container (LDPC), which is able to respond to requests to create new resources, in addition to the general mechanisms HTTP defines. During creation the created resource is added to its Container and a containment link between the Container and the new entry is made.
- </p>
- <p>
- Therefore a LDPC is a specialization of a LDP-RS representing a collection of links to LDPRs or information resources [[WEBARCH]] that responds to client requests for creation, modification, and/or enumeration of its linked members and documents. The simplest container is the Basic Container (LDP-BC). It defines the basic containment described using a generic vocabulary. This can be used in a generic storage service to manage a containment hierarchy of arbitrary resources.
- </p>
- <figure id="fig-bc">
- <img src="images/bc.png" alt=".." />
- <figcaption>Generic document storage using a Basic Container.</figcaption>
- </figure>
- <p>
- Such servers do not impose any restriction on LDPRs and generally act as storage systems without any domain specific application logic and vocabularies. The <a href="#docstore">first scenario in this document</a> concerns a document storage system based on Basic Containers.
- </p>
- <p>
- A Direct Container is a specialisation of a Basic Container. Additional assertions called membership triples which use a domain-specific vocabulary are made by a Direct Container as part of the creation process. The membership triples augment the containment triples maintained by all containers. For example, one aspect of a Product inventory system concerns the how a Direct Container is used for the management of a Product portfolio, where use of existing vocabularly is preferable.
- </p>
- <figure id="fig-dc1">
- <img src="images/dc1.png" alt=".." />
- <figcaption>Using domain vocabularly with a Direct container.</figcaption>
- </figure>
- <p>
- Direct Container membership triples can be about subjects other than the Container resource. An example is a Photo management application where a Photo Container is used for the management of Photos, and where membership triples then express the relationship between a User and a Photo.
- </p>
- <figure id="fig-dc_photos">
- <img src="images/dc_photos.png" alt=".." />
- <figcaption>Membership triples with a non-Container subject.</figcaption>
- </figure>
- <p>
- Another common pattern is where different facets of a Resource be managed using multiple Containers. For example, a Bug Report is has an associated list of Comments as well as supportive media resources.
- </p>
- <figure id="fig-dc_bugs">
- <img src="images/dc_bugs.png" alt=".." />
- <figcaption>Managing multiple facets of a Bug with two Direct Containers.</figcaption>
- </figure>
- <p>
- One important usage concerns using LDP to expose the data and services of existing applications. These systems impose restrictions on LDPRs since the LDP interactions should consider the constraints of the underlying business logic and data model. The <a href="#bugtracker">bug tracker example</a> presented in the latter part of this primer is an example of an application specific LDP server.
- </p>
-
- <p class="note">
- Formal definitions of the terms LDPR, LDPC, and other concepts introduced by LDP can be found in the 'Terminology' section of the Linked Data Platform 1.0 specification [[LDP]]
- </p>
-
- <p>
- The following provide a set of examples to show the Linked Data Platform interactions. Note, this is a primer and should not be considered as a canonical example of ideal LDP modeling.
- </p>
-
- </section>
-
- <section id="docstore">
- <h1>Online document store example (LDP Basics)</h1>
-
- <p>
- This section provides a set of examples of using an online document store application. These examples will demonstrate the behaviour of both types of LDPRs and LDP Basic Containers. Registration with the online document store application by a user results in some data storage space (a root Basic Container) where the application's web resources are stored. Using this root Basic Container a user can create new documents and also child containers to further organize her documents stored in this application.
- </p>
- <p>
- APIs of web applications are commonly documented by listing valid operations which can operate on URLs, where the URLs are described as templates. A description of our exemplary LDP based document store is in the following table. We note with emphasis that it is important for servers to use links as the main mechanism to reveal the location of resources. If it would be necessary to encode such templates into client applications, this would be a strong indicator that the design breaches a number of good design principles. </p>
- </p>
-
- <table class="simple">
- <thead>
- <th>Path</th>
- <th>Method</th>
- <th>Description</th>
- </thead>
- <tbody>
- <tr>
- <td rowspan="5">/{username}/</td>
- <td>GET</td>
- <td>Lists all the documents in the root container.</td>
- </tr>
- <tr>
- <td>POST</td>
- <td>Create a new document under the root container.</td>
- </tr>
- <tr>
- <td>PUT</td>
- <td>Update the description and/or list of files of the root container.</td>
- </tr>
- <tr>
- <td>PATCH</td>
- <td>Update the description and/or list of files of the root container.</td>
- </tr>
- <tr>
- <td>DELETE</td>
- <td>Not allowed.</td>
- </tr>
- <tr>
- <td class="col1" rowspan="5">
- <div class='code'>/{username}/{{document}/}*</div>
- </td>
- <td>GET</td>
- <td>Retrieve the document.</td>
- </tr>
- <tr>
- <td>POST</td>
- <td>Discovered from the resource affordances.</td>
- </tr>
- <tr>
- <td>PUT</td>
- <td>Update the document.</td>
- </tr>
- <tr>
- <td>PATCH</td>
- <td>Partial update to the document if PATCH is supported.</td>
- </tr>
- <tr>
- <td>DELETE</td>
- <td>Delete the document.</td>
- </tr>
- <tr>
- <td rowspan="2">
- <div class='code'>/*/*</div>
- </td>
- <td>OPTIONS</td>
- <td>Discover the allowed operations over a resource</td>
- </tr>
- <tr>
- <td>HEAD</td>
- <td>Only retrieve meta-information about a resource</td>
- </tr>
- </tbody>
- </table>
-
- <p>
- In this example, we will see how Alice, a user of this system, does read / write management of documents using the LDP protocol. A typical interaction with the system would start with Alice registering as a user. It is likely that registration would be a LDP based interaction, but this aspect is out of scope of this example. A consequence of the registration is allocation of space for the storage of documents, and communication of this URL to the user, e.g. a basic container at http://example.org/alice/. This section describes a typical flow of interactions where Alice firsts reads the root document and discovers its affordances. This is followed by subsequent examples of creation, update and delete, and finishes with how the client is able to create nested structure from the containers.
- </p>
-
- <section id="filelookup">
- <h2>Looking up a basic container (GET on an LDP-BC) </h2>
-
- <p>First Alice looks up her storage by retrieving the LDP Basic Container assigned to her to hold her documents. Alice's LDP client does this by doing a GET request on the URI, http://example.org/alice/. </p>
-
- <pre title="Request - basic container retrieval" class='example' data-include='examples/getbc.txt' data-oninclude='fixCode'></pre>
-
- <p>As her document storage was just created, it is an empty container. </p>
-
- <pre title="Response - basic container retrieval" class='example' data-include='examples/getbc_res.txt' data-oninclude='fixCode'></pre>
-
- <p> As shown in the example, in addition to the RDF representation of the Basic Container using the requested media type the server provides an etag of the resource representation and Link headers advertising that the requested resource is indeed an LDP Basic Container and it will support the LDP interaction model. </p>
-
- <p> In addition, the response also contains "Allow" header which advertises which HTTP operations are supported by this LDP Basic Container resource. In this example, it supports OPTIONS,HEAD,GET,POST,PUT,PATCH HTTP verbs.</p>
-
- <p class="note">The Linked Data Platform 1.0 specification [[LDP]] says that all LDP servers MUST support the Turtle media type for LDP-RS resources and SHOULD support JSON-LD media type.</p>
-
- </section>
-
- <section>
- <h2> Discovering the affordances (OPTIONS on an LDP-BC) </h2>
-
- <p>
- In the previous example, we saw that Alice can discover what operations are allowed on a resource by doing a GET request on the resource. As an alternative, she can use the OPTIONS operation to learn of the permitted operations on any given resource.
- </p>
-
- <pre title="Request - retreiving OPTIONS of a basic container" class='example'>
- OPTIONS /alice/ HTTP/1.1
- Host: example.org
- </pre>
-
- <pre title="Response - retreiving OPTIONS of a basic container" class='example'>
-HTTP/1.1 204 OK
-Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
-Accept-Post: text/turtle, application/ld+json, image/bmp, image/jpeg
-Accept-Patch: example/patch
-Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel='type'
- </pre>
-
- <p>According to the response, HTTP operations {OPTIONS,HEAD, GET,POST,PUT,PATCH} are allowed on her root container. In addition to the allowed operations, Accept-Post and Accept-Patch provides which media types are supported by the respective operations. The rel="type" Link header advertises that this resource supports LDP protocol and it is an LDP Basic Container.</p>
-
- <p>In this case, the response tells Alice's LDP client that this is an LDP-Basic Container and the container allows her to POST things of both RDF types (text/turtle, application/ld+json) and images (image/bmp and image/jpeg).</p>
-
- </section>
-
- <section>
- <h2> Creating a RDF resource (POST an RDF resource to an LDP-BC) </h2>
-
- <p>
- Alice can upload a social profile document to her store, by POSTing her FOAF personal profile document to her LDP-BC at the root of her document store. Note, the Slug header offers the server a hint about URL of the resource to be created.
- </p>
-
- <p> The FOAF document includes statements about the resource to be created and other resources relative to the resource to be created. According the LDP specification
- Alice can use null relative URI (<>) in the request entity body to refer to resource to be created.
-
- </p>
-
- <pre title="Request - creating a RDF resource" class='example' data-include='examples/bccreate.txt' data-oninclude='fixCode'></pre>
-
- </pre>
-
- <pre title="Response - creating a RDF resource" class="example">
-HTTP/1.1 201 Created
-Location: http://example.org/alice/foaf
-Link: <http://www.w3.org/ns/ldp#Resource>; rel='type'
-Content-Length: 0
- </pre>
- <p> The response to the create request provides a Link to the newly created resource using the Location header. In this case, the server has honored the hint provided by the slug header and created the new resource in the URL http://example.org/alice/foaf. </p>
- <p>Knowing the URL of the newly created resource, Alice can check the container again to confirm that the container correctly contains the newly created resource.</p>
-
- <pre title="Request - basic container retrieval after resource created" class="example">
- GET /alice/ HTTP/1.1
- Host: example.org
- Accept: text/turtle, application/ld+json
- </pre>
-
- <pre title="Response - basic container retrieval after resource created" class='example' data-include='examples/bcget_res.txt' data-oninclude='fixCode'/>
- <p>
- The ldp:contains containment triple discloses the newly created resource in the response.
- </p>
-
- </section>
-
- <section>
- <h2> Creating a non-RDF (binary) resource (POST an image to an LDP-BC) </h2>
-
- <p>Next, Alice wants to upload a photo of herself to the document storage. She can create an image by POSTing it in the same way she created the RDF document.</p>
-
- <pre title="Request - creating a non-RDF resource" class="example">
-POST /alice/ HTTP/1.1
-Host: example.org
-Slug: avatar
-Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
-Content-Type: image/png
-Content- Length: 1020
-
-### binary data ###
- </pre>
-
- <pre title="Response - creating a non-RDF resource" class="example">
-HTTP/1.1 201 Created
-Location: http://example.org/alice/avatar
-Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
-Link: <http://example.org/alice/avatar/meta>; rel="describedby"
-Content-Length: 0
- </pre>
-
- <p> </p>
-
- <p>The outcome of creating a non-RDF is similar to creating a RDF resource. If successful, the server will return a 201 success code with a Location header that points to the created resource. Furthermore, in the case of binary resources the server may create an additional file to maintain the metadata about the binary file. In the above example, the server creates a new LDP-RS to maintain metadata about the binary resource such as creation date, owner, etc. and this metadata resource is advertised using a Link header with the relation "describedby". </p>
-
- <p> Similar to creating a RDF resource (LDP-RS), a containment triple will be added to the container when a non-RDF (LDP-NR) is created. Thus, the representation of the LDP container after creating the image looks like the following. </p>
- <pre title="Container representation after the non-RDF resource creation" class='example' data-include='examples/bc_after_bin.txt' data-oninclude='fixCode'></pre>
- </section>
-
- <section>
- <h2> Update a RDF LDP resource (PUT on an LDP-RS) </h2>
-
- <p>After creating the image as shown in the previous example, Alice now wants to update her FOAF profile with a link to the image. After retrieving her FOAF profile using a HTTP GET operation, she uses HTTP PUT to update the document by amending the RDF with a link to her photo.</p>
- <p> In this example, Alice's LDP client sends the E-tag of the resource representation that it retrieved previously to prevent any lost update problems. </p>
- <pre title="Request - updating a RDF resource" class="example" data-include='examples/foafupdate.txt' data-oninclude='fixCode'></pre>
-
- <pre title="Response - updating a RDF resource" class="example">
-HTTP/1.1 204 No Content
-Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
- </pre>
-
- <p>If the operation is successful as shown above, the document will be updated with new information.</p>
-
- <p class="note"> Alice can also use the PATCH operation to update the resource.</p>
-
- </section>
-
- <section>
- <h2> Deleting a resource (DELETE on an LDPR) </h2>
-
- <p>If Alice decides to delete the image, she can do that with a delete operation.</p>
-
- <pre title="Request - deleting a RDF resource" class="example">
-DELETE /alice/avatar HTTP/1.1
-Host: example.org
- </pre>
-
- <pre title="Response - deleting a RDF resource" class="example">
-HTTP/1.1 204 No Content
- </pre>
-
- <p> As well as deleting the resource, the server removes the containment triple from the container. For example, a subsequent GET request on the container will return a graph isomorphic to the one shown in the following representation::</p>
-
- <pre title="Container representation after resource deletion" class="example" data-include='examples/bc_after_del.txt' data-oninclude='fixCode'></pre>
-
- <p> For any subsequent request on the deleted resource, the server will respond with the appropriate HTTP response code. </p>
- <pre title="Request - after deletion" class="example">
- GET /alice/avatar HTTP/1.1
- Host: example.org
- Accept: image/png
- </pre>
-
- <pre title="Response - after deletion" class="example">
-HTTP/1.1 410 Gone
- </pre>
- </section>
-
- <section>
- <h3 id="meta-structure">Structural Manipulation (Child Containers)</h3>
- <p>In order for the client to introduce hierarchy to the management of documents, the document store allows creation of documents which are containers. That enables Alice to create a container hierarchy to organise her documents. This can be done by POSTing (a child) container representation to a (parent) container. This enables Alice to create a child container which she intends to use for image storage.
- </p>
-
- <figure id="fig-bcs">
- <img src="images/bcs.png" alt=".." />
- <figcaption>Child Containers inside a Basic Container.</figcaption>
- </figure>
-
- <pre title="State of Alice's document store before creating the photo (child) container" class='example' data-include='examples/create_cr_s1.txt' data-oninclude='fixCode'></pre>
-
- <p>To create a new container for managing photos, Alice POSTs a representation of a container (LDP-BC) to the root container. Alice express her intention that the newly created resource should be an LDP Basic Container by including a Link header in the request with the relationship 'type'. </p>
- <pre title="Request - creating a new container" class='example' data-include='examples/create_cr_req.txt' data-oninclude='fixCode'></pre>
- <p>If the create is successful, the server responds with location of the newly created container for the photos.</p>
- <pre title="Response - creating the new container" class="example">
-HTTP/1.1 201 Created
-Location: http://example.org/alice/photos/
-Content-Length: 0
- </pre>
-
- <p>After creation of this new container, the parent container will look like</p>
- <pre title="State of Alice's document store after creating the photo (child) container" class='example' data-include='examples/create_cr_s2.txt' data-oninclude='fixCode'></pre>
- <p>and the photo container will look like the following.</p>
- <pre title="State of Alice's newly created photo container" class='example' data-include='examples/create_cr_s3.txt' data-oninclude='fixCode'></pre>
-
- </section>
-
- </section>
-
- <section id="bugtracker">
- <h1>Bug Tracker Example (LDP Direct containers)</h1>
-
- <p>The previous section provided practical examples of basic LDP interactions using LDP Basic Containers. One of the limitations of LDP Basic Containers is that a fixed LDP vocabulary is used to assert the relations between a container and its contained resources. However, some scenarios require domain specific vocabulary to be used to list the members of a container. For example, an application which already used Linked Data and its own vocabulary may like to continue using the same vocabulary when migrating to LDP protocol. LDP Direct containers introduce the concept of membership triples allowing the flexibility to define the form of the membership. One of these flexibility points is the ability to select the predicate of the membership triple which can be from a domain-specific vocabulary. This is done using the ldp:hasMemberRelation or ldp:isMemberOfRelation predicate of the Direct Containers.</p>
-
- <p>In addition, in some scenarios it is necessary to add relationships between the newly created resource and some other resource (which is not necessarily the container or another document / information resource). This allows to define relationship between any other information resource or non-information resource (real world thing) by defining the membership constant subject or the object URI of the membership triples using ldp:membershipResource predicate of the Direct Container. The usage of the ldp:hasMemberRelation predicate as well as the ldp:membershipResource will be explained in the following examples. </p>
-
- <p class="note">For more information on information resources (documents) vs real world entities (things) separation please refer to <a href="http://www.w3.org/TR/webarch/#id-resources">Web Arch (Section 2.2. URI/Resource Relationships) </a>, , <a href="http://www.w3.org/TR/cooluris/#semweb">Cool URIs (Section 3. URIs for Real-World Objects)</a>, <a href="http://www.w3.org/TR/urls-in-data/#landing-pages">URLs in Data (Section 3. Landing Pages and Records)</a>.</p>
-
- <p>
- The examples in this section will revolve around a very simple Bug Tracker application. Bug Tracker application records the bugs of several products allowing reporting, updating and deleting bugs and products. In contrast to the online document store example, the bug tracker wants to use an existing domain vocabulary, e.g. has_bug, to express membership relationships in the containers. LDP provides the additional interaction capability in the protocol to add the domain specific triples based on the properties defined in the LDP Direct Container.
- </p>
-
- <p>A RESTful API for a simple Bug Tracker system might be described as follows.</p>
-
- <table class="simple">
- <thead>
- <th>Path</th>
- <th>Method</th>
- <th>Description</th>
- </thead>
- <tbody>
- <!--tr>
- <td rowspan="5">/tracker/</td>
- <td>GET</td>
- <td>Lists all the product descriptions.</td>
- </tr>
- <tr>
- <td>POST</td>
- <td>Create a new product description.</td>
- </tr>
- <tr>
- <td>PUT</td>
- <td>Update the app description and/or list of product descriptions</td>
- </tr>
- <tr>
- <td>PATCH</td>
- <td>Update the app description and/or list of product descriptions</td>
- </tr>
- <tr>
- <td>DELETE</td>
- <td>Not allowed.</td>
- </tr-->
- <tr>
- <td class="col1" rowspan="5">
- <div class='code'>/tracker/{product-id}/</div>
- </td>
- <td>GET</td>
- <td>Lists the product description and bug reports associated with a product.</td>
- </tr>
- <tr>
- <td>POST</td>
- <td>Create a new bug report associated with a product.</td>
- </tr>
- <tr>
- <td>PUT</td>
- <td>Update the project description.</td>
- </tr>
- <tr>
- <td>PATCH</td>
- <td>Not supported.</td>
- </tr>
- <tr>
- <td>DELETE</td>
- <td>Delete the project description and associated bug reports.</td>
- </tr>
- <tr>
- <td rowspan="5">
- <div class='code'>/tracker/{product-id}/{bug-id}</div>
- </td>
- <td>GET</td>
- <td>Gets the bug report.</td>
- </tr>
- <tr>
- <td>POST</td>
- <td>Not supported.</td>
- </tr>
- <tr>
- <td>PUT</td>
- <td>Update the bug report.</td>
- </tr>
- <tr>
- <td>PATCH</td>
- <td>Not supported.</td>
- </tr>
- <tr>
- <td>DELETE</td>
- <td>Delete the bug report.</td>
- </tr>
- <tr>
- <td rowspan="2">
- <div class='code'>/tracker/*/*</div>
- </td>
- <td>OPTIONS</td>
- <td>Discover the allowed operations over a resource</td>
- </tr>
- <tr>
- <td>HEAD</td>
- <td>Only retrieve meta information about a resource</td>
- </tr>
- </tbody>
- </table>
-
- <p> In the examples in this section, we will only focus on the container representation, creation and deletion of resources because that is where the Basic Containers, Direct Containers, and Indirect Containers differ. Other operations such as updating a resource would be similar to what was illustrated in the previous example.</p>
-
- <section id="navandret">
- <h2>Navigation and Retrieval (GET on an LDP-DC)</h2>
-
- <p>One of the main use cases of the example bug tracker is to list a given product's bugs. Assuming that a user got a URL of a product by out of band means, she can look it up to get more information including the bugs associated with it. To get the description of the product, a user (or her LDP client) can do a GET request on the URI of the known product resource. LDPR servers must provide text/turtle representations of the requested LDPRs and may provide other RDF format representations such as JSON-LD or RDF/XML using standard HTTP content negotiation.</p>
- <pre class="example" title="Request - Product Lookup" data-include='examples/product_lookup_req.txt' data-oninclude='fixCode'></pre>
- <p>If the product resource is available, the server responds with the RDF representation of the Direct Container that corresponds to the given product using the requested media type,
- <code>text/turtle</code> or <code>application/ld+json</code> in this case.</p>
- <pre title="Response - Product Lookup" class='example' data-include='examples/product_lookup_resp.txt' data-oninclude='fixCode'></pre>
-
- <p>The representation of the product contains both information about the product such as the title and the bugs associated with the product and information about the product description such as the title of the product description and other properties of the LDP Container. </p>
-
- <p>As you can see from the Link Header that is returned and the RDF representation of the container, this example uses an LDP Direct Container. LDP-DCs contain both containment triples and membership triples and provide the flexibility to the applications to use domain specific vocabulary in the membership triples. For example, in the above example the LDP-DC manages the member relationship, (<?productURI>, bt:hasBug, <?bugURI>), using the application-specific vocabulary term, bt:hasBug. This is done by defining the ldp:hasMemberRelation predicate of the Direct Container to bt:hasBug (<?directContainerURI>, ldp:hasMemberRelation, bt:hasbug). </p>
-
- <p class="note"> The Direct Container shown in the above example has the membership triple pattern ( membership-constant-URI , membership-predicate , member-derived-URI ) using ldp:hasMemberRelation where the constant membership resource is in the subject of the triple and the newly created resources will be added as the object of the triple. It is also possible for the Direct Container to have the membership triple pattern ( member-derived-URI , membership-predicate , membership-constant-URI ) using ldp:isMemberOfRelation predicate where the constant member resource will be the object of the triple and the newly created resource will be added as the subject of the triple. </p>
-
- <p> In addition, in this example the bugs are associated with the product resource (a non-information resource with a # URI) and not with the product description Direct Container itself. This is done by defining the ldp:membershipResource predicate of the LDP Direct Container as the product non-information resource URI (<?directContainerURI>, ldp:membershipResource, </tracker/product1/#it>). By doing so one can define the subject of the membership triple any resource of interest.
- </p>
-
- <p>The next example illustrates the behaviour of LDP Direct containers when new resources are created and how aforementioned predicates of the Direct Containers affect the interaction model of LDP.</p>
-
-
- <!-- <p>Looking up a bug is similar to looking up a product. Based on links in the representation of the Product, the client uses GET to navigate to a known Bug resource.</p>
-
- <pre class="example" title="Bug lookup request"
- data-include='bug_look_up_req.txt' data-oninclude='fixCode'></pre>
- <p>The server responds with the representation of the bug.</p>
- <pre title="Bug lookup response"
- class='example' data-include='bug_look_up_resp.txt'
- data-oninclude='fixCode'></pre -->
-
- </section>
-
- <section>
- <h3 id="BugCreate">Creation (POST a resource to an LDP-DC)</h3>
- <p>Continuing from the previous example, we can report a Bug against the "LDP Demo" product by creating a Bug report (an LDPR representing the bug) under the "LDP Demo" product description LDPC by posting a RDF representation of the Bug report to the LDPC associated with the product description. </p>
-
- <p> The bug report document includes statements about the resource to be created. According the LDP specification, a client can use null relative URI (<>) in the request entity body to refer to resource to be created.
-
- <pre title="A request for creating a bug" class='example' data-include='examples/bug_create_req.txt' data-oninclude='fixCode'></pre>
- <p>If the creation is successful, the server responds with location of the newly created resource.</p>
- <pre title="A response of creating new a bug" class='example' data-oninclude='fixCode'>
-HTTP/1.1 201 Created
-Location: http://example.org/tracker/ldp-demo/bug67
-Content-Length: 0
- </pre>
-
- <p>If the creation fails, the server will respond with an appropriate status code depending on the error. If successful, the LDP Demo product description LDPC will have the following representation after the creation of new resource.</p>
- <pre title="The state of the product LDPC after the bug creation" class='example' data-include='examples/bug_create_s1.txt' data-oninclude='fixCode'></pre>
- <p> As you can see two new triples are added to the container. That is (</tracker/ldp-demo/>, <ldp:contains>, </tracker/ldp-demo/bug67>) and
- (</tracker/ldp-demo/#it>, <bt:hasbug>, </tracker/ldp-demo/bug67>). The former is added in any type of container and the latter is defined by the direct
- container properties. </p>
- <p>The created Bug resource will have the following representation. Note that server has added a server managed property, creation date (dcterms:created), and a default value for the state (bt:isInState) to the Bug in addition to what was POSTed.</p>
- <pre title="The state of the bug LDPR" class='example' data-include='examples/bug_create_s2.txt' data-oninclude='fixCode'></pre>
-
- </section>
-
- <section>
- <h3 id="BugDelete">Deletion (DELETE on an LDPR associated with an LDP-DC)</h3>
-
- This example illustrates the behaviour of a Direct Container when a resource is deleted.
-
- <pre class="example">
- DELETE /tracker/ldp-demo/bug3 HTTP/1.1
- Host: example.org
- If-Match: W/"123454322"
- </pre>
- <p>If the delete is successful, the server will respond with a success status code.</p>
- <pre class="example">
- HTTP/1.1 204 No Content
- </pre>
-
- <p> After the deletion, the representation of the container will look like the following</p>
-
- <pre title="The state of the product LDPC after the bug deletion" class='example' data-include='examples/bug_delete_s1.txt' data-oninclude='fixCode'></pre>
-
- <p> As seen from the LDP Direct Container representation above, both the containment triple (</tracker/ldp-demo/>, ldp:contains, </tracker/ldp-demo/bug3>) and the membership triple (</tracker/ldp-demo/#it>, bt:hasBug, </tracker/ldp-demo/bug3>) were removed from the container representation. </p>
-
- </section>
-
- </section>
-
- <section id="bugtrackerextd">
- <h1>Extended Bug Tracker Example (LDP Indirect containers)</h1>
-
- <p> In this next example, we will use the same scenario as in the previous example, but change the container type to a LDP Indirect Container to show the differences between LDP Direct Containers and Indirect Containers and when to use LDP Indirect Containers. Though LDP Direct Containers provide the flexibility to define the constant membership URI (the subject of the membership triple when using ldp:hasMemberRelation or the object of the membership triple when using ldp:isMemberOfRelation) and the membership predicate, when creating members the member derived URI is always the newly created document URL. LDP Indirect containers provide more flexibility by allowing the member derived URI to be any resource; it could be either a non-information resource or a document other than the newly created resource. This done by defining the predicate to look for in the representation of the resource to be created by setting the ldp:insertedContentRelation predicate of the LDP Indirect Container. How this done will be explained in the following examples. </p>
-
- <section id="navandretext">
- <h2>Navigation and Retrieval (GET on an LDP-IC) </h2>
-
- <p> Similar to the previous LDP-DC example, first we will retrieve the representation of the LDP Indirect Container.</p>
-
- <pre class="example" title="Product lookup request" data-include='examples/product_lookup_req.txt' data-oninclude='fixCode'></pre>
- <p> As a response to the GET request, the server responds with the representation of the product description container.</p>
- <pre title="HTTP response for product lookup" class='example' data-include='examples/ic_product_lookup_resp.txt' data-oninclude='fixCode'></pre>
-
- <p> Now the product container is a LDP Indirect container, which has one main difference: the container has an additional predicate called "ldp:insertedContentRelation". Further, the objects of the containment triples and the membership triples are not the same. While the object of the containment triple is the same (e.g. </tracker/ldp-demo/bug3>, an information resource) the object of the membership triple is now (e.g. </tracker/ldp-demo/bug3#it>, a non-information resource or real world thing). This distinction is because of the ldp:insertedContentRelation definition. How this works will be explained in <a href="#creationext">the next example</a> on creating a new resource. </p>
-
- </section>
- <!-- end navandretext -->
-
- <section id="creationext">
- <h3 id="IndirectCreate">Creation (POST a resource to an LDP-IC) </h3>
-
- <p>Continuing from the previous example, we can create a new Bug Report against the 'LDP demo' product by creating a Bug Report LDPR under the 'LDP Demo' product description LDPC.</p>
-
- <p>The client POSTs a representation of a Bug Report to the Bug Tracker LDPC.</p>
- <pre title="A request for creating a bug" class='example' data-include='examples/ic_bug_create_req.txt' data-oninclude='fixCode'></pre>
- <p> One thing to note is that the representation of the resource to be created contains a triple (< >, foaf:primaryTopic , <#it>). If the create request is successful, the server responds with location of the newly created resource.</p>
- <pre title="A response of creating new a bug" class='example' data-oninclude='fixCode'>
-HTTP/1.1 201 Created
-Location: http://example.org/tracker/ldp-demo/bug67
-Content-Length: 0
- </pre>
-
- <p>If the creation fails, the server will respond with an appropriate status code depending on the error. After the resource is creation, the Product A LDPC will have the following representation.</p>
- <pre title="The state of the product LDPC after the bug creation" class='example' data-include='examples/ic_bug_create_s1.txt' data-oninclude='fixCode'></pre>
- <p> As you can see, two new triples are added to the container. That is (</tracker/ldp-demo/>, <ldp:contains>, </tracker/ldp-demo/bug67>) and
- (</tracker/ldp-demo/#it>, <bt:hasbug>, </tracker/ldp-demo/bug67#it>). </p>
-
- </section>
- <!-- end creationext -->
-
- </section>
-
-
- <section>
- <h1>Security</h1>
- <p>It is not the focus of the Linked Data Platform WG to provide security mechanisms for read/write Linked Data applications; since LDP builds on HTTP, it can re-use any mechanism defined for HTTP. Though most of the security mechanisms that are applicable to general web applications are equally applicable to Linked Data applications, there is still some space to build security mechanisms specific to Linked Data applications by leveraging the Linked Data technologies and providing concrete security requirements for Linked Data applications. In this context, LDP WG has started to create a WG note on Access Control which aims to produce use cases for security scenarios of LDP applications that can be used as the input to a later initiative that will be focused on developing standard security mechanisms for LDP applications.</p>
- <!-- TODO: link to Access Control Note -->
- </section>
-
- <section>
- <h1 id="ldpc">LDP Implementations</h1>
- A list of implementations that plan to be LDP compliant is available in the LDP Implementations <a href="https://www.w3.org/wiki/LDP_Implementations">wiki page</a>. The <a href="http://www.w3.org/2012/ldp/hg/tests/reports/ldp.html">Linked Data Platform 1.0 - Implementation Reports</a> provide the coverage of the specification by each LDP implementation.
- </section>
-
- <section>
- <h1 id="next">What To Read Next</h1>
- The primer only provide an overview of the Linked Data Platform specifications. LDP WG has produced following documents that contribute to the Linked Data Platform specification.
-
- <ul>
- <li><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/TR/ldp-ucr.html">Linked Data Platform Use Cases and Requirements</a> [[LDP-UCR]]</li>
- <li><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html">Linked Data Platform 1.0 specifcation</a> [[LDP]]</li>
- <li><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html">LDP Best Practices and Guidelines</a> [[LDP-BP]]</li>
- <li><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/Test%20Cases/LDP%20Test%20Cases.html">Linked Data Platform 1.0 Test Cases</a>[[LDP-TESTS]]</li>
- </ul>
-
- </section>
-
- <section class='appendix'>
- <h2>Acknowledgements</h2>
- <p>Many thanks to John Arwe (IBM), Ashok Malhotra (Oracle), and Henry Story (Apache Software Foundation) for their thorough review on the LDP Primer document and proposed corrections. We also like to thank all members of the Linked Data Platform WG for the valuable feedback. </p>
- </section>
-
- <section class='appendix informative' id="history">
- <h1>Change History</h1>
- <p>The change history is up to the editors to insert a brief summary of changes, ordered by most recent changes first and with heading from which public draft it has been changed from.
- </p>
- <ul>
- <li>2014-06-16 - Addressing the comments and feedback provided by Ashok, John, and Henry.</li>
- <li>2013-08-05 - Providing JSON-LD representations of the examples.</li>
- <li>2013-07-03 - Moving the content from the wiki to the note.</li>
- </ul>
- </section>
-
-</body>
-
-</html>
-