ldp.html
changeset 448 72e366f1195f
parent 447 f7f6d5fe3313
child 449 623bbfdea989
--- a/ldp.html	Wed Jan 29 12:59:42 2014 -0500
+++ b/ldp.html	Thu Jan 30 13:01:49 2014 -0500
@@ -272,9 +272,18 @@
 	<dd>As defined by Tim Berners-Lee [[LINKED-DATA]].<p></p></dd>
 	
 	<dt><dfn>Linked Data Platform Resource</dfn> (<abbr title="Linked Data Platform Resource">LDPR</abbr>)</dt>
-	<dd>HTTP resource whose state is represented in RDF that conforms to the simple lifecycle
+	<dd>HTTP resource whose state is represented in any representation that conforms to the simple lifecycle
 		patterns and conventions in <a href="#ldpr" class="sectionRef"></a>.<p></p></dd>
 		
+	<dt><dfn>Linked Data Platform RDF Resource</dfn> (<abbr title="Linked Data Platform RDF Resource">LDP-RR</abbr>)</dt>
+	<dd>An <a title="Linked Data Platform Resource">LDP-R</a> whose state is represented in an RDF representation.
+	<p></p></dd>	
+
+	<dt><dfn>Linked Data Platform Binary Resource</dfn> (<abbr title="Linked Data Platform Binary Resource">LDP-BR</abbr>)</dt>
+	<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is <em>not</em> represented in an RDF representation.
+	These are binary or text resources that do not have useful RDF representations.
+	<p></p></dd>
+		
 	<dt><dfn>Linked Data Platform Container</dfn> (<abbr title="Linked Data Platform Container">LDPC</abbr>)</dt>
 	<dd>An LDPR representing a collection of <a title="Membership triples">membership triples</a> which is uniquely identified by a URI
 	that responds to client requests for creation, modification, and enumeration of its members.
@@ -506,7 +515,23 @@
 		This document also explains <a href="#ldpr-Paging">how a server paginates an LDPR's representation</a> if it gets too big.
 		Companion informative documents describe additional guidelines for use when interacting with LDPRs. 
 	</p>
-
+	<p>An LDP server manages two kinds of <a title="Linked Data Platform Resources">LDPRs</a>, those resources who whose state 
+	is represented using an RDF representation (LDP-RR) and those using other representations (LDP-BR).  LDP-RRs have the unique
+	quality in that their representation is based on the RDF which provides for a number of use cases from web metadata, open data 
+	models, machine processable information and automated processing by software agents [[!RDF-CONCEPTS]].  LDP-BRs are almost anything
+	on the Web today: images, html pages, word processing documents, spreadsheets, etc and LDP-RRs often serve a purpose to manage the 
+	metadata associated with LDP-BRs.
+	</p>
+    <figure id="fig-ldpr-kinds">
+        <img src="images/ldpr1.png" alt="Sample separation of Linked Data Platform Resource" />
+        <figcaption>Samples of different types of LDPRs</figcaption>
+    </figure>
+    <p>The LDP-BRs and LDP-RRs are simply sub-types of LDPRs, as illustrated in <a href="#fig-ldpr-class"></a>.</p>  
+    <figure id="fig-ldpr-class">
+       <img src="images/ldpr2.png" alt="Class Diagram of Linked Data Platform Resource" />
+       <figcaption>Class relationship of types of LDPRs</figcaption>
+     </figure>
+	
 </section>
 
 <section id="ldpr-general">
@@ -515,25 +540,26 @@
 	<section id="ldpr-gen-http"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST at least be HTTP/1.1 conformant servers [[!HTTP11]].
 	</h2></section><!-- Was 4.2.1 / #ldpr-4_2_1 -->
 	
-	<section id="ldpr-gen-rdf"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST provide an RDF representation for LDPRs. 
-	The HTTP <code>Request-URI</code> of the LDPR is typically the subject of most triples in the response.
+	<section id="ldpr-gen-rdf"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST provide an RDF representation for <a title="Linked Data Platform RDF Resource">LDP-RRs</a>. 
+	The HTTP <code>Request-URI</code> of the LDP-RR is typically the subject of most triples in the response.
 	</h2></section><!-- Was 4.2.2 / #ldpr-4_2_2 -->
 	
-	<section id="ldpr-gen-binary"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY host a mixture of LDPRs and non-LDPRs. For example, it
+	<section id="ldpr-gen-binary"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY host a mixture of LDPRs, <a title="Linked Data Platform RDF Resource">LDP-RRs</a>
+	and <a title="Linked Data Platform Binary Resource">LDP-BRs</a>. For example, it
 		is common for <a title="LDP server">LDP servers</a> to need to host binary or text resources
 		that do not have useful RDF representations.</h2></section><!-- Was 4.2.3 / #ldpr-4_2_3 -->
 
-	<section id="ldpr-gen-reusevocab"><h2 class="normal">LDPRs SHOULD reuse existing vocabularies instead of creating
+	<section id="ldpr-gen-reusevocab"><h2 class="normal"><a title="Linked Data Platform RDF Resource">LDP-RRs</a> SHOULD reuse existing vocabularies instead of creating
 		their own duplicate vocabulary terms.  In addition to this general rule, some specific cases are
 		covered by other conformance rules.
 	</h2></section><!-- Was 4.2.4 / #ldpr-4_2_4 -->
 	
-	<section id="ldpr-gen-reusevocabsuchas"><h2 class="normal">LDPR predicates SHOULD use standard vocabularies such as Dublin Core
+	<section id="ldpr-gen-reusevocabsuchas"><h2 class="normal"><a title="Linked Data Platform RDF Resource">LDP-RRs</a> predicates SHOULD use standard vocabularies such as Dublin Core
 		[[!DC-TERMS]], RDF [[!RDF-CONCEPTS]] and RDF Schema [[!RDF-SCHEMA]], whenever
 		possible.
 	</h2></section><!-- Was 4.2.4.1 / #ldpr-4_2_4_1 -->
 	
-	<section id="ldpr-gen-atleast1rdftype"><h2 class="normal">LDPR representations SHOULD have at least one <code>rdf:type</code>
+	<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
 		client applications that don’t support inferencing.
 	</h2></section><!-- Was 4.2.5 / #ldpr-4_2_5 -->
@@ -545,7 +571,7 @@
 	<section id="ldpr-gen-linktypehdr"><h2 class="normal"><a title="LDP server">LDP servers</a>
 		exposing LDPRs 
 		MUST advertise their LDP support by exposing a HTTP <code>Link</code> header
-		with a target URI of <code>http://www.w3.org/ns/ldp/Resource</code>, and
+		with a target URI of <code>http://www.w3.org/ns/ldp#RDFResource</code>, and
 		a link relation type of <code>type</code> (that is, <code>rel='type'</code>)
 		in all responses to requests made 
 		to the LDPR's HTTP <code>Request-URI</code>. 
@@ -620,7 +646,7 @@
 	</h2></section><!-- Was 4.3.2 / #ldpr-4_3_2 -->
 	
 	<section id="ldpr-get-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST provide a <code>text/turtle</code>
-		representation of the requested LDPR [[!TURTLE]].
+		representation of the requested <a title="Linked Data Platform RDF Resource">LDP-RR</a> [[!TURTLE]].
 	</h2></section><!-- Was 4.3.3 / #ldpr-4_3_3 -->
 
 </section>
@@ -777,8 +803,8 @@
 		To address this problem, servers should support a technique called Paging.  
 		When a client retrieves such a resource, the server includes in its response
 		a link to the next part of the resource's state, at a URL of the server's choosing.
-		The triples in the representation of the each page of an LDPR
-		are typically a subset of the triples in the resource.
+		The triples in the representation of the <a title="Single-page resource">each page of an LDPR</a>
+		are typically a subset of the triples from the <a title="Paged resource">paged resource</a>.
 	</p>
 	<p><a title="LDP server">LDP servers</a> may respond to requests for a
 		resource by returning the first page of the resource
@@ -1294,7 +1320,7 @@
 		discover <dfn><abbr title="Linked Data Platform Containers">LDPCs</abbr></dfn>.</p>
 
 	<section id="ldpc-isldpr"><h2 class="normal">Each Linked Data Platform Container MUST also be 
-		a conforming Linked Data Platform Resource.
+		a conforming <a title="">Linked Data Platform RDF Resource</a>.
 	</h2></section><!-- Was 5.2.1 / #ldpc-5_2_1 -->
 	
 	<section id="ldpc-mbrpred"><h2 class="normal"><a title="LDP server">LDP servers</a>
@@ -1530,7 +1556,8 @@
 		the site that implements the LDPC.
 	</h2></section><!-- Was 5.4.2 / #ldpc-5_4_2 -->
 	
-	<section id="ldpc-post-createbins"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY accept an HTTP <code>POST</code> of non-RDF representations for
+	<section id="ldpc-post-createbins"><h2 class="normal"><a title="LDP server">LDP servers</a> MAY accept an HTTP <code>POST</code> of non-RDF representations 
+	<a title="Linked Data Platform Binary Resource">(LDP-BR)</a> for
 		creation of any kind of resource, for example binary resources.  See <a href="#ldpc-post-acceptposthdr">AcceptPost section</a> for 
 		details on how clients can discover whether a LDPC supports this behavior.
 	</h2></section><!-- Was 5.4.3 / #ldpc-5_4_3 -->
@@ -1586,9 +1613,11 @@
 		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 non-RDF and therefore non-LDPR member (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 LDPR
-	to contain data about the created resource.  If an LDPC server creates this associated LDPR it MUST indicate
+	<section id="ldpc-post-createbinlinkmetahdr"><h2 class="normal">Upon successful creation of a non-RDF 
+	<a title="Linked Data Platform Binary Resource">(LDP-BR)</a> and therefore non-LDPR member (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 Resource">LDP-RR</a>
+	to contain data about the created resource.  If an LDPC server creates this associated <a title="Linked Data Platform RDF Resource">LDP-RR</a> it MUST indicate
 	its location on the HTTP response using the HTTP response header <code>Link</code> and relationship type <code>meta</code>
 	and <code>href</code> to be the URI of the meta-resource [[!RFC5988]].
 	</h2></section><!-- Was 5.4.12 / #ldpc-5_4_12 -->
@@ -1748,10 +1777,10 @@
 		would be <code>Link: &lt;?nonMemberProperties&gt;;rel='http://www.w3.org/ns/ldp#nonMemberResource'</code>
 	</section><!-- Was 5.9.1 / #ldpc-5_9_1 -->
 	
-	<section id="ldpc-options-linkmetahdr"><h2 class="normal">When a LDPC creates a non-LDPR (e.g. binary) member (for example, one whose 
-	representation was HTTP <code>POST</code>ed to the LDPC and then referenced by a membership triple) it might create an associated LDPR to contain data about the 
-	non-LDPR (see <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>).  For non-LDPRs that have this associated LDPR, an LDPC server MUST provide an HTTP <code>Link</code>
-	header whose target URI is the associated LDPR, and whose link relation type is 
+	<section id="ldpc-options-linkmetahdr"><h2 class="normal">When a LDPC creates a <a title="Linked Data Platform Binary Resource">LDP-BR</a> member (for example, one whose 
+	representation was HTTP <code>POST</code>ed to the LDPC and then referenced by a membership triple) it might create an associated <a title="Linked Data Platform RDF Resource">LDP-RR</a> to contain data about the 
+	non-LDPR (see <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>).  For LDP-BRs that have this associated LDP-RR, an LDPC server MUST provide an HTTP <code>Link</code>
+	header whose target URI is the associated LDP-RR, and whose link relation type is 
 	<code>meta</code> [[!RFC5988]].
 	
 	<!-- TODO: Consider some improvement to this:
@@ -2061,6 +2090,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-01-30 - ACTION-123 Added concepts of LDP-RDF-Resource and LDP-Binary-Resource (SS)</li>
 	<li>2014-01-29 - Fix up conformance section to use new LDP client section (SS)</li>
 	<li>2014-01-21 - Updated reference to LDP BP&amp;G editor's draft and added ref to LDP-UCR (SS)</li>
 	<li>2014-01-21 - Removed redudant reqs that have been moved to <a href="#ldpclient"></a> (SS)</li>