--- a/TR/NOTE-ldp-primer-20150421/Overview.html Mon Apr 20 14:44:30 2015 +0200
+++ b/TR/NOTE-ldp-primer-20150421/Overview.html Mon Apr 20 18:35:27 2015 +0200
@@ -515,7 +515,7 @@
</p>
<blockquote>
<p>Types of LDPRs:
- <img src="./images/resources.png">
+ <img src="./images/resources.png" alt="Types of LDPRs">
</p>
</blockquote>
<p>
@@ -650,17 +650,17 @@
<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>
- <div class="example"><div class="example-title"><span>Example 1</span>: Request - basic container retrieval</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /alice/ HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 1</span>: Request - basic container retrieval</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /alice/ HTTP/1.1
Host: example.org
Accept: text/turtle
</pre></div><div class="jsonld" style="font-family: sans-serif; display: none;">JSON-LD:</div><div class="jsonld" style="display: none;"><pre>GET /alice/ HTTP/1.1
Host: example.org
-Accept: application/ld+json</pre></div></pre></div>
+Accept: application/ld+json</pre></div></div></div>
<p>As her document storage was just created, it is an empty container. </p>
- <div class="example"><div class="example-title"><span>Example 2</span>: Response - basic container retrieval</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
+ <div class="example"><div class="example-title"><span>Example 2</span>: Response - basic container retrieval</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
Content-Type: text/turtle; charset=UTF-8
Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type", <http://www.w3.org/ns/ldp#Resource>; rel="type"
Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -691,7 +691,7 @@
"@id": "http://example.org/alice/",
"@type": [ "ldp:Container", "ldp:BasicContainer"],
"dcterms:title": "Alice’s data storage on the Web"
-}</pre></div></pre></div>
+}</pre></div></div></div>
<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>
@@ -733,7 +733,7 @@
<figcaption>Fig. <span class="figno">5</span> <span class="fig-title">Child Containers inside a Basic Container.</span></figcaption>
</figure>
- <div class="example"><div class="example-title"><span>Example 5</span>: State of Alice's document store before creating the photo (child) container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
+ <div class="example"><div class="example-title"><span>Example 5</span>: State of Alice's document store before creating the photo (child) container</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
<http://example.org/alice/> a ldp:Container, ldp:BasicContainer ;
@@ -748,10 +748,10 @@
"@type": [ "ldp:Container", "ldp:BasicContainer"],
"dcterms:title": "Alice’s data storage on the Web",
"ldp:contains": { "@id": "http://example.org/alice/foaf" }
-}</pre></div></pre></div>
+}</pre></div></div></div>
<p>To create a new container for managing photos, Alice POSTs a representation of a container (LDP-BC) to the root container. Alice expresses 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>
- <div class="example"><div class="example-title"><span>Example 6</span>: Request - creating a new container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST alice/ HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 6</span>: Request - creating a new container</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST alice/ HTTP/1.1
Host: example.org
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp/BasicContainer>; rel="type"
@@ -778,7 +778,7 @@
"@type": [ "ldp:Container", "ldp:BasicContainer"],
"dcterms:title": "Photos of Alice" ,
"dcterms:description": "This container will contain photos of Alice."
-}</pre></div></pre></div>
+}</pre></div></div></div>
<p>If the POST is successful, the server responds with the location of the newly created container for the photos.</p>
<div class="example"><div class="example-title"><span>Example 7</span>: Response - creating a new container</div><pre class="example">HTTP/1.1 201 Created
Location: http://example.org/alice/photos/
@@ -786,7 +786,7 @@
Content-Length: 0 </pre></div>
<p>This is how the parent container will look like after creating the new container</p>
- <div class="example"><div class="example-title"><span>Example 8</span>: State of Alice's document store after creating the photo (child) container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
+ <div class="example"><div class="example-title"><span>Example 8</span>: State of Alice's document store after creating the photo (child) container</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
<http://example.org/alice/> a ldp:Container, ldp:BasicContainer ;
@@ -802,9 +802,9 @@
{ "@id": "http://example.org/alice/foaf" },
{ "@id": "http://example.org/alice/photos/" }
]
-}</pre></div></pre></div>
+}</pre></div></div></div>
<p>and the photo container will look like the following.</p>
- <div class="example"><div class="example-title"><span>Example 9</span>: State of Alice's newly created photo container</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
+ <div class="example"><div class="example-title"><span>Example 9</span>: State of Alice's newly created photo container</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
<http://example.org/alice/photos/> a ldp:Container, ldp:BasicContainer;
@@ -821,7 +821,7 @@
- </pre></div></pre></div>
+ </pre></div></div></div>
</section>
@@ -836,7 +836,7 @@
</p>
- <div class="example"><div class="example-title"><span>Example 10</span>: Request - creating an RDF resource</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /alice/ HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 10</span>: Request - creating an RDF resource</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /alice/ HTTP/1.1
Host: example.org
Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
Slug: foaf
@@ -871,7 +871,7 @@
},
"dcterms:title": "Alice’s FOAF file"
}
-</pre></div></pre></div>
+</pre></div></div></div>
<div class="example"><div class="example-title"><span>Example 11</span>: Response - creating an RDF resource</div><pre class="example">HTTP/1.1 201 Created
Location: http://example.org/alice/foaf
@@ -884,7 +884,7 @@
Host: example.org
Accept: text/turtle, application/ld+json</pre></div>
- <div class="example"><div class="example-title"><span>Example 13</span>: Response - basic container retrieval after resource created</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
+ <div class="example"><div class="example-title"><span>Example 13</span>: Response - basic container retrieval after resource created</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
Content-Type: text/turtle; charset=UTF-8
Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type", <http://www.w3.org/ns/ldp#Resource>; rel="type"
Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -917,7 +917,7 @@
"@type": [ "ldp:Container", "ldp:BasicContainer"],
"dcterms:title": "Alice’s data storage on the Web",
"ldp:contains": { "@id": "http://example.org/alice/foaf" }
-}</pre></div></pre></div></section>
+}</pre></div></div></div></section>
<section id="creating-a-non-rdf-binary-resource-post-an-image-to-an-ldp-bc" typeof="bibo:Chapter" resource="#creating-a-non-rdf-binary-resource-post-an-image-to-an-ldp-bc" property="bibo:hasPart">
<h3 id="h-creating-a-non-rdf-binary-resource-post-an-image-to-an-ldp-bc" resource="#h-creating-a-non-rdf-binary-resource-post-an-image-to-an-ldp-bc"><span property="xhv:role" resource="xhv:heading"><span class="secno">2.5 </span> Creating a non-RDF (binary) resource (POST an image to an LDP-BC) </span></h3>
@@ -944,7 +944,7 @@
<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>
- <div class="example"><div class="example-title"><span>Example 16</span>: Container representation after the non-RDF resource creation</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: <http://purl.org/dc/terms/>.
+ <div class="example"><div class="example-title"><span>Example 16</span>: Container representation after the non-RDF resource creation</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix ldp: <http://www.w3.org/ns/ldp#>.
<http://example.org/alice/> a ldp:Container, ldp:BasicContainer;
@@ -960,7 +960,7 @@
"@type": [ "ldp:Container", "ldp:BasicContainer"],
"dcterms:title": "Alice’s data storage on the Web",
"ldp:contains": [{ "@id": "http://example.org/alice/foaf" }, { "@id": "http://example.org/alice/avatar" } ]
-}</pre></div></pre></div>
+}</pre></div></div></div>
</section>
<section id="update-a-rdf-ldp-resource-put-on-an-ldp-rs" typeof="bibo:Chapter" resource="#update-a-rdf-ldp-resource-put-on-an-ldp-rs" property="bibo:hasPart">
@@ -968,7 +968,7 @@
<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>
- <div class="example"><div class="example-title"><span>Example 17</span>: Request - updating a RDF resource</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>PUT /alice/foaf HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 17</span>: Request - updating a RDF resource</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>PUT /alice/foaf HTTP/1.1
Host: example.org
If-Match: W/"123454321"
Content-Type: text/turtle
@@ -997,7 +997,7 @@
"foaf:img" : { "@id": "http://example.org/alice/avatar" }
},
"dcterms:title": "Alice’s FOAF file"
-}</pre></div></pre></div>
+}</pre></div></div></div>
<div class="example"><div class="example-title"><span>Example 18</span>: Response - updating a RDF resource</div><pre class="example">HTTP/1.1 204 No Content
Link: <http://www.w3.org/ns/ldp#Resource>; rel="type" </pre></div>
@@ -1021,7 +1021,7 @@
<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>
- <div class="example"><div class="example-title"><span>Example 21</span>: Container representation after resource deletion</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: <http://purl.org/dc/terms/>.
+ <div class="example"><div class="example-title"><span>Example 21</span>: Container representation after resource deletion</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: <http://purl.org/dc/terms/>.
@prefix ldp: <http://www.w3.org/ns/ldp#>.
<http://example.org/alice/> a ldp:Container, ldp:BasicContainer;
@@ -1037,7 +1037,7 @@
"@type": [ "ldp:Container", "ldp:BasicContainer"],
"dcterms:title": "Alice’s data storage on the Web",
"ldp:contains": { "@id": "http://example.org/alice/foaf" }
-}</pre></div></pre></div>
+}</pre></div></div></div>
<p> For any subsequent request on the deleted resource, the server will respond with the appropriate HTTP response code. </p>
<div class="example"><div class="example-title"><span>Example 22</span>: Request - after deletion</div><pre class="example">GET /alice/avatar HTTP/1.1
@@ -1158,16 +1158,16 @@
<h3 id="h-navandret" resource="#h-navandret"><span property="xhv:role" resource="xhv:heading"><span class="secno">3.1 </span>Navigation and Retrieval (GET on an LDP-DC)</span></h3>
<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>
- <div class="example"><div class="example-title"><span>Example 24</span>: Request - Product Lookup</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 24</span>: Request - Product Lookup</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre></div><div class="jsonld" style="font-family: sans-serif; display: none;">JSON-LD:</div><div class="jsonld" style="display: none;"><pre>GET /tracker/ldp-demo/ HTTP/1.1
Host: example.org
-Accept: application/ld+json; charset=UTF-8</pre></div></pre></div>
+Accept: application/ld+json; charset=UTF-8</pre></div></div></div>
<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>
- <div class="example"><div class="example-title"><span>Example 25</span>: Response - Product Lookup</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
+ <div class="example"><div class="example-title"><span>Example 25</span>: Response - Product Lookup</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
Content-Type: text/turtle; charset=UTF-8
Link: <http://www.w3.org/ns/ldp#DirectContainer>; rel="type", <http://www.w3.org/ns/ldp#Resource>; rel="type"
Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -1219,7 +1219,7 @@
"dcterms:title": "LDP Demo",
"bt:hasBug": [{ "@id": "bug3"}, { "@id": "bug4"} ]
}
-]</pre></div></pre></div>
+]</pre></div></div></div>
<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>
@@ -1250,7 +1250,7 @@
<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 the resource to be created.
- </p><div class="example"><div class="example-title"><span>Example 26</span>: A request for creating a bug</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
+ </p><div class="example"><div class="example-title"><span>Example 26</span>: A request for creating a bug</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
Host: example.org
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"
@@ -1275,7 +1275,7 @@
"@type": "bt:BugReport",
"dcterms:title": "LDP Demo crashes when shutting down.",
"dcterms:creator": { "@id": "http://example.org/tracker/users/johndoe" }
-}</pre></div></pre></div>
+}</pre></div></div></div>
<p>If the creation is successful, the server responds with location of the newly created resource.</p>
<div class="example"><div class="example-title"><span>Example 27</span>: A response of creating new a bug</div><pre class="example" data-oninclude="fixCode">HTTP/1.1 201 Created
Location: http://example.org/tracker/ldp-demo/bug67
@@ -1283,7 +1283,7 @@
Content-Length: 0 </pre></div>
<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>
- <div class="example"><div class="example-title"><span>Example 28</span>: The state of the product LDPC after the bug creation</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
+ <div class="example"><div class="example-title"><span>Example 28</span>: The state of the product LDPC after the bug creation</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix bt: <http://example.org/vocab/bugtracker#> .
@@ -1319,12 +1319,12 @@
"dcterms:title": "LDP Demo",
"bt:hasbug": [{ "@id": "/tracker/ldp-demo/bug3"}, { "@id": "/tracker/ldp-demo/bug4"}, { "@id": "/tracker/ldp-demo/bug67"} ]
}
-]</pre></div></pre></div>
+]</pre></div></div></div>
<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>
- <div class="example"><div class="example-title"><span>Example 29</span>: The state of the bug LDPR</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: <http://purl.org/dc/terms/> .
+ <div class="example"><div class="example-title"><span>Example 29</span>: The state of the bug LDPR</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix bt: <http://example.org/vocab/bugtracker#> .
</tracker/ldp-demo/bug67> a bt:Bug;
@@ -1345,7 +1345,7 @@
"@value": "2013-05-05T10:00:00"
},
"bt:isInState": "New"
-}</pre></div></pre></div>
+}</pre></div></div></div>
</section>
@@ -1363,7 +1363,7 @@
<p> After the deletion, the representation of the container will look like the following</p>
- <div class="example"><div class="example-title"><span>Example 32</span>: The state of the product LDPC after the bug deletion</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
+ <div class="example"><div class="example-title"><span>Example 32</span>: The state of the product LDPC after the bug deletion</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix bt: <http://example.org/vocab/bugtracker#> .
@@ -1400,7 +1400,7 @@
]
-</pre></div></pre></div>
+</pre></div></div></div>
<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>
@@ -1418,15 +1418,15 @@
<p> Similar to the previous LDP-DC example, first we will retrieve the representation of the LDP Indirect Container.</p>
- <div class="example"><div class="example-title"><span>Example 33</span>: Product lookup request</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 33</span>: Product lookup request</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>GET /tracker/ldp-demo/ HTTP/1.1
Host: example.org
Accept: text/turtle; charset=UTF-8
</pre></div><div class="jsonld" style="font-family: sans-serif; display: none;">JSON-LD:</div><div class="jsonld" style="display: none;"><pre>GET /tracker/ldp-demo/ HTTP/1.1
Host: example.org
-Accept: application/ld+json; charset=UTF-8</pre></div></pre></div>
+Accept: application/ld+json; charset=UTF-8</pre></div></div></div>
<p> As a response to the GET request, the server responds with the representation of the product description container.</p>
- <div class="example"><div class="example-title"><span>Example 34</span>: HTTP response for product lookup</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
+ <div class="example"><div class="example-title"><span>Example 34</span>: HTTP response for product lookup</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK
Content-Type: text/turtle; charset=UTF-8
Link: <http://www.w3.org/ns/ldp#IndirectContainer>; rel="type", <http://www.w3.org/ns/ldp#Resource>; rel="type"
Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -1483,7 +1483,7 @@
"dcterms:title": "LDP Demo",
"bt:hasbug": [{ "@id": "/tracker/ldp-demo/bug3#it"}, { "@id": "/tracker/ldp-demo/bug4#it"} ]
}
-]</pre></div></pre></div>
+]</pre></div></div></div>
<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="https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-primer/ldp-primer.html#creationext">the next example</a> on creating a new resource. </p>
@@ -1496,7 +1496,7 @@
<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>
- <div class="example"><div class="example-title"><span>Example 35</span>: A request for creating a bug</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
+ <div class="example"><div class="example-title"><span>Example 35</span>: A request for creating a bug</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>POST /tracker/ldp-demo/ HTTP/1.1
Host: example.org
Content-Type: text/turtle
@@ -1534,7 +1534,7 @@
"@id": "#it",
"@type": "bt:Bug"
}
-]</pre></div></pre></div>
+]</pre></div></div></div>
<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>
<div class="example"><div class="example-title"><span>Example 36</span>: A response of creating new a bug</div><pre class="example" data-oninclude="fixCode">HTTP/1.1 201 Created
Location: http://example.org/tracker/ldp-demo/bug67
@@ -1542,7 +1542,7 @@
Content-Length: 0 </pre></div>
<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>
- <div class="example"><div class="example-title"><span>Example 37</span>: The state of the product LDPC after the bug creation</div><pre class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
+ <div class="example"><div class="example-title"><span>Example 37</span>: The state of the product LDPC after the bug creation</div><div><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>@prefix ldp: <http://www.w3.org/ns/ldp#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix bt: <http://example.org/vocab/bugtracker#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@@ -1582,7 +1582,7 @@
"dcterms:title": "LDP Demo"
"bt:hasBug": [{ "@id": "/tracker/ldp-demo/bug3#it"}, { "@id": "/tracker/ldp-demo/bug3#it"}, { "@id": "/tracker/ldp-demo/bug67#it"} ]
}
-]</pre></div></pre></div>
+]</pre></div></div></div>
<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>