ldp.html
changeset 514 7e329a35960e
parent 513 2df2933649d4
child 515 9f5b3854a5bb
--- a/ldp.html	Sat Mar 01 14:51:42 2014 -0500
+++ b/ldp.html	Sat Mar 01 15:15:19 2014 -0500
@@ -4,7 +4,6 @@
 	TODO: Once companion documents (best practices, primer) have URLs, link to them.  Search on "companion".
 	TODO: Add new "discovery of server capabilities" non-norm section
     TODO: Consider folding LDP Clients section, feels a bit out of place
-    TODO: Consider creating LDPR sub sections R, RS, NR like LDPCs
     TODO: Consider adding Venn diagram for differences of LDPCs
  -->
 <html>
@@ -298,7 +297,7 @@
 	<p></p></dd>	
 
 	<dt><dfn>Linked Data Platform Non-RDF Source</dfn> (<abbr title="Linked Data Platform Non-RDF Source">LDP-NR</abbr>)</dt>
-	<dd>A <a title="Linked Data Platform Resource">LDPR</a> whose state is <em>not</em> represented in RDF.
+	<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is <em>not</em> represented in RDF.
 	These are binary or text documents that do not have useful RDF representations.
 	<p></p></dd>
 		
@@ -311,18 +310,18 @@
 	<p></p></dd>
 	
 	<dt><dfn>Linked Data Platform Basic Container</dfn> (<abbr title="Linked Data Platform Basic Container">LDP-BC</abbr>)</dt>
-	<dd>A <a title="Linked Data Platform Container">LDPC</a> that defines a simple link to
+	<dd>An <a title="Linked Data Platform Container">LDPC</a> that defines a simple link to
 	its <a title="Containment">contained</a> documents (information resources) [[!WEBARCH]].
 	<p></p></dd>
 	
 	<dt><dfn>Linked Data Platform Direct Container</dfn> (<abbr title="Linked Data Platform Direct Container">LDP-DC</abbr>)</dt>
-	<dd>A <a title="Linked Data Platform Container">LDPC</a> adds the concept <a title="Membership">membership</a>, allows the flexibility of choosing what form its 
+	<dd>An <a title="Linked Data Platform Container">LDPC</a> adds the concept <a title="Membership">membership</a>, allows the flexibility of choosing what form its 
 	<a title="Membership triples">membership triples</a> take, and allows <a title="Membership">members</a> to be 
 	any resources [[!WEBARCH]], not only documents.
 	<p></p></dd>
 	
 	<dt><dfn>Linked Data Platform Indirect Container</dfn> (<abbr title="Linked Data Platform Indirect Container">LDP-IC</abbr>)</dt>
-	<dd>A <a title="Linked Data Platform Container">LDPC</a> that is similar to a <a title="Linked Data Platform Direct Container">LDP-DC</a>
+	<dd>An <a title="Linked Data Platform Container">LDPC</a> that is similar to a <a title="Linked Data Platform Direct Container">LDP-DC</a>
 	and is capable of having <a title="Membership">members</a> whose URIs are based
 	on the content of its <a title="Containment">contained</a> documents rather than the URIs assigned to those documents.
 	<p></p></dd>
@@ -1096,7 +1095,7 @@
 	(<code>topic-URI</code>) in the new membership triple.</p>
 	
 	<p>This type of container is also referred to as a <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a>. 
-	It is similar to a an <a title="Linked Data Platform Direct Container">LDP Direct Container</a> 
+	It is similar to an <a title="Linked Data Platform Direct Container">LDP Direct Container</a> 
 	but it provides an indirection to add (via a create request) as member any resource, 
 	such as a URI representing a real-world object,
 	that is different from the document that is created.</p>
@@ -1133,7 +1132,7 @@
 		that has many members will be large. There are several important
 		cases where clients need to access only the subset of the container's properties 
 		that are unrelated to member resources and unrelated to contained documents, for
-		example to determine the membership triple pattern and membership predicate of a 
+		example to determine the membership triple pattern and membership predicate of an 
 		LDP-DC.  LDP calls these <a title="Empty-container triples">empty-container triples</a>,
 		because they are what remains when the container has zero members and zero contained resources.
 		Since retrieving the whole container representation to
@@ -1333,7 +1332,7 @@
 		SHOULD NOT re-use URIs.
 	</h2></section><!-- Was 5.4.11 / #ldpc-5_4_11 -->
 	
-	<section id="ldpc-post-createbinlinkmetahdr"><h2 class="normal">Upon successful creation of a  
+	<section id="ldpc-post-createbinlinkmetahdr"><h2 class="normal">Upon successful creation of an  
 	<a title="Linked Data Platform Non-RDF Source">LDP-NR</a> (HTTP status code of 
 	201-Created and URI indicated by <code>Location</code> response header), <a title="LDP server">LDP servers</a> MAY create an associated 
 	<a title="Linked Data Platform RDF Source">LDP-RS</a>
@@ -1381,7 +1380,7 @@
 	
 	<section id="ldpc-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> that allow LDPR creation via <code>PUT</code> 
 		SHOULD NOT re-use URIs.  For RDF representations (LDP-RSs),the created resource
-		can be thought of as a RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[!rdf11-concepts]].
+		can be thought of as an RDF <a href="http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph">named graph</a> [[!rdf11-concepts]].
 	</h2></section><!-- Was 5.5.4 / #ldpc-5_5_4 -->
 	
 </section>
@@ -1450,7 +1449,7 @@
 	<p>This specification imposes the following new requirements on HTTP <code>OPTIONS</code> for LDPCs.
 		</p>
 
-	<section id="ldpc-options-linkmetahdr"><h2 class="normal">When an LDPC server creates a 
+	<section id="ldpc-options-linkmetahdr"><h2 class="normal">When an LDPC server creates an 
 	<a title="Linked Data Platform Non-RDF Source">LDP-NR</a> (for example, one whose 
 	representation was HTTP <code>POST</code>ed to the LDPC) 
 	the LDP server might create an associated <a title="Linked Data Platform RDF Source">LDP-RS</a> 
@@ -1762,14 +1761,14 @@
 		can include an arbitrary number of
 		additional triples whose subjects are the members of the container,
 		or that are from the representations of the members (if they have RDF
-		representations). This allows a <a>LDP server</a> to provide clients with
+		representations). This allows an <a>LDP server</a> to provide clients with
 		information about the members without the client having to do a <code>GET</code>
 		on each member individually.  See <a href="#ldpc-member_data">Container
 		Member Information</a> for additional details.
 	</h2></section>
 	
 	<section id="ldp-rdfconcepts-extra-triples-types"><h2 class="normal">The state of an LDPR can have more than one
-		triple with a <code>rdf:type</code> predicate.
+		triple with an <code>rdf:type</code> predicate.
 	</h2></section>
 
 </section> 
@@ -1977,7 +1976,7 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
+	   a ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
 	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
 	   ldp:hasMemberRelation o:asset;
@@ -2019,7 +2018,7 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
+	   a ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
 	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
 	   ldp:hasMemberRelation o:asset;
@@ -2050,7 +2049,7 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
+	   a ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
 	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
 	   ldp:hasMemberRelation o:asset;
@@ -2086,7 +2085,7 @@
 	@prefix o: &lt;http://example.org/ontology/&gt;.
 
 	&lt;&gt;
-	   a ldp:Container, ldp:DirectContainer;
+	   a ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
 	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
 	   ldp:hasMemberRelation o:asset;