ACTION-120 (Part 1) Added concepts of containers (basic, direct and indirect)
authorsspeiche
Tue, 04 Feb 2014 17:11:33 -0500
changeset 451 f68e4a59fba1
parent 450 e8d84dbc86dc
child 452 c4b538b7e57f
ACTION-120 (Part 1) Added concepts of containers (basic, direct and indirect)
images/ldpc-basic.png
images/ldpr1.png
ldp.html
Binary file images/ldpc-basic.png has changed
Binary file images/ldpr1.png has changed
--- a/ldp.html	Mon Feb 03 09:50:16 2014 -0500
+++ b/ldp.html	Tue Feb 04 17:11:33 2014 -0500
@@ -306,7 +306,7 @@
 	
 	<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 predefined predicate to simply link to 
-	its contained (ldp:contains) resources.
+	its <a title="Containment">contained</a> resources.
 	<p></p></dd>
 	
 	<dt><dfn>Linked Data Platform Direct Container</dfn> (<abbr title="Linked Data Platform Direct Container">LDP-DC</abbr>)</dt>
@@ -315,16 +315,17 @@
 	<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 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 that is different from the one that is created.
-	<p></p></dd>	
+	<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.
+	<p></p></dd>
 		
 	<dt><dfn>Membership</dfn></dt>
-	<dd>The relationship binding an LDP-RR (LDPCs are also LDP-RRs) and its members LDPRs.  There often is a 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 members LDPRs.  
+	There often is a linked LDPCs 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.  This link is direction between the LDPC and its contained LDPRs.  The
+	<dd>The relationship binding an LDPC to its contained LDPRs.  The
 	lifecycle of the contained LDPR, depends on the containing LDPC.<p></p></dd>
 
 	<dt><dfn>Membership triples</dfn></dt>
@@ -545,7 +546,7 @@
 	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">
+    <figure id="fig-ldpr-types">
         <img src="images/ldpr1.png" alt="Sample separation of Linked Data Platform Resource" />
         <figcaption>Samples of different types of LDPRs</figcaption>
     </figure>
@@ -753,7 +754,7 @@
 	
 	<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.  
-		This is a consequence of the requirement to enable simple creation and modification of LPDRs.
+		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>
 		
@@ -1662,7 +1663,7 @@
 	
 	<section id="ldpc-post-mincontraints"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD allow clients to create new resources without
 		requiring detailed knowledge of application-specific constraints.
-		This is a consequence of the requirement to enable simple creation and modification of LPDRs.
+		This is a consequence of the requirement to enable simple creation and modification of LDPRs.
 		<!-- TODO: Consider reference to 4.2.13 to include Link rel='desribedBy' header for such constraints.  
 		           Also, should this call out LDPRs explicity?  Would think we could just have "resources" statement. -->
 	</h2></section><!-- Was 5.4.9 / #ldpc-5_4_9 -->