changeset 61 2f8a2d58e65c
parent 60 97516e223fb8
child 64 555e00343af1
--- a/ldp.html	Tue Feb 12 13:27:01 2013 -0500
+++ b/ldp.html	Tue Feb 12 15:25:09 2013 -0500
@@ -404,20 +404,15 @@
 	<div id="ldpr-4_4_1" class="rule">4.4.1 If HTTP PUT is performed on an existing resource, LDPR servers MUST
 		replace the entire persistent state of the identified resource with
-		the entity representation in the body of the request. The only
-		recognized exception are the properties <code>dcterms:modified</code>
-		and <code>dcterms:creator</code> that are never under
-		client control - LDPR servers MUST ignore any values of these
-		properties that are provided by the client. Any LDPR servers that wish
+		the entity representation in the body of the request. 
+		BPR servers MAY ignore server managed properties such as <code>dcterms:modified</code> 
+		and <code>dcterms:creator</code> if they are not under
+		client control. Any LDPR servers that wish
 		to support a more sophisticated merge of data provided by the client
 		with existing state stored on the server for a resource MUST use HTTP
+	</div>
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/11">ISSUE-11</a></div>
-	Do we need to define server-managed properties or do we leave them to applications?
-	</div>
-	</div>
 	<div id="ldpr-4_4_2" class="rule">4.4.2 LDPR clients SHOULD use the HTTP <code>If-Match</code>
 		header and HTTP <code>ETags</code> to ensure it isn’t
 		modifying a resource that has changed since the client last retrieved
@@ -1365,6 +1360,7 @@
 	<li>2013-01-16 - Added new issues ranging from 26-43. Removed closed/deferred issues: 2 & 3 (SS)</li>
 	<li>2013-02-12 - Fixed up previous publication links (SS) </li>
 	<li>2013-02-12 - ISSUE-10 - 4.1.12 to be MUST use entity tags (either weak or strong ones) (SS) </li>
+	<li>2013-02-12 - ISSUE-11 - 4.4.1 Relaxed the MUST ignore dc:modified/creator to MAY (SS) </li>
 <section class='appendix informative' id="todos">