Adopted new predicate names: ldp:membershipResource, ldp:hasMemberRelation and ldp:isMemberOfRelation
authorsspeiche
Mon, 17 Feb 2014 13:23:43 -0500
changeset 488 6bc3c9a2b2f7
parent 487 e1e3f400d318
child 489 a33c03215d88
Adopted new predicate names: ldp:membershipResource, ldp:hasMemberRelation and ldp:isMemberOfRelation
ldp.html
ldp.ttl
--- a/ldp.html	Mon Feb 17 12:24:17 2014 -0500
+++ b/ldp.html	Mon Feb 17 13:23:43 2014 -0500
@@ -13,8 +13,8 @@
 	referring readers to SPARQL 1.1.  Which normative reference do we want? http://www.w3.org/TR/sparql11-query/ Ask Sandro
 	TODO: Add new "discovery of server capabilities" non-norm section
  Various pre-LC comments:
-    - TODO: (now 6.2.7) 5.2.5.1 For a given triple T with a subject C of the LDPC and predicate of ldp:containsRelation, 
-	  5.2.5.2 For a given triple T with a subject C of the LDPC and predicate of ldp:containedByRelation, 
+    - TODO: (now 6.2.7) 5.2.5.1 For a given triple T with a subject C of the LDPC and predicate of ldp:hasMemberRelation, 
+	  5.2.5.2 For a given triple T with a subject C of the LDPC and predicate of ldp:isMemberOfRelation, 
 	  5.2.10 Some LDPC's have membership object's that are not directly URIs minted upon LDPC member creation, 
 	  (JohnA) I found these particularly hard to read.  And I perpetrated the SortCollation paragraphs.  
 	  Links to examples might be an 80-20 solution. 
@@ -1242,8 +1242,8 @@
 <>
    a ldp:Container, ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:containerResource <http://example.org/netWorth/nw1/>;
-   ldp:containsRelation o:asset;
+   ldp:membershipResource <http://example.org/netWorth/nw1/>;
+   ldp:hasMemberRelation o:asset;
    ldp:contains <a1>, <a2>.
 </pre>
 
@@ -1257,8 +1257,8 @@
 &lt;&gt;
    a ldp:Container, ldp:DirectContainer;
    dcterms:title "The liabilities of JohnZSmith";
-   ldp:containerResource &lt;http://example.org/netWorth/nw1/&gt;;
-   ldp:containsRelation o:liability;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1/&gt;;
+   ldp:hasMemberRelation o:liability;
    ldp:contains &lt;l1&gt;, &lt;l2&gt;, &lt;l3&gt;.
 </pre>
 
@@ -1322,8 +1322,8 @@
 &lt;advisorContainer/&gt;
    a ldp:Container, ldp:IndirectContainer;
    dcterms:title "The asset advisors of JohnZSmith";
-   ldp:containerResource &lt;&gt;;
-   ldp:containsRelation o:advisor;
+   ldp:membershipResource &lt;&gt;;
+   ldp:hasMemberRelation o:advisor;
    ldp:insertedContentRelation foaf:primaryTopic;
    ldp:contains
    	 &lt;advisorContainer/bob&gt;,
@@ -1420,8 +1420,8 @@
 &lt;http://example.org/container1/&gt;
    a ldp:Container, ldp:DirectContainer;
    dcterms:title "A Linked Data Platform Container of Acme Resources";
-   ldp:containerResource &lt;http://example.org/container1/&gt;;
-   ldp:containsRelation ldp:member;
+   ldp:membershipResource &lt;http://example.org/container1/&gt;;
+   ldp:hasMemberRelation ldp:member;
    ldp:insertedContentRelation ldp:MemberSubject;
    dcterms:publisher &lt;http://acme.com/&gt;.</pre>
    
@@ -1481,8 +1481,8 @@
 &lt;&gt;
    a ldp:Container, ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-   ldp:containsRelation o:asset;
+   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+   ldp:hasMemberRelation o:asset;
    ldp:insertedContentRelation ldp:MemberSubject.
 
 &lt;?firstPage&gt;
@@ -1570,14 +1570,14 @@
 	<section id="ldpc-containres"><h2 class="normal">Each <a title="Linked Data Platform Direct Container">LDP Direct Container</a>
 		and <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a> representation MUST contain exactly one triple 
 		whose subject is the LDPC URI, 
-		whose predicate is the <code>ldp:containerResource</code>, 
+		whose predicate is the <code>ldp:membershipResource</code>, 
 		and whose object is the LDPC's <var>membership-constant-URI</var>.
 		Commonly the LDPC's URI is the <var>membership-constant-URI</var>, but LDP does not require this.
 	</h2>
 		<section id="ldpc-containres-basic"><h2 class="normal"><a title="Linked Data Platform Basic Container">LDP-BCs</a> MUST
 			behave as if their state contains the triple 
 			whose subject is the LDPC URI, 
-			whose predicate is <code>ldp:containerResource</code>, 
+			whose predicate is <code>ldp:membershipResource</code>, 
 			and whose object is the LDPC URI (subject and object are the same URI), 
 			but there is no requirement to materialize this triple in LDP-BC representations.
 		</h2></section>
@@ -1586,10 +1586,10 @@
 	<section id="ldpc-containtriples"><h2 class="normal">Each <a title="Linked Data Platform Direct Container">LDP Direct Container</a>
 		and <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a> representation MUST contain exactly one triple 
 		whose subject is the LDPC URI, 
-		and whose predicate is either <code>ldp:containsRelation</code> or <code>ldp:containedByRelation</code>. 
+		and whose predicate is either <code>ldp:hasMemberRelation</code> or <code>ldp:isMemberOfRelation</code>. 
 		The object of the triple is constrained by other sections, such as
-		<a href="#ldpc-containtriple-relation" class="sectionRef">ldp:containsRelation</a> or 
-		<a href="#ldpc-containtriple-byrelation" class="sectionRef">ldp:containedByRelation</a>, based on the 
+		<a href="#ldpc-containtriple-relation" class="sectionRef">ldp:hasMemberRelation</a> or 
+		<a href="#ldpc-containtriple-byrelation" class="sectionRef">ldp:isMemberOfRelation</a>, based on the 
 		<a title="Membership triples">membership triple</a> 
 		pattern used by the container.
 	</h2><!-- Was 5.2.5 / #ldpc-5_2_5 -->
@@ -1600,13 +1600,13 @@
 		pattern is <var>( membership-constant-URI , membership-predicate , member-derived-URI )</var> MUST
 		contain exactly one triple
 		whose subject is the LDPC URI, 
-		whose predicate is <code>ldp:containsRelation</code>, 
+		whose predicate is <code>ldp:hasMemberRelation</code>, 
 		and whose object is the URI of <var>membership-predicate</var>.
 	</h2>
 			<section id="ldpc-containtriple-basic"><h2 class="normal"><a title="Linked Data Platform Basic Container">LDP-BCs</a> MUST
 			behave as if their state contains the triple 
 			whose subject is the LDPC URI, 
-			whose predicate is <code>ldp:containsRelation</code>, 
+			whose predicate is <code>ldp:hasMemberRelation</code>, 
 			and whose object is <code>ldp:contains</code>,
 			but there is no requirement to materialize this triple in LDP-BC representations.
 		</h2></section>
@@ -1618,7 +1618,7 @@
 		pattern is <var>( member-derived-URI , membership-predicate , membership-constant-URI )</var> MUST
 		contain exactly one triple
 		whose subject is the LDPC URI, 
-		whose predicate is either <code>ldp:containedByRelation</code>, 
+		whose predicate is either <code>ldp:isMemberOfRelation</code>, 
 		and whose object is the URI of <var>membership-predicate</var>.
 	</h2></section><!-- Was 5.2.5.2 / #ldpc-5_2_5_2 -->
 	</section>
@@ -2342,8 +2342,8 @@
 	&lt;&gt;
 	   a ldp:Container, ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:hasMemberRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 
 	&lt;http://example.org/netWorth/nw1&gt;
@@ -2384,8 +2384,8 @@
 	&lt;&gt;
 	   a ldp:Container, ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:hasMemberRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 	</pre>
 
@@ -2415,8 +2415,8 @@
 	&lt;&gt;
 	   a ldp:Container, ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:hasMemberRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 	</pre>
 
@@ -2451,8 +2451,8 @@
 	&lt;&gt;
 	   a ldp:Container, ldp:DirectContainer;
 	   dcterms:title "The assets of JohnZSmith";
-	   ldp:containerResource &lt;http://example.org/netWorth/nw1&gt;;
-	   ldp:containsRelation o:asset;
+	   ldp:membershipResource &lt;http://example.org/netWorth/nw1&gt;;
+	   ldp:hasMemberRelation o:asset;
 	   ldp:insertedContentRelation ldp:MemberSubject.
 
 	&lt;http://example.org/netWorth/nw1&gt;
@@ -2575,6 +2575,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-17 - Adopted new predicate names: ldp:membershipResource, ldp:hasMemberRelation and ldp:isMemberOfRelation (SS) </li>
 	<li>2014-02-12 - Updated LDPR Post reference to Put, which had implied that clients could PUT (to an LDPC) to create an LDPR (JA)</li>
 	<li>2014-02-12 - Updated containerResource on examples 6 and 7, section 6.1, in resp to public-ldp email (JA)</li>
 	<li>2014-02-12 - Updated LDP-IC definition per email thread (JA)</li>
--- a/ldp.ttl	Mon Feb 17 12:24:17 2014 -0500
+++ b/ldp.ttl	Mon Feb 17 13:23:43 2014 -0500
@@ -138,31 +138,31 @@
 	rdfs:isDefinedBy :;
 	rdfs:label "Descending".
 	
-:containsRelation
+:hasMemberRelation
 	a rdf:Property;
-	rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < membership-constant-URI , object-of-containsRelation, member-URI >.";
+	rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < membership-constant-URI , object-of-hasMemberRelation, member-URI >.";
 	vs:term_status "unstable";
 	rdfs:domain :Container;
 	rdfs:isDefinedBy :;
-	rdfs:label "containsRelation";
+	rdfs:label "hasMemberRelation";
 	rdfs:range rdf:Property.
 
-:containedByRelation
+:isMemberOfRelation
 	a rdf:Property;
-	rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < member-URI , object-of-containedByRelation, membership-constant-URI >.";
+	rdfs:comment "Indicates which predicate is used in membership triples, and that the membership triple pattern is < member-URI , object-of-isMemberOfRelation, membership-constant-URI >.";
 	vs:term_status "unstable";
 	rdfs:domain :Container;
 	rdfs:isDefinedBy :;
-	rdfs:label "containedByRelation";
+	rdfs:label "isMemmberOfRelation";
 	rdfs:range rdf:Property.
 	
-:containerResource
+:membershipResource
 	a rdf:Property;
-	rdfs:comment "Indicates the membership-constant-URI in a membership triple.  Depending upon the membership triple pattern a container uses, as indicated by the presence of ldp:containsRelation or ldp:containedByRelation, the membership-constant-URI might occupy either the subject or object position in membership triples.";
+	rdfs:comment "Indicates the membership-constant-URI in a membership triple.  Depending upon the membership triple pattern a container uses, as indicated by the presence of ldp:hasMemberRelation or ldp:isMemberOfRelation, the membership-constant-URI might occupy either the subject or object position in membership triples.";
 	vs:term_status "unstable";
 	rdfs:domain :Container;
 	rdfs:isDefinedBy :;
-	rdfs:label "containerResource";
+	rdfs:label "membershipResource";
 	rdfs:range rdf:Property.
 	
 :insertedContentRelation