ldp.html
changeset 486 974b4886835b
parent 485 195cdbad4852
child 487 e1e3f400d318
--- a/ldp.html	Wed Feb 12 08:55:47 2014 -0500
+++ b/ldp.html	Wed Feb 12 12:39:38 2014 -0500
@@ -228,7 +228,7 @@
 <h1>Introduction</h1>
 	<p>This specification describes the use
 	of HTTP for accessing, updating, creating and deleting resources from
-	servers that expose their resources as Linked Data.  It provides clarifications
+	servers that expose their resources as Linked Data.  It provides clarifications
 	and extensions of the rules of Linked Data [[LINKED-DATA]]:</p>
 	<ol>
 		<li>Use URIs as names for things</li>
@@ -460,10 +460,10 @@
 		format [[TURTLE]].</p>
 	<p>Commonly used namespace prefixes:</p>
 	<pre style="word-wrap: break-word; white-space: pre-wrap;">	@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
-	@prefix foaf:     &lt;http://xmlns.com/foaf/0.1/&gt;.
-	@prefix rdf:     &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
-	@prefix ldp:     &lt;http://www.w3.org/ns/ldp#&gt;.
-	@prefix xsd:     &lt;http://www.w3.org/2001/XMLSchema#&gt;.</pre>
+	@prefix foaf:     &lt;http://xmlns.com/foaf/0.1/&gt;.
+	@prefix rdf:     &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
+	@prefix ldp:     &lt;http://www.w3.org/ns/ldp#&gt;.
+	@prefix xsd:     &lt;http://www.w3.org/2001/XMLSchema#&gt;.</pre>
 </section>
 </section>
     
@@ -519,7 +519,7 @@
 	<section id="ldpr-cli-preservetriples"><h2 class="normal">
 		A <a title="LDP client">LDP client</a> MUST preserve all triples retrieved from an LDP-RR using HTTP <code>GET</code> that
 		it doesn’t change whether it understands the predicates or not, when
-		its intent is to perform an update using HTTP <code>PUT</code>.  The use of HTTP
+		its intent is to perform an update using HTTP <code>PUT</code>.  The use of HTTP
 		<code>PATCH</code> instead of HTTP <code>PUT</code> for update avoids this burden for clients
 		[[RFC5789]].
 	</h2></section> <!-- Was 4.5.5 / #ldpr-ldpr-4_5_5 -->
@@ -624,7 +624,7 @@
 	</h2></section><!-- Was 4.2.4.1 / #ldpr-4_2_4_1 -->
 	
 	<section id="ldpr-gen-atleast1rdftype"><h2 class="normal"><a title="Linked Data Platform RDF Resource">LDP-RRs</a> representations SHOULD have at least one <code>rdf:type</code>
-		set explicitly.  This makes the representations much more useful to
+		set explicitly.  This makes the representations much more useful to
 		client applications that don’t support inferencing.
 	</h2></section><!-- Was 4.2.5 / #ldpr-4_2_5 -->
 	
@@ -801,7 +801,7 @@
 	</h2></section><!-- Was 4.5.6 / #ldpr-4_5_6 -->
 	
 	<section id="ldpr-put-simpleupdate"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD allow clients to update resources without
-		requiring detailed knowledge of server-specific constraints.  
+		requiring detailed knowledge of server-specific constraints.  
 		This is a consequence of the requirement to enable simple creation and modification of LDPRs.
 	</h2></section><!-- Was 4.5.7 / #ldpr-4_5_7 -->	
 </section>
@@ -883,7 +883,7 @@
 	<p>It sometimes happens that a
 		resource is too large to reasonably transmit its representation in a
 		single HTTP response.  
-		To address this problem, servers should support a technique called Paging.  
+		To address this problem, servers should support a technique called Paging.  
 		When a client retrieves such a resource, the server redirects the client to a "first page" resource, and includes in its response
 		a link to the next part of the resource's state, all at a URLs of the server's choosing.
 		The triples in the representation of the <a title="Single-page resource">each page of an LDPR</a>
@@ -900,7 +900,7 @@
 	<p>
 		Looking at an example resource representing Example Co.'s customer
 		relationship data, identified by the URI <code>http://example.org/customer-relations</code>,
-		we’ll split the response across two pages.  
+		we’ll split the response across two pages.  
 		The client 
 		retrieves <code>http://example.org/customer-relations</code>, and
 		the server responds with <a href="#atrisk-333">status code <code>333 (Returning Related)</code></a>, 
@@ -923,21 +923,21 @@
 
 &lt;&gt;
    a o:CustomerRelations;
-   dcterms:title "The customer information for Example Co.";
-   o:client &lt;#JohnZSmith&gt;, &lt;#BettyASmith&gt;, &lt;#JoanRSmith&gt;. 
+   dcterms:title "The customer information for Example Co.";
+   o:client &lt;#JohnZSmith&gt;, &lt;#BettyASmith&gt;, &lt;#JoanRSmith&gt;. 
 
 &lt;#JohnZSmith&gt;
-   a foaf:Person;
+   a foaf:Person;
    o:status o:ActiveCustomer;
-   foaf:name "John Z. Smith".
+   foaf:name "John Z. Smith".
 &lt;#BettyASmith&gt;
-   a foaf:Person;
+   a foaf:Person;
    o:status o:PreviousCustomer;
-   foaf:name "Betty A. Smith".
+   foaf:name "Betty A. Smith".
  &lt;#JoanRSmith&gt;
-   a foaf:Person;
+   a foaf:Person;
    o:status o:PotentialCustomer;
-   foaf:name "Joan R. Smith".</pre>
+   foaf:name "Joan R. Smith".</pre>
 
 	<p>
 		Because the server includes a <code>Link: &lt;http://example.org/customer-relations?p=2&gt;; rel='next'</code>
@@ -966,21 +966,21 @@
 @base &lt;http://example.org/customer-relations&gt;.
 
 &lt;&gt;
-   o:client &lt;#GlenWSmith&gt;, &lt;#AlfredESmith&gt;. 
+   o:client &lt;#GlenWSmith&gt;, &lt;#AlfredESmith&gt;. 
  
 &lt;#GlenWSmith&gt;
-   a foaf:Person;
+   a foaf:Person;
    o:status o:ActiveCustomer, o:GoldCustomer;
-   foaf:name "Glen W. Smith".
+   foaf:name "Glen W. Smith".
 
 &lt;#AlfredESmith&gt;
-   a foaf:Person;
+   a foaf:Person;
    o:status o:ActiveCustomer, o:BronzeCustomer;
-   foaf:name "Alfred E. Smith".
+   foaf:name "Alfred E. Smith".
  </pre>
 	<p>
 		In this example, there are only two customers provided in the
-		final page.  To indicate this is the last page, the server omits the <code>Link: rel='next'</code> 
+		final page.  To indicate this is the last page, the server omits the <code>Link: rel='next'</code> 
 		header in its response.
 	</p>
 	<p>
@@ -1157,16 +1157,16 @@
 		container (the fact that it is a container and a brief title):</p>
 
 <pre class="example" id="ldpc-ex-simple"># The following is the representation of
-#    http://example.org/c1/
+#    http://example.org/c1/
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/c1/&gt;
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 
 &lt;&gt;
-   a ldp:Container, ldp:BasicContainer;
-   dcterms:title "A very simple container";
-   ldp:contains &lt;r1&gt;, &lt;r2&gt;, &lt;r3&gt;.</pre>
+   a ldp:Container, ldp:BasicContainer;
+   dcterms:title "A very simple container";
+   ldp:contains &lt;r1&gt;, &lt;r2&gt;, &lt;r3&gt;.</pre>
  
    	<figure id="fig-ldpc-basic">
         <img src="images/ldpc-basic.png" alt="Sample Linked Data Platform Basic Container" />
@@ -1188,7 +1188,7 @@
 	start with a domain resource for a person's net worth, as illustrated below:</p>
 			
 <pre class="example" id="ldpc-ex-membership-partial"># The following is a partial representation of
-#   http://example.org/netWorth/nw1
+#   http://example.org/netWorth/nw1
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/netWorth/nw1/&gt;
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
@@ -1213,7 +1213,7 @@
 	</p>
 
 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of LDPR
-#   http://example.org/netWorth/nw1
+#   http://example.org/netWorth/nw1
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/netWorth/nw1/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
@@ -1232,7 +1232,7 @@
 </pre>
 
 <pre class="example" id="ldpc-ex-membership-subj"># The following is an elaborated representation of LDPC
-#   http://example.org/netWorth/nw1/assetContainer/
+#   http://example.org/netWorth/nw1/assetContainer/
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/netWorth/nw1/assetContainer/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
@@ -1247,7 +1247,7 @@
 </pre>
 
 <pre class="example" id="ldpc-ex-membership-full-liabcont"># The following is an elaborated representation of LDPC
-#   http://example.org/netWorth/nw1/liabilityContainer/
+#   http://example.org/netWorth/nw1/liabilityContainer/
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/netWorth/nw1/liabilityContainer/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
@@ -1303,13 +1303,13 @@
 	these real-world resources, not the documents that describe them.</p>
 	
 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of
-#   http://example.org/netWorth/nw1
+#   http://example.org/netWorth/nw1
 # Adding o:advisor but eaving off o:asset and o:liability for brevity.
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/netWorth/nw1/&gt;
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
-@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
+@prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 &lt;&gt;
    a o:NetWorth;
@@ -1418,9 +1418,9 @@
 
 &lt;http://example.org/container1/&gt;
    a ldp:Container, ldp:DirectContainer;
-   dcterms:title "A Linked Data Platform Container of Acme Resources";
+   dcterms:title "A Linked Data Platform Container of Acme Resources";
    ldp:containerResource &lt;http://example.org/container1/&gt;;
-   ldp:containsRelation ldp:member;
+   ldp:containsRelation ldp:member;
    ldp:insertedContentRelation ldp:MemberSubject;
    dcterms:publisher &lt;http://acme.com/&gt;.</pre>
    
@@ -1478,40 +1478,40 @@
 @prefix o: &lt;http://example.org/ontology/&gt;.
 
 &lt;&gt;
-   a ldp:Container, ldp:DirectContainer;
-   dcterms:title "The assets of JohnZSmith";
-   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-   ldp:containsRelation o:asset;
+   a ldp:Container, ldp:DirectContainer;
+   dcterms:title "The assets of JohnZSmith";
+   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:containsRelation o:asset;
    ldp:insertedContentRelation ldp:MemberSubject.
 
 &lt;?firstPage&gt;
    a ldp:Page;
-   ldp:pageOf &lt;&gt;;
+   ldp:pageOf &lt;&gt;;
    ldp:containerSortCriteria (&lt;#SortValueAscending&gt;).
 
 &lt;#SortValueAscending&gt;
    a ldp:ContainerSortCriterion;
-   ldp:containerSortOrder ldp:Ascending;
+   ldp:containerSortOrder ldp:Ascending;
    ldp:containerSortPredicate o:value.
 
 &lt;http://example.org/netWorth/nw1&gt;
-   a o:NetWorth;
+   a o:NetWorth;
    o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.
 
 &lt;a1&gt;
-   a o:Stock;
-   o:value 100.00 .
+   a o:Stock;
+   o:value 100.00 .
 &lt;a2&gt;
-   a o:Cash;
-   o:value 50.00 .
+   a o:Cash;
+   o:value 50.00 .
 &lt;a3&gt;
-   a o:RealEstateHolding;
-   o:value 300000 .
+   a o:RealEstateHolding;
+   o:value 300000 .
 </pre>
 		<p>
 			As you can see by the addition of the <code>ldp:ContainerSortCriteria</code> 
 			predicate, the <code>o:value</code> predicate is used
-			to order the page members in ascending order.  It is up to the domain model
+			to order the page members in ascending order.  It is up to the domain model
 			and server to determine the appropriate predicate to indicate the
 			resource’s order within a page, and up to the client receiving this 
 			representation to use that order in whatever way is appropriate, for 
@@ -1692,20 +1692,20 @@
 		<a title="Membership triples">membership triples</a> following one of the consistent 
 		patterns from that definition.
 		The membership-constant-URI of the triples MAY be the container itself
-		or MAY be another resource (as in the <a href="#ldpc-ex-membership-subj">example</a>).  See also
+		or MAY be another resource (as in the <a href="#ldpc-ex-membership-subj">example</a>).  See also
 		section on <a href="#ldpc-mbrpred">LDPC membership predicates</a>.
 	</h2></section><!-- Was 5.3.1 / #ldpc-5_3_1 -->
 	
 	<section id="ldpc-sortcriteriaobj"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY 
 		represent the members of a paged LDPC in a sequential
-		order.  If the server does so, it MUST specify the order using a triple 
+		order.  If the server does so, it MUST specify the order using a triple 
 		whose subject is the page URI, 
 		whose predicate is <code>ldp:containerSortCriteria</code>, 
 		and whose object is a <code>rdf:List</code> of
 		<code>ldp:containerSortCriterion</code> resources.  
 		The resulting order MUST be as defined by SPARQL <code>SELECT</code>’s <code>ORDER BY</code> clause 
 		[[!SPARQL-QUERY]].
-		Sorting criteria MUST be the same for all pages of a representation; if
+		Sorting criteria MUST be the same for all pages of a representation; if
 		the criteria were allowed to vary, the ordering among members of a container
 		across pages would be undefined. 
 		The first list entry provides the primary
@@ -1841,7 +1841,7 @@
 		Commonly, that entity is the model for the “to be created” LDPR, so
 		triples whose subject is the null relative URI will usually result in
 		triples in the created resource whose subject is the created
-		resource.  
+		resource.  
 	</h2></section><!-- Was 5.4.7 / #ldpc-5_4_7 -->	
 	
 	<section id="ldpc-post-serverassignuri"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD assign the URI for the resource to be
@@ -2339,25 +2339,25 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
-	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   a ldp:Container, ldp:DirectContainer;
+	   dcterms:title "The assets of JohnZSmith";
+	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:containsRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 
 	&lt;http://example.org/netWorth/nw1&gt;
-	   a o:NetWorth;
+	   a o:NetWorth;
 	   o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.
 
 	&lt;a1&gt;
-	   a o:Stock;
-	   o:value 100.00 .
+	   a o:Stock;
+	   o:value 100.00 .
 	&lt;a2&gt;
-	   a o:Cash;
-	   o:value 50.00 .
+	   a o:Cash;
+	   o:value 50.00 .
 	&lt;a3&gt;
-	   a o:RealEstateHolding;
-	   o:value 300000 .
+	   a o:RealEstateHolding;
+	   o:value 300000 .
 	</pre>
 
 	<p id="prefer-examples-direct-empty-container-only1">
@@ -2381,10 +2381,10 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
-	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   a ldp:Container, ldp:DirectContainer;
+	   dcterms:title "The assets of JohnZSmith";
+	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:containsRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 	</pre>
 
@@ -2412,10 +2412,10 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
-	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   a ldp:Container, ldp:DirectContainer;
+	   dcterms:title "The assets of JohnZSmith";
+	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:containsRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 	</pre>
 
@@ -2448,14 +2448,14 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
-	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   a ldp:Container, ldp:DirectContainer;
+	   dcterms:title "The assets of JohnZSmith";
+	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:containsRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 
 	&lt;http://example.org/netWorth/nw1&gt;
-	   a o:NetWorth;
+	   a o:NetWorth;
 	   o:asset &lt;a1&gt;, &lt;a3&gt;, &lt;a2&gt;.
 	</pre>