--- a/ldp.html	Mon Jul 08 13:25:58 2013 -0400
+++ b/ldp.html	Mon Jul 08 15:25:55 2013 -0400
@@ -1374,7 +1374,7 @@
 		creation of any kind of resource, for example binary resources.
 	</div>
 	<div id="ldpc-5_4_4" class="rule">5.4.4 For servers that support create, LDPC servers MUST create an LDPR from a
-		RDF representation in the request entity body.  The LDPR could also be a LDPC, therefore servers may
+		RDF representation in the request entity body.  The newly created LDPR could also be a LDPC, therefore servers may
 		allow the creations of LDPCs within a LDPC. 
 	</div>
 	
@@ -1460,6 +1460,22 @@
 		specifications such as LDP.
 	</div>
 	
+	<div class="ldp-issue-pending">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/79">ISSUE-79</a></div>
+	ldp:contains
+	</div>	
+		
+	<div id="ldpr-5_4_14" class="rule">5.4.14 LDPCs that create new member resources MAY add triples to the container 
+		as part of member creation to reflect its factory role.  
+		LDP defines the <code>ldp:contains</code> predicate for this purpose.  
+		An LDPC that tracks members created through the LDPC MUST add a triple
+		whose subject is the container's URI, 
+		whose predicate is <code>ldp:contains</code>, and
+		whose object is the newly created member resource's URI; 
+		it MAY add other triples as well.
+	</div>
+	
+	
 </section>
 
 <section>
@@ -1512,9 +1528,20 @@
 	</div>	
 	<div id="ldpc-5_6_2" class="rule">5.6.2 When the LDPC server successfully completes the DELETE request on a LDPC, it MUST remove any
 		membership triples associated with the LDPC as indicated by the canonical Request-URI.  The LDPC server MAY perform additional removal 
-		of member resources. The server could decide some additional cleanup tasks for resources it knows are no longer referenced or have not
+		of member resources. 
+		For example, the server could perform additional cleanup tasks for resources it knows are no longer referenced or have not
 		been accessed for some period of time.
 	</div>
+	
+	<div class="ldp-issue-pending">
+	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/79">ISSUE-79</a></div>
+	ldp:contains
+	</div>	
+		
+	<div id="ldpc-5_6_3" class="rule">5.6.3 When the conditions in <a href="#ldpc-5_6_1">5.6.1</a> hold, and the LDPC tracks member 
+		resources that it created using the <code>ldp:contains</code> predicate, the LDPC server MUST also remove 
+		the deleted member's <code>ldp:contains</code> triple.
+	</div>	
 
 </section>
 
@@ -1647,7 +1674,7 @@
 <ul>
 	<li>2013-07-08 - ISSUE-  (JA)</li>
 	<li>2013-07-08 - ISSUE-  (JA)</li>
-	<li>2013-07-08 - ISSUE-  (JA)</li>
+	<li>2013-07-08 - ISSUE-79 ldp:contains  (JA)</li>
 	<li>2013-07-08 - ISSUE-80 Accept-Post (JA)</li>
 	<li>2013-07-08 - ISSUE-32 Must support options (JA)</li>
 	<li>2013-07-08 - ISSUE-78 No client inferencing  (JA)</li>

--- a/ldp.ttl	Mon Jul 08 13:25:58 2013 -0400
+++ b/ldp.ttl	Mon Jul 08 15:25:55 2013 -0400
@@ -152,3 +152,13 @@
 	rdfs:label "non-member-resource";
 	rdfs:domain ldp:Container;
 	rdfs:range ldp:Container.
+
+	:contains
+	a rdf:Property;
+	rdfs:comment "Links a container with resources created through the container.";
+	vs:term_status "unstable";
+	rdfs:domain :Container;
+	rdfs:isDefinedBy :;
+	rdfs:label "contains";
+	rdfs:range rdfs:Resource.
+