--- a/ldp.html	Tue Feb 04 20:30:48 2014 -0500
+++ b/ldp.html	Tue Feb 04 20:50:06 2014 -0500
@@ -346,7 +346,7 @@
 		The difference between the two is simply which position member-derived-URI occupies, which is usually
 		driven by the choice of <var>membership-predicate</var>.  Most predicates have a natural forward direction
 		inherent in their name, and existing vocabularies contain useful examples that read naturally in
-		each direction.  <code>rdfs:member</code> and <code>dcterms:isPartOf</code> are representative examples.
+		each direction.  <code>ldp:member</code> and <code>dcterms:isPartOf</code> are representative examples.
 		<p>
 		Each container exposes properties (see <a href="#ldpc-general" class="sectionRef"></a>)
 		that allow clients to determine which pattern it
@@ -437,7 +437,6 @@
 	<pre style="word-wrap: break-word; white-space: pre-wrap;">	@prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 	@prefix foaf:     &lt;http://xmlns.com/foaf/0.1/&gt;.
 	@prefix rdf:     &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt;.
-	@prefix rdfs:    &lt;http://www.w3.org/2000/01/rdf-schema#&gt;.
 	@prefix ldp:     &lt;http://www.w3.org/ns/ldp#&gt;.
 	@prefix xsd:     &lt;http://www.w3.org/2001/XMLSchema#&gt;.</pre>
 </section>
@@ -1059,7 +1058,7 @@
 		In the simplest cases, the
 		consistent value will be the LDPC resource's URI, but it does not
 		have to be. The membership predicate is also variable and will often
-		be a predicate from the server application vocabulary or the <code>rdfs:member</code> predicate.
+		be a predicate from the server application vocabulary or the <code>ldp:member</code> predicate.
 	</p>
 	<p>This document includes a set of guidelines for
 		creating new resources and adding them to the list of
@@ -1078,16 +1077,15 @@
 <!-- @base is here only so it's easier to paste into validators for checking -->
 # @base &lt;http://example.org/c1/&gt;
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
-@prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 
 &lt;&gt;
    a ldp:Container, ldp:BasicContainer;
    ldp:containerResource &lt;&gt; ;
-   ldp:containsRelation rdfs:member;
+   ldp:containsRelation ldp:member;
    ldp:insertedContentRelation ldp:MemberSubject;
    dcterms:title "A very simple container";
-   rdfs:member &lt;r1&gt;, &lt;r2&gt;, &lt;r3&gt;.</pre>
+   ldp:member &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" />
@@ -1095,7 +1093,7 @@
     </figure>
 
 	<p>This example is very straightforward - the
-	membership predicate is <code>rdfs:member</code> and the other
+	membership predicate is <code>ldp:member</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
@@ -1105,7 +1103,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>rdfs:member</code> as the membership predicate. Let's
+	a predicate other than <code>ldp:member</code> 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
@@ -1323,7 +1321,6 @@
 Content-Length: 325
 Link: &lt;http://www.w3.org/ns/ldp/Container&gt;; rel="type"
 
-@prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 
@@ -1331,7 +1328,7 @@
    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 rdfs:member;
+   ldp:containsRelation ldp:member;
    ldp:insertedContentRelation ldp:MemberSubject;
    dcterms:publisher &lt;http://acme.com/&gt;.</pre>
    
@@ -1446,7 +1443,7 @@
 	</h2></section><!-- Was 5.2.1 / #ldpc-5_2_1 -->
 	
 	<section id="ldpc-mbrpred"><h2 class="normal"><a title="LDP server">LDP servers</a>
-		SHOULD use the <code>rdfs:member</code> predicate as an LDPC's <a title="Membership predicate">membership predicate</a>
+		SHOULD use the <code>ldp:member</code> predicate as an LDPC's <a title="Membership predicate">membership predicate</a>
 		if there is no obvious predicate from an application vocabulary to use.
 		The state of an LDPC includes information about which
 		resources are its members, in the form of <a title="Membership triples">membership triples</a> that
@@ -2211,6 +2208,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-04 - ACTION-120 (Part 3) Added ldp:member (SS)</li>
 	<li>2014-02-04 - ACTION-120 (Part 2) Added concepts of containers (basic, direct and indirect) to LDPC intro (SS)</li>
 	<li>2014-01-30 - ACTION-120 (Part 1) Added concepts of containers (basic, direct and indirect) (SS)</li>
 	<li>2014-01-30 - ACTION-123 Added concepts of LDP-RDF-Resource and LDP-Binary-Resource (SS)</li>

--- a/ldp.ttl	Tue Feb 04 20:30:48 2014 -0500
+++ b/ldp.ttl	Tue Feb 04 20:50:06 2014 -0500
@@ -188,6 +188,15 @@
 	rdfs:domain :Container;
 	rdfs:range :Resource.
 
+:member
+	a rdf:Property;
+	rdfs:comment "LDP servers should use this predicate as the membership predicate if there is no obvious predicate from an application vocabulary to use.";
+	vs:term_status "unstable";
+	rdfs:domain :Resource;
+	rdfs:isDefinedBy :;
+	rdfs:label "member";
+	rdfs:range rdfs:Resource.
+
 :created
 	a rdf:Property;
 	rdfs:comment "Links a container with resources created through the container.";