ldp.html
changeset 388 63e9c5b73aa2
parent 387 85cebac44f86
child 389 f1dbb042137b
--- a/ldp.html	Tue Oct 22 15:01:18 2013 -0400
+++ b/ldp.html	Tue Oct 22 15:35:52 2013 -0400
@@ -1607,12 +1607,16 @@
 		(for example, the member is managed by the same server), the LDPC server MUST also remove it from
 		the LDPC by removing the corresponding membership triple.
 	</div>	
-	<div id="ldpc-5_6_2" class="rule">5.6.2 When the LDPC server successfully completes the <code>DELETE</code> request on a LDPC, it MUST remove any
-		membership triples associated with the LDPC as indicated by the canonical <code>Request-URI</code>.  The LDPC server MAY perform additional removal 
-		of member resources. 
+	<div id="ldpc-5_6_2" class="rule">5.6.2 When a <a>LDP server</a> successfully completes a <code>DELETE</code> request 
+		on a LDPC member resource, it MUST remove any
+		membership triples associated with the deleted member resource identified by the <code>Request-URI</code>.
+	</div>	
+	<blockquote>
+		Informative note: The <a>LDP server</a> might perform additional removal 
+		of member resources, as described in the <a href="#ldp-http-method-side-effects">normative references</a> like [[HTTP11]]. 
 		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>	
+	</blockquote>
 	<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:created</code> predicate, the LDPC server MUST also remove 
 		the deleted member's <code>ldp:created</code> triple.
@@ -1981,6 +1985,8 @@
 
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote>  -->
 <ul>
+    <li>2013-10-22 - Resolve ACTION-107 Update spec to reflect 10/07 resolution on 5.6.2 LDPC deletion (JA)</li>
+    <li>2013-10-22 - Resolve ACTION-102 Make 4.6.2 informative, clarify that it re-states what http allows, and in fact it applies to all methods not just delete. (JA)</li>
     <li>2013-10-22 - Resolve ACTION-103 Change SHOULD to MUST in 4.10.2.3 "LDPR servers that initiate paging SHOULD respond to request ..." (JA)</li>
     <li>2013-10-22 - Resolve ACTION-108 move restatements of HTTP et al. out of normative sections (JA)</li>
     <li>2013-10-22 - Resolve ACTION-106 5.3.5 MUST -> SHOULD (JA)</li>