--- a/ldp.html	Mon Apr 15 08:47:09 2013 -0400
+++ b/ldp.html	Thu Apr 18 16:29:34 2013 -0400
@@ -975,21 +975,38 @@
 		from the server application vocabulary. If there is no obvious
 		predicate from the server application vocabulary to use, LDPC servers
 		SHOULD use the <code>rdfs:member</code> predicate.
-		
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/21">ISSUE-21</a></div>
-	container affordances
-	</div>	
 	</div>
+	
 	<div id="ldpc-5_2_4" class="rule">5.2.4 An LDPC MUST contain one triple containing the <code>ldp:membershipSubject</code>
 		predicate when the membership subject is not the LDPC itself.  
 		This triple's object provides clients with the LDPC's membership subject URI.
 	</div>
+	
 	<div id="ldpc-5_2_5" class="rule">5.2.5 An LDPC MUST contain one triple containing the <code>ldp:membershipPredicate</code>
-		predicate when
-		the container predicate is not <code>rdfs:member</code>.
-		This triple's object provides clients with the LDPC's membership predicate URI.
+		or <code>ldp:membershipPredicateInverse</code> predicate when
+		the membership predicate is not <code>rdfs:member</code>.
 	</div>
+	
+	<div id="ldpc-5_2_5_1" class="rule">5.2.5.1 For a given triple <var>T<sub>m</sub></var> with a subject <var>C<sub>m</sub></var>
+	of the LDPC and predicate of 
+	<code>ldp:membershipPredicate</code>, the object MUST be the URI of the membership predicate <var>P<sub>m</sub></var> used to
+	indicate membership to the linked to LDPC, or simply: <var>T<sub>m</sub> = ( C<sub>m</sub></var>, <code>ldp:membershipPredicate</code>, <var>P<sub>m</sub>)</var>. 
+	For the membership predicate URI object used in the previous triple <var>T<sub>m</sub></var>, it would be found in a resource's
+	same subject <var>R<sub>m</sub></var> and same predicate <var>P<sub>m</sub></var> membership triples of the form: 
+	(<var>R<sub>m</sub></var>, <var>P<sub>m</sub></var>, <var>MR<sub>n</sub></var>), where <var>MR<sub>n</sub></var> represents URI of
+	of a member resource.
+	</div>
+	
+	<div id="ldpc-5_2_5_2" class="rule">5.2.5.2  For a given triple <var>T<sub>i</sub></var> with a subject <var>C<sub>i</sub></var>
+	of the LDPC and predicate of 
+	<code>ldp:membershipPredicateInverse</code>, the object MUST be the URI of the membership predicate <var>P<sub>i</sub></var> used to
+	indicate membership to the linked to LDPC, or simply: <var>T<sub>i</sub> = ( C<sub>i</sub></var>, <code>ldp:membershipPredicateInverse</code>, <var>P<sub>i</sub>)</var>. 
+	For the membership predicate URI object used in the previous triple <var>T<sub>i</sub></var>, it would be found in a resource's
+	object subject <var>R<sub>m</sub></var> and same predicate <var>P<sub>i</sub></var> membership triples of the form: 
+	(<var>MR<sub>n</sub></var>, <var>P<sub>i</sub></var>, <var>R<sub>i</sub></var>), where <var>MR<sub>n</sub></var> represents URI of
+	of a member resource.
+	</div>
+	
 	<div id="ldpc-5_2_6" class="rule">5.2.6 The representation of a LDPC MAY include an arbitrary number of
 		additional triples whose subjects are the members of the container,
 		or that are from the representations of the members (if they have RDF
@@ -1187,7 +1204,8 @@
 	</div>
 	<div id="ldpc-5_5_2" class="rule">5.5.2 LDPC servers MAY allow updating LDPC non-membership properties using
 		HTTP PUT on <code>&lt;containerURL&gt;?non-member-properties</code>, which
-		MAY exclude server-managed properties such as <code>ldp:membershipSubject</code> and <code>ldp:membershipPredicate</code>.
+		MAY exclude server-managed properties such as <code>ldp:membershipSubject</code>, <code>ldp:membershipPredicate</code>
+		and <code>ldp:membershipPredicateInverse</code>.
 	</div>
 </section>
 
@@ -1265,6 +1283,7 @@
 </p>
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130307/">Second Public Working Draft</a></em></blockquote>
 <ul>
+	<li>2013-04-15 - ISSUE-21 Added ldp:membershipPredicateInverse to 5.2.5 &amp; 5.5.2, created 5.2.5.1 &amp; 5.3.5.2 to indicate difference. (SS)</li>
 	<li>2013-04-15 - ISSUE-39 Moved informative text from 5.4.5 into 5.4.1, shifted subsections .6-.10 (SS)</li>
 	<li>2013-04-15 - Expanded on wording for 4.3 to be more consistent (SS)</li>
 	<li>2013-04-08 - Fixed two old references to BPR (SS)</li>