Cleanup from Action-123 add LDPR-RR and LDPR-BR
authorJohn Arwe
Wed, 05 Feb 2014 14:32:56 -0500
changeset 461 64c0ca32c9e6
parent 460 1f6e06fd7272
child 462 3a7f9b05bad8
Cleanup from Action-123 add LDPR-RR and LDPR-BR
ldp.html
ldp.ttl
--- a/ldp.html	Wed Feb 05 18:19:59 2014 +0000
+++ b/ldp.html	Wed Feb 05 14:32:56 2014 -0500
@@ -287,7 +287,7 @@
 		[[HTTP11]]. </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 any representation that conforms to the simple lifecycle
+	<dd>A HTTP resource whose state is represented in any way 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>
@@ -296,39 +296,45 @@
 	<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 RDF.
-	These are binary or text resources that do not have useful RDF representations.
+	<dd>A <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>
 		
 	<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">members</a> 
-	that responds to client requests for creation, modification, and/or enumeration of its members, and that conforms to the simple lifecycle
-	patterns and conventions in <a href="#ldpc" class="sectionRef"></a>
+	<dd>An LDPR representing a collection of <a title="Membership">member</a> resources and/or <a title="Containment">contained</a>
+	documents (information resources [[!WEBARCH]])
+	that responds to client requests for creation, modification, and/or enumeration of its members and documents, 
+	and that conforms to the simple lifecycle
+	patterns and conventions in <a href="#ldpc" class="sectionRef"></a>.
 	<p></p></dd>
 	
 	<dt><dfn>Linked Data Platform Basic Container</dfn> (<abbr title="Linked Data Platform Basic Container">LDP-BC</abbr>)</dt>
 	<dd>An <a title="Linked Data Platform Container">LDPC</a> that uses a single pre-defined predicate to link to both
-	its <a title="Containment">contained</a> and <a title="Membership">member</a> resources.
+	its <a title="Containment">contained</a> and <a title="Membership">member</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>An <a title="Linked Data Platform Container">LDPC</a> that has the flexibility of choosing what form its 
-	<a title="Membership triples">membership triples</a> take.
+	<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>An <a title="Linked Data Platform Container">LDPC</a> that is similar to a <a title="Linked Data Platform Direct Container">LDP-DC</a> 
-	but it allows an indirection with the ability to list as member a resource, such as a URI representing a real-world object,
-	that is different from the resource that is created.
+	<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 accepting creation requests that result in <a title="Membership">members</a> being added based
+	on the content of its <a title="Containment">contained</a> documents rather than the URIs assigned to those documents.
 	<p></p></dd>
 		
 	<dt><dfn>Membership</dfn></dt>
-	<dd>The relationship linking an LDP-RR (LDPCs are also LDP-RRs) and its members LDPRs.  
-	There often is a linked LDPCs that assists with managing the member LDPRs.<p></p></dd>
+	<dd>The relationship linking an LDP-RR (LDPCs are also LDP-RRs) and its member LDPRs.  
+	There often is a linked LDPC that assists with managing the member LDPRs.<p></p></dd>
 
 	<dt><dfn>Containment</dfn></dt>
 	<dd>The relationship binding an LDPC to its contained LDPRs.  The
-	lifecycle of the contained LDPR, depends on the containing LDPC.<p></p></dd>
+	lifecycle of the contained LDPR is limited by the lifecycle of the containing LDPC;
+	that is, a contained LDPR cannot be created before its containing LDPC exists, nor
+	does a contained LDPR continue to exist after its containing LDPC is deleted.
+	<p></p></dd>
 
 	<dt><dfn>Membership triples</dfn></dt>
 	<dd>A set of triples in an LDPC's state that lists its members.
@@ -542,11 +548,11 @@
 		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.
+	is represented using RDF (LDP-RR) and those using other formats (LDP-BR).  LDP-RRs have the unique
+	quality that their representation is based on RDF, which addresses 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 hold 
+	metadata associated with LDP-BRs in some cases.
 	</p>
     <figure id="fig-ldpr-types">
         <img src="images/ldpr1.png" alt="Sample separation of Linked Data Platform Resource" />
@@ -1690,7 +1696,7 @@
 	<!-- TODO: Do we need a rule for creation of ldp:contains here?  Steve's answer, no...leave to ldp:contains rule. -->
 	
 	<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
+	<a title="Linked Data Platform Binary Resource">(LDP-BRs)</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 -->
@@ -1857,7 +1863,7 @@
 	
 	<section id="ldpc-del-contremovesmbrres"><h2 class="normal">When a LDPC member resource originally created by the LDPC (for example, one whose 
 	representation was HTTP <code>POST</code>ed to the LDPC and then referenced by a membership triple) is deleted, and the LDPC server 
-	created an associated LDPR (see <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>), the LDPC server MUST also remove the associated LDPR it created.
+	created an associated LDPR (see the <a href="#ldpc-post-createbinlinkmetahdr">LDPC POST section</a>), the LDPC server MUST also remove the associated LDPR it created.
 	</h2></section><!-- Was 5.6.4 / #ldpc-5_6_4 -->
 	
 </section>
--- a/ldp.ttl	Wed Feb 05 18:19:59 2014 +0000
+++ b/ldp.ttl	Wed Feb 05 14:32:56 2014 -0500
@@ -29,8 +29,8 @@
 :RDFResource
     a rdfs:Class;
     rdfs:subClassOf :Resource;
-	rdfs:comment "A Linked Data Platform Resource (LDPR) whose state is represented in an
-		RDF representation.";
+	rdfs:comment "A Linked Data Platform Resource (LDPR) whose state is represented as 
+		RDF.";
 	vs:term_status "unstable";
 	rdfs:isDefinedBy :;
 	rdfs:label "RDFResource".
@@ -38,8 +38,8 @@
 :BinaryResource
     a rdfs:Class;
     rdfs:subClassOf :Resource;
-	rdfs:comment "A Linked Data Platform Resource (LDPR) whose state is NOT represented in
-		an RDF representation.";
+	rdfs:comment "A Linked Data Platform Resource (LDPR) whose state is NOT represented as
+		RDF.";
 	vs:term_status "unstable";
 	rdfs:isDefinedBy :;
 	rdfs:label "BinaryResource".