--- a/ldp.html	Wed Jul 10 10:39:34 2013 -0400
+++ b/ldp.html	Wed Jul 10 11:45:09 2013 -0400
@@ -1288,11 +1288,6 @@
 		any kind of resource identified by its URI, LDPR or otherwise.
 	</div>
 	
-	<div class="ldp-issue-open">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/51">ISSUE-51</a></div>
-	Linking from a Resource to its Containers (not the containers the resource is in)
-	</div>
-	
 	<div id="ldpc-5_2_4" class="rule">5.2.4 An LDPC MUST contain one triple 
 		whose subject is the LDPC URI, 
 		whose predicate is the <code>ldp:membershipSubject</code>, 
@@ -1358,12 +1353,16 @@
 	
 
 	<div id="ldpc-5_2_10" class="rule">5.2.10 Some LDPC's have membership object's that are not directly
-	    URIs minted upon LDPC member creation, for example hash URIs [[RFC3986]]. To determine which object URI to use for the
-	    membership triple, LDPC's MUST contain triple whose subject is the LDPC URI, predicate is <code>ldp:membershipObject</code>,
-	    with an object <var>MO</var>. Where <var>MO</var> can be used to locate a triple of the form: <var>(LDPC URI, MO, N)</var> and 
+	    URIs minted upon LDPC member creation, for example URIs with non-empty fragment identifier [[RFC3986]]. 
+	    To determine which object URI to use for the  membership triple, LDPC's MUST contain triple whose
+	    subject is the LDPC URI, predicate is <code>ldp:membershipObject</code>, with an object <var>MO</var>. 
+	    Where <var>MO</var> and the HTTP URI <var>R</var> from POST create (as found in HTTP response <code>Location</code> header) can be 
+	    used to locate a triple of the form: <var>(R, MO, N)</var> and 
 	    where <var>N</var> can be used to construct the membership triple of the form: <var>(membership subject, membership predicate, N)</var>.
 	    When <code>ldp:membershipPredicateInverse</code> is used instead of <code>ldp:membershipPredicate</code>, the membership triple MUST be
-	    of the form: <var>(N, membership predicate, membership subject)</var>.
+	    of the form: <var>(N, membership predicate, membership subject)</var>. To indicate that the member resource URI is the membership object
+	    (the default or typical case), the object MUST be set to predefined URI <code>ldp:MemberSubject</code> such that it forms the triple: 
+	    <var>(LDPC URI, <code>ldp:membershipObject</code>, <code>ldp:MemberSubject</code>)</var>.
 	</div>
 	<div class="ldp-issue-pending">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/72">ISSUE-72</a></div>
@@ -1953,6 +1952,7 @@
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
 -->
 <ul>
+	<li>2013-07-10 - ISSUE-72 take 2 - added ldp:MemberSubject to handle default case (SS)</li>
 	<li>2013-07-10 - ISSUE-72 adding 5.2.10 for ldp:membershipObject (SS)</li>
 	<li>2013-07-09 - ISSUE-58 inlining - actions 87-89 inclusive  (JA)</li>
 	<li>2013-07-08 - Moved 5.7.* sections out of HEAD and into OPTIONS as 5.9.*, added 4.6.2 (SS)</li>

--- a/ldp.ttl	Wed Jul 10 10:39:34 2013 -0400
+++ b/ldp.ttl	Wed Jul 10 11:45:09 2013 -0400
@@ -188,4 +188,13 @@
 	rdfs:isDefinedBy :;
 	rdfs:label "inlinedResource";
 	rdfs:range rdfs:Resource.
+
+:MemberSubject
+	a rdf:Description;
+	rdfs:comment "Used to indicate default and typical behavior when ldp:membershipObject is the same as the member resource.";
+	vs:term_status "unstable";
+	rdfs:isDefinedBy :;
+	rdfs:label "MemberSubject".
 	
+
+