ldp.html
changeset 462 3a7f9b05bad8
parent 461 64c0ca32c9e6
child 463 ae72388dbb82
--- a/ldp.html	Wed Feb 05 14:32:56 2014 -0500
+++ b/ldp.html	Wed Feb 05 15:39:51 2014 -0500
@@ -1232,7 +1232,7 @@
 	<p>Additionally, we could extend our net worth example to include a container for
 	advisors (people) that have managed the assets and liabilities.  We have decided
 	to identify these advisors with URLs that contain a fragment (hash) to represent
-	these real-world resources, not the documents that decribe them.</p>
+	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
@@ -1263,12 +1263,14 @@
 	
 	<p>To handle this type of indirection, the triple with predicate of <code>ldp:insertedContentRelation</code> and object of 
 	<code>foaf:primaryTopic</code> informs clients that when POSTing to this container, they will include a triple of the
-	form (LDPR, foaf:primaryTopic, LDPR#me) to inform the server which URI to use for the membership triple.</p>
+	form <code>(&lt;&gt;, foaf:primaryTopic, topic-URI)</code> to inform the server which URI to use 
+	(<code>topic-URI</code>) in the new membership triple.</p>
 	
-	<p>This type of container is also refered to as an <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a>. 
+	<p>This type of container is also referred to as an <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> 
-	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>
+	but it allows an indirection with the ability 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>
 
 	<p><a href="#fig-ldpc-types"></a> illustrates the 3 types: Basic, Direct and Indirect, along
 	with their relationship to types of LDPRs.  It is not expected that there will be a container
@@ -1684,9 +1686,10 @@
 		entity body on a 201 (Created) response.
 	</h2></section><!-- Was 5.4.1 / #ldpc-5_4_1 -->
 
-	<section id="ldpc-post-createdmbr"><h2 class="normal">After a successful HTTP <code>POST</code> request to a LDPC, the new resource MUST
-		appear as a member of the contained resource until the new resource is deleted or
-		removed by other methods. An LDPC MAY also contain resources that were
+	<section id="ldpc-post-createdmbr"><h2 class="normal">After a successful HTTP <code>POST</code> request to a LDPC, 
+		the newly created document MUST
+		appear as a contained resource of the LDPC until the newly created document is deleted or
+		removed by other methods. An LDPC's membership MAY also include resources that were
 		added through other means - for example through the user interface of
 		the site that implements the LDPC.
 	</h2></section><!-- Was 5.4.2 / #ldpc-5_4_2 -->