Simplified some of the container examples
authorsspeiche
Fri, 07 Feb 2014 11:44:00 -0500
changeset 467 0eed67a3db4e
parent 466 7b840138bdf1
child 468 f960af656afb
Simplified some of the container examples
ldp.html
--- a/ldp.html	Thu Feb 06 17:12:36 2014 -0500
+++ b/ldp.html	Fri Feb 07 11:44:00 2014 -0500
@@ -1147,11 +1147,8 @@
 
 <>
    a ldp:Container, ldp:BasicContainer;
-   ldp:containerResource <> ;
-   ldp:containsRelation ldp:member;
-   ldp:insertedContentRelation ldp:MemberSubject;
    dcterms:title "A very simple container";
-   ldp:member &lt;r1&gt;, &lt;r2&gt;, &lt;r3&gt;.</pre>
+   ldp:contains &lt;r1&gt;, &lt;r2&gt;, &lt;r3&gt;.</pre>
  
    	<figure id="fig-ldpc-basic">
         <img src="images/ldpc-basic.png" alt="Sample Linked Data Platform Basic Container" />
@@ -1159,7 +1156,7 @@
     </figure>
 
 	<p>This example is very straightforward - the
-	membership predicate is <code>ldp:member</code> and the other
+	membership and containment predicate are both <code>ldp:contains</code> and the other
 	consistent membership value is the container's
 	URI, occurring in the subject position of the triples. 
 	A POST to this container will create a new resource
@@ -1169,7 +1166,7 @@
 
 	<p>Sometimes it is useful to use a subject
 	other than the container itself as the consistent membership value, and/or to use
-	a predicate other than <code>ldp:member</code> as the membership predicate. Let's
+	a  predicate from an application's domain model as the membership predicate. Let's
 	start with a domain resource for a person's net worth, as illustrated below:</p>
 			
 <pre class="example" id="ldpc-ex-membership-partial"># The following is a partial representation of
@@ -1626,7 +1623,7 @@
 		<section id="ldpc-indirectmbr-basic"><h2 class="normal">
 			LDP 
 			<a title="Linked Data Platform Basic Container">Basic</a> and 
-			<a title="Linked Data Platform Direct Container">Direct</a>Containers 
+			<a title="Linked Data Platform Direct Container">Direct</a> Containers 
 			MUST behave as if they
 			have a <var>( LDPC URI, <code>ldp:insertedContentRelation</code> , <code>ldp:MemberSubject</code> )</var>
 			triple, but LDP imposes no requirement to materialize such a triple in representations.
@@ -2314,6 +2311,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-02-07 - Simplified some of the container examples (SS)</li>
 	<li>2014-02-06 - partial first pass at arnaud's email comments (JA)</li>
 	<li>2014-02-06 - fixing containment def, adding containment triples to terminology (JA)</li>
 	<li>2014-02-06 - fixing POST to create containment/membership triples, which was mangled (JA)</li>