--- a/ldp-primer/ldp-primer.html Mon Jun 16 10:43:42 2014 +0200
+++ b/ldp-primer/ldp-primer.html Mon Jun 16 14:27:26 2014 +0100
@@ -328,24 +328,24 @@
<figcaption>Generic document storage using a Basic Container.</figcaption>
</figure>
<p>
- Such servers do not impose any restriction on LDPRs and generally act as storage systems without any domain specific application logic and vocabularies. The <a href="#photomanager">first scenario in this document</a> concerns a document storage system based on Basic Containers.
+ Such servers do not impose any restriction on LDPRs and generally act as storage systems without any domain specific application logic and vocabularies. The <a href="#docstore">first scenario in this document</a> concerns a document storage system based on Basic Containers.
</p>
<p>
- A Direct Container allows and LDP server to advertise the addition of assertions using a domain-specific vocabulary as part of the creation process; called membership triples, these augment the containment triples maintained by all containers.
+ A Direct Container is a specialisation of a Basic Container. Additional assertions called membership triples which use a domain-specific vocabulary are made by a Direct Container as part of the creation process. The membership triples augment the containment triples maintained by all containers. For example, in the document storage system, membership triples may use some existing domain-specific vocabularly.
</p>
<figure id="fig-dc1">
<img src="images/dc1.png" alt=".." />
<figcaption>Using domain vocabularly with a Direct container.</figcaption>
</figure>
<p>
- Direct Containers can also use domain specific vocabulary and link from a resource other than the Container resource to the new resource.
+ Direct Container membership triples can be about subjects other than the Container resource. An example is a Photo management application where a Photo Container is used for the management of Photos, and where membership triples express the relationship between a User and a Photo.
</p>
<figure id="fig-dc_photos">
<img src="images/dc_photos.png" alt=".." />
<figcaption>Membership triples with a non-Container subject.</figcaption>
</figure>
<p>
- Different facets of a Resource can be managed using multiple Containers.
+ Another common pattern is where different facets of a Resource be managed using multiple Containers. For example, a Bug Report is described by a comment list as well as supportive media resources.
</p>
<figure id="fig-dc_bugs">
<img src="images/dc_bugs.png" alt=".." />
@@ -361,7 +361,7 @@
</section>
- <section id="photomanager">
+ <section id="docstore">
<h1>Online document store example (LDP Basics)</h1>
<p>
@@ -452,8 +452,8 @@
<pre title="Response - basic container retrieval" class='example' data-include='getbc_res.txt' data-oninclude='fixCode'></pre>
<p> As shown in the example, in addition to the RDF representation of the Basic Container using the requested media type the server provides an etag of the resource representation and Link headers advertising that the requested resource is indeed an LDP Basic Container and it will support the LDP interaction model. </p>
-
- <p> In addition, the response also contains "Allow" header which advertises which HTTP operations are supported by this LDP Basic Container resource. In this example, it supports OPTIONS,HEAD,GET,POST,PUT,PATCH HTTP verbs.</p>
+
+ <p> In addition, the response also contains "Allow" header which advertises which HTTP operations are supported by this LDP Basic Container resource. In this example, it supports OPTIONS,HEAD,GET,POST,PUT,PATCH HTTP verbs.</p>
<p class="note">The Linked Data Platform 1.0 specification [[LDP]] says that all LDP servers MUST support the Turtle media type for LDP-RS resources and SHOULD support JSON-LD media type.</p>
@@ -490,11 +490,11 @@
<p>
Alice can upload a social profile document to her store, by POSTing her FOAF personal profile document to her LDP-BC at the root of her document store. Note, the Slug header offers the server a hint about URL of the resource to be created.
- </p>
-
- <p> The FOAF document includes statements about the resource to be created and other resources relative to the resource to be created. According the LDP specification
- Alice can use null relative URI (<>) in the request entity body to refer to resource to be created.
-
+ </p>
+
+ <p> The FOAF document includes statements about the resource to be created and other resources relative to the resource to be created. According the LDP specification
+ Alice can use null relative URI (<>) in the request entity body to refer to resource to be created.
+
</p>
<pre title="Request - creating a RDF resource" class='example' data-include='bccreate.txt' data-oninclude='fixCode'></pre>
@@ -584,9 +584,9 @@
<section>
<h2> Deleting a resource (DELETE on an LDPR) </h2>
- <p>If Alice decides to delete the image, she can do that with a delete operation.</p>
-
- <p>Similar to the previous update operation, Alice uses the etag of the resource representation she retrieved with If-Match header to do a conditional delete to ensure that the resource state
+ <p>If Alice decides to delete the image, she can do that with a delete operation.</p>
+
+ <p>Similar to the previous update operation, Alice uses the etag of the resource representation she retrieved with If-Match header to do a conditional delete to ensure that the resource state
was not changed since she decided to delete it. </p>
<pre title="Request - deleting a RDF resource" class="example">
@@ -780,8 +780,8 @@
<section>
<h3 id="BugCreate">Creation (POST a resource to an LDP-DC)</h3>
<p>Continuing from the previous example, we can report a Bug against the "LDP Demo" product by creating a Bug report (an LDPR representing the bug) under the "LDP Demo" product description LDPC by posting a RDF representation of the Bug report to the LDPC associated with the product description. </p>
-
- <p> The bug report document includes statements about the resource to be created. According the LDP specification, a client can use null relative URI (<>) in the request entity body to refer to resource to be created.
+
+ <p> The bug report document includes statements about the resource to be created. According the LDP specification, a client can use null relative URI (<>) in the request entity body to refer to resource to be created.
<pre title="A request for creating a bug" class='example' data-include='bug_create_req.txt' data-oninclude='fixCode'></pre>
<p>If the creation is successful, the server responds with location of the newly created resource.</p>
@@ -911,18 +911,18 @@
<li><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/default/Test%20Cases/LDP%20Test%20Cases.html">Linked Data Platform 1.0 Test Cases</a>[[LDP-TESTS]]</li>
</ul>
- </section>
-
- <section class='appendix'>
- <h2>Acknowledgements</h2>
- <p>Many thanks to John Arwe (IBM), Ashok Malhotra (Oracle), and Henry Story (Apache Software Foundation) for their thorough review on the LDP Primer document and proposed corrections. We also like to thank all members of the Linked Data Platform WG for the valuable feedback. </p>
+ </section>
+
+ <section class='appendix'>
+ <h2>Acknowledgements</h2>
+ <p>Many thanks to John Arwe (IBM), Ashok Malhotra (Oracle), and Henry Story (Apache Software Foundation) for their thorough review on the LDP Primer document and proposed corrections. We also like to thank all members of the Linked Data Platform WG for the valuable feedback. </p>
</section>
<section class='appendix informative' id="history">
<h1>Change History</h1>
<p>The change history is up to the editors to insert a brief summary of changes, ordered by most recent changes first and with heading from which public draft it has been changed from.
</p>
- <ul>
+ <ul>
<li>2014-06-16 - Addressing the comments and feedback provided by Ashok, John, and Henry.</li>
<li>2013-08-05 - Providing JSON-LD representations of the examples.</li>
<li>2013-07-03 - Moving the content from the wiki to the note.</li>