--- a/ldp-primer/ldp-primer.html Wed Sep 11 11:54:36 2013 -0400
+++ b/ldp-primer/ldp-primer.html Wed Sep 11 23:34:40 2013 -0400
@@ -1,1 +1,1 @@
-<?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', '');
},500)
}
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' async></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.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-wg",
// 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: "https://dvcs.w3.org/hg/ldpwg/raw-file/tip/ldp-bp/ldp-bp.html",
authors: [
"Cody Burleson",
"Nandana Mihindukulasooriya"
],
status: "WD",
deliveredBy: [
"http://www.w3.org/2012/ldp/"
],
publisher: "W3C"
},
"LDP-TESTS": {
title: "Linked Data Platform 1.0 Test Cases",
href: "https://dvcs.w3.org/hg/ldpwg/raw-file/tip/Test%20Cases/LDP%20Test%20Cases.html",
authors: [
"Raúl García-Castro"
],
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 Linked Data Platform (LDP), including the basic concepts
of LDP including Linked Data Platform Resource (LDPR) and Linked Data Platform Container (LDPC)
and their affordances, and a running example showing how an LDP client can interact with a LDP server
in the context of read-write Linked Data application i.e. how to HTTP for accessing, updating,
creating and deleting resources from servers that expose their resources as Linked Data.
</section>
<section id="intro-section">
<h1 id="intro">Introduction</h1>
<p>Linked Data is a universal approach for handling data which fundamentally includes the notion linking between data items.
Much like the Web is giant network of interlinked documents for a human reader, the graph of Linked Data in the Web is a
data layer on top of which applications are delivered, information is modified, processed, visualized and shared.
</p>
<p> Linked Data Platform specification discusses standard HTTP and RDF techniques and best practices that you should use, and
anti-patterns you should avoid, when constructing clients and servers that read and write Linked Data resources.
</p>
<p>The Primer aims to provide introductory examples and guidance in the use of the LDP protocol. For a systematic account 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]].</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>Commonly used namespace prefixes omitted from the Turtle serialisations:</p>
<pre style="word-wrap: break-word; white-space: pre-wrap;">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix wdrs: <http://www.w3.org/2007/05/powder-s#> .
@prefix bt: <http://example.org/vocab/bugtracker#> . </pre>
<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> The LDP consists of two main building blocks: Linked Data Platform Resource (LDPR) and
Linked Data Platform Container (LDPC).Any HTTP resource whose state is represented in RDF that conforms to the simple lifecycle patterns and conventions in LDP
specification is an LDPR. It is recommended that LDPRs reuse existing vocabularies instead of creating their own duplicate
vocabulary terms. It is also recommended that LDPRs have at least one rdf:type set explicitly to make the representations
more useful to client applications that don’t support inferencing. For example, a FOAF file of a person as shown in Example 1
can be an example of an LDPR . It uses terms from Dublin Core [[DC-TERMS]], Friend of a Friend [[FOAF]] vocabularies.
</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<pre title="An example LDPR" class='example' data-include='ldpr_ex.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p> Linked Data Platform Container (LDPC) is a specialization of an LDPR. An LDPC is a collection of same-subject, same-predicate triples which is uniquely identified by a URI that responds to client requests for creation, modification, and enumeration of its members.
For example, a set of friends of a person can be a represented as an LDPC as shown in Example 2 that contains a collection of triples
with the pattern <code><#friends, foaf:member, ?friend> </code>.
</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<pre title="An example LDPC" class='example' data-include='ldpc_ex.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<pre title="A member resource of LDPC in Example 2" class='example' data-include='ldpc_ex_m.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p>
Elements of the collection of same-subject, same-predicate triples are called Membership triples or simply members of the LDPC. Several predicates
of the LDPC ldp:membershipSubject, ldp:membershipPredicate, ldp:membershipObject defines the different aspects of the membership relation.
</p>
<p> Members of an LDPC does not have to be LDPRs. Any HTTP resource can be a member for an LDPC. For example,
</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<pre title="An example LDPC with non-LDPRs" class='example' data-include='ldpc_ex_non_ldpr.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p>
Use cases that motivated LDP specification varies from just publishing a dataset as Linked Data with advanced features as pagination,
providing read/write access to using Linked Data for application integration. The Linked Data Platform Use Cases and Requirements document provides
a more detailed information on the use cases that motivated the LDP specification.
</p>
<p>There will be several categories of systems implementing the LDP specification. Two main categories of the LDP servers include:</p>
<dl class="glossary">
<dt>Generic / vanilla LDP servers</dt>
<dd>RDF storage systems that allow interacting with their resources by means of the LDP specification. These servers do not impose any restriction on LDPRs.</dd>
<dt>Application specific LDP severs </dt>
<dd>Systems exposing their data using the LDP specification. These systems impose restrictions on LDPRs since they have an underlying business logic and data model.</dd>
</dl>
</section>
<section id="bugtracker">
<h1><a id="bugtracker">Bug Tracker Example</a></h1>
<p>
This section provides 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.
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. We can re-use simple domain vocabulary,
e.g. has_bug or related, to express our data. LDP provides the additional interaction capability in the protocol to perform dynamic
evolution of knowledge representation.
</p>
<p>RESTful APIs are often documented by through listing valid operations operating on URLs described as templates. 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">/app/</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'>/app/{product-id}/</div></td>
<td>GET</td>
<td>Lists the 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'>/app/{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'>/*/*</div></td>
<td>OPTIONS</td>
<td>Discover the allowed operations over a resource</td>
</tr>
<tr>
<td>HEAD</td>
<td>Only retrieve metainformation about a resource</td>
</tr>
</tbody>
</table>
<section id="navandret">
<h2>Navigation and Retreival</h2>
<b>Lookup a Product (LDPC?)</b>
<p> One of the main use cases of the example bug tracker is to list of the bugs of a given product. Assuming
that a user got a URL of a product by out of band means, one can look it up to get more information including
the bugs associated with it.</p>
<table>
<tr>
<td class="col1"><img src="product_lookup.png" /></td>
<td>
<p>To get the description of the product, a client can do a GET request on the URI of the known product resource. LDPR
servers should provide text/turtle representations of the requested LDPRs and may provide RDF format representations
using standard HTTP content negotiation. </p>
<pre class="example" title="Product lookup request"
data-include='product_lookup_req.txt' data-oninclude='fixCode'></pre>
<p>If the product resource is available, the server responds with the representation of the resource using the requested media type,
<code>text/turtle</code> in this case.</p>
<pre title="HTTP response for product lookup" class='example' data-include='product_lookup_resp.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p>
The project description resource contains both information about the project such as the title and the information about members of the product LDPC
i.e. the bugs associated with the product.
</p>
<p>Looking up a bug is similar to looking up a product. </p>
<table>
<tr>
<td class="col1"><img src="bug_lookup.png" /></td>
<td>
<p>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>
</td>
</tr>
</table>
</section>
<section>
<h3 id="BugCreate">Creation</h3>
<p>Continuing from the previous example, we can report a Bug against 'product1' by creating a Bug LDPR under the 'Product' LDPC.
The client POSTs a representation of a Bug to the Bug Tracker LDPC. </p>
<table>
<tr>
<td class="col1"><img src="bug_create.png" /></td>
<td>
<p>The client POSTs a representation of a Bug to the Bug Tracker LDPC.</p>
<pre title="A request for creating a bug"
class='example' data-include='bug_create_req.txt'
data-oninclude='fixCode'></pre>
<p>If the create 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: /app/product1/67
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<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='bug_create_s1.txt'
data-oninclude='fixCode'></pre>
<p>And 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 being POSTed.</p>
<pre title="The state of the bug LDPR"
class='example' data-include='bug_create_s2.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="BugUpdate">Update</h3>
<p> TODO - Description </p>
<table>
<tr>
<td class="col1"><img src="bug_update.png" /></td>
<td>
<p>TODO - Description</p>
<pre title="A request for updating a bug"
class='example' data-include='bug_update_req.txt'
data-oninclude='fixCode'></pre>
<p>If the update is successful, the server will respond with a success status and a new etag.</p>
<pre class="example">
HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="BugDelete">Deletion</h3>
<p> TODO - Description </p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO - Description</p>
<pre class="example">
DELETE /app/product1/bug3 HTTP/1.1
Host: example.org
</pre>
<p>If the update is successful, the server will respond with a success status and a new etag.</p>
<pre class="example">
HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="meta-structure">Editing Structure (change name!)</h3>
<p>If the bug tracker allows creating new Products in the tracker, that can done by posting a representation of a new Product to the
Bug Tracker container.</p>
<table>
<tr>
<td class='col1'><img src="replace.png" /></td>
<td>
<p>The status of the bug tracker before creating the new product.</p>
<pre title="The state of the Bug Tracker LDPC"
class='example' data-include='product_create_s1.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client POSTs a representation of a Product to the Bug Tracker LDPC.</p>
<pre title="A request for creating a product"
class='example' data-include='product_create_req.txt'
data-oninclude='fixCode'></pre>
<p>If the create is successful, the server responds with location of the newly created resource.</p>
<pre title="The response after creating new product" class="example">
HTTP/1.1 201 Created
Location: /app/product2
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td></td><td>
<p>After creation of this new container, 'Product A', the representation of the 'Tracker' container will be</p>
<pre title="The state of the Bug Tracker after the product creation"
class='example' data-include='product_create_s2.txt'
data-oninclude='fixCode'></pre>
<p>and the 'Product A' will have the following representation.</p>
<pre title="The state of the new Product"
class='example' data-include='product_create_s3.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="ProductLookup">Operation Discovery</h3>
<p>
Assuming that a user got the URL of the product by out of band means, a starting point would be to discover
which operations can be performed on the product resource.
</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client does an OPTIONS with the URI of a known product description resource.</p>
<pre class="example">OPTIONS /app/product1/ HTTP/1.1
Host: example.org
</pre>
<p>If the product description resource is available, the server responds with the allowed HTTP operations on the product
resource along with some other metadata.</p>
<div class="turtle">
<pre title="HTTP response for OPTIONS on a product" class='example'>
HTTP/1.1 200 OK
Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
Accept-Post: text/turtle, application/ld+json
Accept-Patch: example/patch
Link: <http://www.w3.org/ns/ldp/Resource>; rel="type"
Link: <?nonMemberProperties>;rel="http://www.w3.org/ns/ldp#nonMemberResource"
Content-Length: 0
</pre>
</div>
</td>
</tr>
</table>
<p> According to the response, HTTP operations {OPTIONS,GET,POST,PUT,PATCH} are allowed on the product description resource.
In addition to the allowed operations, Accept-Post and Accept-Patch provides which media types are supported by respective operations.
The rel="type" Link header advertises that this is resource supports LDP protocol and the the rel="ldp:nonMemberResource" provides a link
to the non-member resource of this product description.
</p>
</section>
<section id="paging">
<h3>Pagination</h3>
<p>It sometimes happens that a resource is too large to reasonably transmit its representation in a single HTTP response. For example, if the
bug resource in our example includes comments, It might happen that it may be become too large. To address this problem, LDPRs should support
a technique called Paging.</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>If a client does a get on an LDPR that supports paging, it will be redirected to the first page of the resource.</p>
<pre class="example">
GET /app/product1/bug3 HTTP/1.1
Host: example.org
</pre>
<pre class="example">
HTTP/1.1 303 See Other
Location: /app/product1/bug3?firstpage
</pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>Alternatively if the client wants to know in advance whether the resource is paged or not, it can do an OPTIONS request on the LDPR URI</p>
<pre class="example">
OPTIONS /app/product1/bug3 HTTP/1.1
Host: example.org
</pre>
<p>If the resource is paged, the response contains a HTTP Link header with rel="first"; and the target URI of that header would be the URL of
the first page resource. </p>
<pre class="example">
HTTP/1.1 200 OK
Allow: OPTIONS,HEAD,GET,PUT,PATCH
Accept-Patch: example/patch
Link: <http://www.w3.org/ns/ldp/Resource>; rel="type"
Link: </app/product1/bug3?firstpage>; rel="first"
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>After knowing the URL of the first page resource, the client can retrieve it using a HTTP GET</p>
<pre class="example">
GET /app/product1/bug3?firstpage HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre>
<pre title="HTTP response for getting the first page resource"
class='example' data-include='paging_page1_res.txt'
data-oninclude='fixCode'></pre>
<p>The first page contains a link to the second page with LDPR as the subject,
ldp:nextPage as the predicate and the subsequent page as the object.</p>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The second page can be retrieved the same way as the first page was retrieved.</p>
<pre class="example">
GET /app/product1/bug3?secondPage HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre>
<pre title="HTTP response for getting the second page resource"
class='example' data-include='paging_page2_res.txt'
data-oninclude='fixCode'></pre>
<p>The last page of resource contains with LDPR as the subject,
ldp:nextPage as the predicate and the rdf:nil as the object.</p>
</td>
</tr>
</table>
</section>
<section id="odering">
<h3>Ordering</h3>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>There are many cases where an ordering of the members of the container is important. </p>
<pre class="example">
GET /app/product1?firstPage HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre>
<pre title="The representation of an ordered LDPC"
class='example' data-include='ordered_ldpc_resp.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<section id="binary-res">
<h3>Binary resources</h3>
<b>Creating a binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>We have an LDPC which we can use to create binary resources</p>
<pre title="The state of the attachments LDPC"
class='example' data-include='attachments_s1.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td><img src="replace.png" /></td>
<td>
<p>The client POSTs a binary resource to the LDPC</p>
<pre title="A request for creating a product"
class='example'>POST /app/product1/bug3/attachments/ HTTP/1.1
Host: example.org
Content-Type: image/png
Slug: login-page.png
Content-Length: 1254
#### binary data #####
</pre>
<p>If the create is successful, the server it responds with a Location header and a Link header to
the automatically created metadata LDPR.</p>
<pre title="A response after creating new a binary resource" class='example'>HTTP/1.1 201 Created
Location: /app/product1/bug3/attachments/login-page.png
Link: </app/product1/bug3/attachments/1>; rel="meta"
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td></td>
<td>
<p>After the creation, LDPC representation looks like</p>
<pre title="The state of the attachments LDPC after creation"
class='example' data-include='attachments_s2.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<b>Accessing the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client can retrieve the binary resource by doing a GET on the binary resource URI.</p>
<pre class="example">GET /app/product1/bug3/attachments/login-page.png HTTP/1.1
Host: example.org
Accept: image/png
</pre>
<p>LDPR server responds with</p>
<pre title="HTTP response for getting the binary resource"
class='example'>HTTP/1.1 200 OK
Content-Type: image/png
Link: </app/product1/bug3/attachments/1>; rel="meta"
ETag: W/"123456789"
#### binary data #####
</pre>
</td>
</tr>
</table>
</section>
<b>Accessing the metadata about the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client can retrieve the metadata of the binary resource by doing a GET on the metadata-LDPR URI.</p>
<pre class="example">GET /app/product1/bug3/attachments/1
Host: example.org
Accept: text/turtle
</pre>
<p>LDPR server responds with</p>
<pre title="HTTP response for getting the binary resource"
class='example' data-include='attachments_m_get_res.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<b>Updating the metadata about the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO</p>
<pre title="Updating the metadata of the binary resource"
class='example' data-include='attachments_m_update_req.txt'
data-oninclude='fixCode'></pre>
<p>LDPR server responds with</p>
<pre class="example">HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
</td>
</tr>
</table>
</section>
<b>Deleting the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO</p>
<pre class="example"> DELETE /app/product1/bug3/attachments/login-page.png HTTP/1.1
Host: example.org
</pre>
<pre class="example">HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
<pre class="example">GET /app/product1/bug3/attachments/login-page.png HTTP/1.1
Host: example.org
</pre>
<pre class="example">HTTP/1.1 410 Gone
</pre>
<pre class="example"> GET /app/product1/bug3/attachments/1
Host: example.org
</pre>
<pre class="example">HTTP/1.1 410 Gone
</pre>
</td>
</tr>
</table>
</section>
</section>
</section>
<section>
<h1 id="advexamples">Advanced Examples</h1>
<section>
<h3 id="ldpmemx">Uses of membership{Subject,Predicate,Object} predicates </h3>
<p>In most of the previous examples we kept the ldp:membershipSubject as the LDPC itself and ldp:membershipObject as the ldp:MemberSubject. However, these
predicates can be used to change the semantics of the membership relationship in LDPCs. </p>
<p class="note">TO DO: A small note on document vs Thing separation linking to <a href="http://www.w3.org/TR/webarch/#id-resources">Web Arch</a>,
, <a href="http://www.w3.org/TR/cooluris/#semweb">Cool URIs</a>, <a href="http://www.w3.org/TR/urls-in-data/#landing-pages">URLs in Data</a>.</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>If the separation between real world resource and information is important, the product description of the previous Bug Tracker example can
be alternatively designed as following.</p>
<pre title="Representation of the product description"
class='example' data-include='product_alt_s1.txt'
data-oninclude='fixCode'></pre>
<p>In the above example, the product description information resource is explicitly seperated from the real world product resource. Now the RDF representation
contains information about both the information resource that is identified by the URI </app/product1/> and the real world resource identified by the
URI </app/product1/#it>. </p>
<p>With this seperation, now the ldp:membershipSubject of the container is not the container URI itself but </app/product1/#it>. The effect of these is that
membership relation triples added when new resources are POSTed to this container will now have the subject </app/product1/#it> not the container URI. Further,
ldp:membershipObject of this container is foaf:primaryTopic. Thus, the object of the membership triple will not be the newly created resource but the foaf:primaryTopic
defined inside that newly created resource as shown in the following example. </p>
<pre title="HTTP request for creating a new bug report"
class='example' data-include='bug_alt_create_req.txt'
data-oninclude='fixCode'></pre>
<p>And the server will respond with the URI of the newly created information resource in the Location header.</p>
<pre title="Representation of the newly created bug"
class='example' data-oninclude='fixCode'>
HTTP/1.1 201 Created
Location: /app/product1/67
Content-Length: 0
</pre>
<p>After the resource creation, the representations of the LDPC and newly created LDPR would be </p>
<pre title="Representation of the LDPC"
class='example' data-oninclude='fixCode' data-include='product_alt_s2.txt'></pre>
<pre title="Representation of the newly created bug"
class='example' data-oninclude='fixCode' data-include='bug_alt_s1.txt'></pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="mempredinv">ldp:membershipPredicateInverse predicate</h3>
<p>In sometimes the membership relationship can defined in a way such that the container is becomes the object of the membership triple. For example,
in our example, if the membership triple was like < bug, bt:relatedProduct, product > the product container would look like</p>
<pre title="Representation of an LDPC with ldp:membershipPredicateInverse predicate"
class='example' data-oninclude='fixCode' data-include='product_inv_s1.txt'></pre>
<p>TODO - Find a better example</p>
</section>
<section id="res-inlining">
<h3>Resource Inlining</h3>
<p> TODO - Description </p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO - Description</p>
<pre title="A HTTP request to a LDPR with inlined resources"
class='example' data-oninclude='fixCode' data-include='res_inline_req.txt'></pre>
<p> </p>
<pre title="A HTTP response from a LDPR with inlined resources"
class='example' data-oninclude='fixCode' data-include='res_inline_res.txt'></pre>
</td>
</tr>
</table>
</section>
<section id="mem-inlining">
<h3>Member Inlining</h3>
</section>
</section>
<section>
<h1 id="ldpc">LDP Implementations</h1>
A list of implementations that plan to be LDP compliant is available in the LDP Implementations wiki page.
LDP Implementation report provides 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>Linked Data Platform 1.0 Primer (This document)</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 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>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>
\ No newline at end of file
+<?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', '');
},500)
}
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' async></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.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-wg",
// 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: "https://dvcs.w3.org/hg/ldpwg/raw-file/tip/ldp-bp/ldp-bp.html",
authors: [
"Cody Burleson",
"Nandana Mihindukulasooriya"
],
status: "WD",
deliveredBy: [
"http://www.w3.org/2012/ldp/"
],
publisher: "W3C"
},
"LDP-TESTS": {
title: "Linked Data Platform 1.0 Test Cases",
href: "https://dvcs.w3.org/hg/ldpwg/raw-file/tip/Test%20Cases/LDP%20Test%20Cases.html",
authors: [
"Raúl García-Castro"
],
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 Linked Data Platform (LDP), including the basic concepts
of LDP including Linked Data Platform Resource (LDPR) and Linked Data Platform Container (LDPC)
and their affordances, and a running example showing how an LDP client can interact with a LDP server
in the context of read-write Linked Data application i.e. how to HTTP for accessing, updating,
creating and deleting resources from servers that expose their resources as Linked Data.
</section>
<section id="intro-section">
<h1 id="intro">Introduction</h1>
<p>Linked Data is a universal approach for handling data which fundamentally includes the notion linking between data items.
Much like the Web is giant network of interlinked documents for a human reader, the graph of Linked Data in the Web is a
data layer on top of which applications are delivered, information is modified, processed, visualized and shared.
</p>
<p> Linked Data Platform specification discusses standard HTTP and RDF techniques and best practices that you should use, and
anti-patterns you should avoid, when constructing clients and servers that read and write Linked Data resources.
</p>
<p>The Primer aims to provide introductory examples and guidance in the use of the LDP protocol. For a systematic account 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]].</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>Commonly used namespace prefixes omitted from the Turtle serialisations:</p>
<pre style="word-wrap: break-word; white-space: pre-wrap;">
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix wdrs: <http://www.w3.org/2007/05/powder-s#> .
@prefix bt: <http://example.org/vocab/bugtracker#> . </pre>
<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> The LDP consists of two main building blocks: Linked Data Platform Resource (LDPR) and
Linked Data Platform Container (LDPC).Any HTTP resource whose state is represented in RDF that conforms to the simple lifecycle patterns and conventions in LDP
specification is an LDPR. It is recommended that LDPRs reuse existing vocabularies instead of creating their own duplicate
vocabulary terms. It is also recommended that LDPRs have at least one rdf:type set explicitly to make the representations
more useful to client applications that don’t support inferencing. For example, a FOAF file of a person as shown in Example 1
can be an example of an LDPR . It uses terms from Dublin Core [[DC-TERMS]], Friend of a Friend [[FOAF]] vocabularies.
</p>
<table>
<tr>
<td class="col1"><img src="nandana_foaf.png" /></td>
<td>
<pre title="An example LDPR" class='example' data-include='ldpr_ex.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p> Linked Data Platform Container (LDPC) is a specialization of an LDPR. An LDPC is a collection of same-subject, same-predicate triples which is uniquely identified by a URI that responds to client requests for creation, modification, and enumeration of its members.
For example, a set of friends of a person can be a represented as an LDPC as shown in Example 2 that contains a collection of triples
with the pattern <code><#friends, foaf:member, ?friend> </code>.
</p>
<table>
<tr>
<td class="col1"><img src="nandana_friends.png" /></td>
<td>
<pre title="An example LDPC" class='example' data-include='ldpc_ex.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td class="col1"><img src="roger.png" /></td>
<td>
<pre title="A member resource of LDPC in Example 2" class='example' data-include='ldpc_ex_m.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p>
Elements of the collection of same-subject, same-predicate triples are called Membership triples or simply members of the LDPC. Several predicates
of the LDPC ldp:membershipSubject, ldp:membershipPredicate, ldp:membershipObject defines the different aspects of the membership relation.
</p>
<p> Members of an LDPC does not have to be LDPRs. Any HTTP resource can be a member for an LDPC. For example,
</p>
<table>
<tr>
<td class="col1"><img src="photos.png" /></td>
<td>
<pre title="An example LDPC with non-LDPRs" class='example' data-include='ldpc_ex_non_ldpr.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p>
Use cases that motivated LDP specification varies from just publishing a dataset as Linked Data with advanced features as pagination,
providing read/write access to using Linked Data for application integration. The Linked Data Platform Use Cases and Requirements document provides
a more detailed information on the use cases that motivated the LDP specification.
</p>
<p>There will be several categories of systems implementing the LDP specification. Two main categories of the LDP servers include:</p>
<dl class="glossary">
<dt>Generic / vanilla LDP servers</dt>
<dd>RDF storage systems that allow interacting with their resources by means of the LDP specification. These servers do not impose any restriction on LDPRs.</dd>
<dt>Application specific LDP severs </dt>
<dd>Systems exposing their data using the LDP specification. These systems impose restrictions on LDPRs since they have an underlying business logic and data model.</dd>
</dl>
</section>
<section id="bugtracker">
<h1><a id="bugtracker">Bug Tracker Example</a></h1>
<p>
This section provides 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.
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. We can re-use simple domain vocabulary,
e.g. has_bug or related, to express our data. LDP provides the additional interaction capability in the protocol to perform dynamic
evolution of knowledge representation.
</p>
<p>RESTful APIs are often documented by through listing valid operations operating on URLs described as templates. 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">/app/</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'>/app/{product-id}/</div></td>
<td>GET</td>
<td>Lists the 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'>/app/{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'>/*/*</div></td>
<td>OPTIONS</td>
<td>Discover the allowed operations over a resource</td>
</tr>
<tr>
<td>HEAD</td>
<td>Only retrieve metainformation about a resource</td>
</tr>
</tbody>
</table>
<p class="note">Do we want to say something about suggested, user-friendly URIs ? </p>
<section id="navandret">
<h2>Navigation and Retreival</h2>
<b>Lookup a Product (LDPC?)</b>
<p> One of the main use cases of the example bug tracker is to list of the bugs of a given product. Assuming
that a user got a URL of a product by out of band means, one can look it up to get more information including
the bugs associated with it.</p>
<table>
<tr>
<td class="col1"><img src="product_lookup.png" /></td>
<td>
<p>To get the description of the product, a client can do a GET request on the URI of the known product resource. LDPR
servers should provide text/turtle representations of the requested LDPRs and may provide RDF format representations
using standard HTTP content negotiation. </p>
<pre class="example" title="Product lookup request"
data-include='product_lookup_req.txt' data-oninclude='fixCode'></pre>
<p>If the product resource is available, the server responds with the representation of the resource using the requested media type,
<code>text/turtle</code> in this case.</p>
<pre title="HTTP response for product lookup" class='example' data-include='product_lookup_resp.txt' data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
<p>
The project description resource contains both information about the project such as the title and the information about members of the product LDPC
i.e. the bugs associated with the product.
</p>
<p>Looking up a bug is similar to looking up a product. </p>
<table>
<tr>
<td class="col1"><img src="bug_lookup.png" /></td>
<td>
<p>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>
</td>
</tr>
</table>
</section>
<section>
<h3 id="BugCreate">Creation</h3>
<p>Continuing from the previous example, we can report a Bug against 'product1' by creating a Bug LDPR under the 'Product' LDPC.
The client POSTs a representation of a Bug to the Bug Tracker LDPC. </p>
<table>
<tr>
<td class="col1"><img src="bug_create.png" /></td>
<td>
<p>The client POSTs a representation of a Bug to the Bug Tracker LDPC.</p>
<pre title="A request for creating a bug"
class='example' data-include='bug_create_req.txt'
data-oninclude='fixCode'></pre>
<p>If the create 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: /app/product1/67
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td class="col1"><img src="product_postcreate.png" /></td>
<td>
<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='bug_create_s1.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td class="col1"><img src="bug67.png" /></td>
<td>
<p>And 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 being POSTed.</p>
<pre title="The state of the bug LDPR"
class='example' data-include='bug_create_s2.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="BugUpdate">Update</h3>
<p> TODO - Description </p>
<table>
<tr>
<td class="col1"><img src="bug_update.png" /></td>
<td>
<p>TODO - Description</p>
<pre title="A request for updating a bug"
class='example' data-include='bug_update_req.txt'
data-oninclude='fixCode'></pre>
<p>If the update is successful, the server will respond with a success status and a new etag.</p>
<pre class="example">
HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="BugDelete">Deletion</h3>
<p> TODO - Description </p>
<table>
<tr>
<td class="col1"><img src="bug_delete.png" /></td>
<td>
<p>TODO - Description</p>
<pre class="example">
DELETE /app/product1/bug3 HTTP/1.1
Host: example.org
</pre>
<p>If the update is successful, the server will respond with a success status and a new etag.</p>
<pre class="example">
HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="meta-structure">Structural Manipulation</h3>
<p>If the bug tracker allows creating new Products in the tracker, that can done by posting a representation of a new Product to the Bug Tracker container. In this example the client includes the necessary ldp membership properties making the new Product a container for Bug resources.</p>
<table>
<tr>
<td class='col1'><img src="app.png" /></td>
<td>
<p>The status of the bug tracker before creating the new product.</p>
<pre title="The state of the Bug Tracker LDPC"
class='example' data-include='product_create_s1.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td class="col1"><img src="app_post.png" /></td>
<td>
<p>The client POSTs a representation of a Product to the Bug Tracker LDPC.</p>
<pre title="A request for creating a product"
class='example' data-include='product_create_req.txt'
data-oninclude='fixCode'></pre>
<p>If the create is successful, the server responds with location of the newly created resource.</p>
<pre title="The response after creating new product" class="example">
HTTP/1.1 201 Created
Location: /app/product2
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td></td><td>
<p>After creation of this new container, 'product2', the representation of the 'Tracker' container will be</p>
<pre title="The state of the Bug Tracker after the product creation"
class='example' data-include='product_create_s2.txt'
data-oninclude='fixCode'></pre>
<p>and the 'product2' will have the following representation.</p>
<pre title="The state of the new Product"
class='example' data-include='product_create_s3.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="ProductLookup">Operation Discovery</h3>
<p>
Assuming that a user got the URL of the product by out of band means, a starting point would be to discover
which operations can be performed on the product resource.
</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client does an OPTIONS with the URI of a known product description resource.</p>
<pre class="example">OPTIONS /app/product1/ HTTP/1.1
Host: example.org
</pre>
<p>If the product description resource is available, the server responds with the allowed HTTP operations on the product
resource along with some other metadata.</p>
<div class="turtle">
<pre title="HTTP response for OPTIONS on a product" class='example'>
HTTP/1.1 200 OK
Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
Accept-Post: text/turtle, application/ld+json
Accept-Patch: example/patch
Link: <http://www.w3.org/ns/ldp/Resource>; rel="type"
Link: <?nonMemberProperties>;rel="http://www.w3.org/ns/ldp#nonMemberResource"
Content-Length: 0
</pre>
</div>
</td>
</tr>
</table>
<p> According to the response, HTTP operations {OPTIONS,GET,POST,PUT,PATCH} are allowed on the product description resource.
In addition to the allowed operations, Accept-Post and Accept-Patch provides which media types are supported by respective operations.
The rel="type" Link header advertises that this is resource supports LDP protocol and the the rel="ldp:nonMemberResource" provides a link
to the non-member resource of this product description.
</p>
</section>
<section id="paging">
<h3>Pagination</h3>
<p>It sometimes happens that a resource is too large to reasonably transmit its representation in a single HTTP response. For example, if the
bug resource in our example includes comments, It might happen that it may be become too large. To address this problem, LDPRs should support
a technique called Paging.</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>If a client does a get on an LDPR that supports paging, it will be redirected to the first page of the resource.</p>
<pre class="example">
GET /app/product1/bug3 HTTP/1.1
Host: example.org
</pre>
<pre class="example">
HTTP/1.1 303 See Other
Location: /app/product1/bug3?firstpage
</pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>Alternatively if the client wants to know in advance whether the resource is paged or not, it can do an OPTIONS request on the LDPR URI</p>
<pre class="example">
OPTIONS /app/product1/bug3 HTTP/1.1
Host: example.org
</pre>
<p>If the resource is paged, the response contains a HTTP Link header with rel="first"; and the target URI of that header would be the URL of
the first page resource. </p>
<pre class="example">
HTTP/1.1 200 OK
Allow: OPTIONS,HEAD,GET,PUT,PATCH
Accept-Patch: example/patch
Link: <http://www.w3.org/ns/ldp/Resource>; rel="type"
Link: </app/product1/bug3?firstpage>; rel="first"
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>After knowing the URL of the first page resource, the client can retrieve it using a HTTP GET</p>
<pre class="example">
GET /app/product1/bug3?firstpage HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre>
<pre title="HTTP response for getting the first page resource"
class='example' data-include='paging_page1_res.txt'
data-oninclude='fixCode'></pre>
<p>The first page contains a link to the second page with LDPR as the subject,
ldp:nextPage as the predicate and the subsequent page as the object.</p>
</td>
</tr>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The second page can be retrieved the same way as the first page was retrieved.</p>
<pre class="example">
GET /app/product1/bug3?secondPage HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre>
<pre title="HTTP response for getting the second page resource"
class='example' data-include='paging_page2_res.txt'
data-oninclude='fixCode'></pre>
<p>The last page of resource contains with LDPR as the subject,
ldp:nextPage as the predicate and the rdf:nil as the object.</p>
</td>
</tr>
</table>
</section>
<section id="odering">
<h3>Ordering</h3>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>There are many cases where an ordering of the members of the container is important. </p>
<pre class="example">
GET /app/product1?firstPage HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre>
<pre title="The representation of an ordered LDPC"
class='example' data-include='ordered_ldpc_resp.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<section id="binary-res">
<h3>Binary resources</h3>
<b>Creating a binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>We have an LDPC which we can use to create binary resources</p>
<pre title="The state of the attachments LDPC"
class='example' data-include='attachments_s1.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
<tr>
<td><img src="replace.png" /></td>
<td>
<p>The client POSTs a binary resource to the LDPC</p>
<pre title="A request for creating a product"
class='example'>POST /app/product1/bug3/attachments/ HTTP/1.1
Host: example.org
Content-Type: image/png
Slug: login-page.png
Content-Length: 1254
#### binary data #####
</pre>
<p>If the create is successful, the server it responds with a Location header and a Link header to
the automatically created metadata LDPR.</p>
<pre title="A response after creating new a binary resource" class='example'>HTTP/1.1 201 Created
Location: /app/product1/bug3/attachments/login-page.png
Link: </app/product1/bug3/attachments/1>; rel="meta"
Content-Length: 0
</pre>
</td>
</tr>
<tr>
<td></td>
<td>
<p>After the creation, LDPC representation looks like</p>
<pre title="The state of the attachments LDPC after creation"
class='example' data-include='attachments_s2.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<b>Accessing the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client can retrieve the binary resource by doing a GET on the binary resource URI.</p>
<pre class="example">GET /app/product1/bug3/attachments/login-page.png HTTP/1.1
Host: example.org
Accept: image/png
</pre>
<p>LDPR server responds with</p>
<pre title="HTTP response for getting the binary resource"
class='example'>HTTP/1.1 200 OK
Content-Type: image/png
Link: </app/product1/bug3/attachments/1>; rel="meta"
ETag: W/"123456789"
#### binary data #####
</pre>
</td>
</tr>
</table>
</section>
<b>Accessing the metadata about the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>The client can retrieve the metadata of the binary resource by doing a GET on the metadata-LDPR URI.</p>
<pre class="example">GET /app/product1/bug3/attachments/1
Host: example.org
Accept: text/turtle
</pre>
<p>LDPR server responds with</p>
<pre title="HTTP response for getting the binary resource"
class='example' data-include='attachments_m_get_res.txt'
data-oninclude='fixCode'></pre>
</td>
</tr>
</table>
</section>
<b>Updating the metadata about the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO</p>
<pre title="Updating the metadata of the binary resource"
class='example' data-include='attachments_m_update_req.txt'
data-oninclude='fixCode'></pre>
<p>LDPR server responds with</p>
<pre class="example">HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
</td>
</tr>
</table>
</section>
<b>Deleting the binary resource</b>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO</p>
<pre class="example"> DELETE /app/product1/bug3/attachments/login-page.png HTTP/1.1
Host: example.org
</pre>
<pre class="example">HTTP/1.1 204 No Content
ETag: W/"123456790"
</pre>
<pre class="example">GET /app/product1/bug3/attachments/login-page.png HTTP/1.1
Host: example.org
</pre>
<pre class="example">HTTP/1.1 410 Gone
</pre>
<pre class="example"> GET /app/product1/bug3/attachments/1
Host: example.org
</pre>
<pre class="example">HTTP/1.1 410 Gone
</pre>
</td>
</tr>
</table>
</section>
</section>
</section>
<section>
<h1 id="advexamples">Advanced Examples</h1>
<section>
<h3 id="ldpmemx">Uses of membership{Subject,Predicate,Object} predicates </h3>
<p>In most of the previous examples we kept the ldp:membershipSubject as the LDPC itself and ldp:membershipObject as the ldp:MemberSubject. However, these
predicates can be used to change the semantics of the membership relationship in LDPCs. </p>
<p class="note">TO DO: A small note on document vs Thing separation linking to <a href="http://www.w3.org/TR/webarch/#id-resources">Web Arch</a>,
, <a href="http://www.w3.org/TR/cooluris/#semweb">Cool URIs</a>, <a href="http://www.w3.org/TR/urls-in-data/#landing-pages">URLs in Data</a>.</p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>If the separation between real world resource and information is important, the product description of the previous Bug Tracker example can
be alternatively designed as following.</p>
<pre title="Representation of the product description"
class='example' data-include='product_alt_s1.txt'
data-oninclude='fixCode'></pre>
<p>In the above example, the product description information resource is explicitly seperated from the real world product resource. Now the RDF representation
contains information about both the information resource that is identified by the URI </app/product1/> and the real world resource identified by the
URI </app/product1/#it>. </p>
<p>With this seperation, now the ldp:membershipSubject of the container is not the container URI itself but </app/product1/#it>. The effect of these is that
membership relation triples added when new resources are POSTed to this container will now have the subject </app/product1/#it> not the container URI. Further,
ldp:membershipObject of this container is foaf:primaryTopic. Thus, the object of the membership triple will not be the newly created resource but the foaf:primaryTopic
defined inside that newly created resource as shown in the following example. </p>
<pre title="HTTP request for creating a new bug report"
class='example' data-include='bug_alt_create_req.txt'
data-oninclude='fixCode'></pre>
<p>And the server will respond with the URI of the newly created information resource in the Location header.</p>
<pre title="Representation of the newly created bug"
class='example' data-oninclude='fixCode'>
HTTP/1.1 201 Created
Location: /app/product1/67
Content-Length: 0
</pre>
<p>After the resource creation, the representations of the LDPC and newly created LDPR would be </p>
<pre title="Representation of the LDPC"
class='example' data-oninclude='fixCode' data-include='product_alt_s2.txt'></pre>
<pre title="Representation of the newly created bug"
class='example' data-oninclude='fixCode' data-include='bug_alt_s1.txt'></pre>
</td>
</tr>
</table>
</section>
<section>
<h3 id="mempredinv">ldp:membershipPredicateInverse predicate</h3>
<p>In sometimes the membership relationship can defined in a way such that the container is becomes the object of the membership triple. For example,
in our example, if the membership triple was like < bug, bt:relatedProduct, product > the product container would look like</p>
<pre title="Representation of an LDPC with ldp:membershipPredicateInverse predicate"
class='example' data-oninclude='fixCode' data-include='product_inv_s1.txt'></pre>
<p>TODO - Find a better example</p>
</section>
<section id="res-inlining">
<h3>Resource Inlining</h3>
<p> TODO - Description </p>
<table>
<tr>
<td class="col1"><img src="replace.png" /></td>
<td>
<p>TODO - Description</p>
<pre title="A HTTP request to a LDPR with inlined resources"
class='example' data-oninclude='fixCode' data-include='res_inline_req.txt'></pre>
<p> </p>
<pre title="A HTTP response from a LDPR with inlined resources"
class='example' data-oninclude='fixCode' data-include='res_inline_res.txt'></pre>
</td>
</tr>
</table>
</section>
<section id="mem-inlining">
<h3>Member Inlining</h3>
</section>
</section>
<section>
<h1 id="ldpc">LDP Implementations</h1>
A list of implementations that plan to be LDP compliant is available in the LDP Implementations wiki page.
LDP Implementation report provides 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>Linked Data Platform 1.0 Primer (This document)</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 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>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>
\ No newline at end of file