ldp.html
changeset 857 1aa5e5968ad3
parent 856 674c5bfc21d2
child 859 336ac8ce294d
--- a/ldp.html	Mon Oct 20 11:18:30 2014 -0400
+++ b/ldp.html	Mon Oct 20 11:27:01 2014 -0400
@@ -447,6 +447,14 @@
 	but if future versions of LDP define additional classes of triples then this definition
 	would expand to subtract out those classes as well.
 	<p></p></dd>
+
+	<dt><dfn>LDP-server-managed triples</dfn></dt>
+	<dd>
+	The portion of an LDP's triples whose behavior is constrained directly by this specification; for example,
+	membership triples and containment triples.  This portion of resources' content does <em>not</em>
+	include constraints imposed outside of LDP, for example by other specifications that the server 
+	happens to support, or by <a href="#ldpr-gen-pubclireqs">server implementation decisions</a>.
+	<p></p></dd>
   </dl>
 
 <section id="conventions">
@@ -674,9 +682,10 @@
 		<a title="LDP server">LDP servers</a> MUST
 		replace the entire persistent state of the identified resource with
 		the entity representation in the body of the request. 
-		<a title="LDP server">LDP servers</a> MAY ignore server-managed properties such as <code>dcterms:modified</code> 
-		and <code>dcterms:creator</code> if they are not under
-		client control. Any <a title="LDP server">LDP servers</a> that wish
+		<a title="LDP server">LDP servers</a> MAY ignore <a>LDP-server-managed properties</a>,
+		and MAY ignore other properties such as <code>dcterms:modified</code> 
+		and <code>dcterms:creator</code> if they are <a href="#ldpr-gen-pubclireqs">handled specially by the server</a>.
+		Any <a title="LDP server">LDP servers</a> 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
 		<code>PATCH</code>, not HTTP <code>PUT</code>.
@@ -689,7 +698,7 @@
 
 	<section id="ldprs-put-servermanagedprops"><h2 class="normal">
 		If an otherwise valid HTTP <code>PUT</code> request is received 
-		that attempts to change properties the server does not allow clients to modify, 
+		that attempts to change properties <a href="#ldpr-gen-pubclireqs">the server does not allow clients to modify</a>, 
 		<a title="LDP server">LDP servers</a> MUST 
 		fail the request by responding with a 4xx range status code (typically
 		409 Conflict). 
@@ -701,10 +710,12 @@
 	<blockquote>
 		Non-normative note: Clients might provide properties equivalent to those already in the resource's state,
 		e.g. as part of a GET/update representation/PUT sequence, and those PUT requests are intended to work as long as the 
-		server-managed properties 
+		<a title="LDP-server-managed triples">LDP-server-managed properties</a>
 		are identical on the GET response and the subsequent PUT request.
-		This is in contrast to other cases like write-once properties that the server does not allow clients to modify once set; 
-		write-once properties are under client control, they are not <a href="#ldpr-put-replaceall">server-managed</a>.
+		This is in contrast to other cases like 
+		<a href="#ldpr-put-replaceall">write-once properties that the server does not allow clients to modify once set</a>; 
+		properties like this are under client and/or server control but are not constrained by LDP, 
+		so they are not <a>LDP-server-managed triples</a>.  
 	</blockquote>
 	
 	<section id="ldprs-put-failed"><h2 class="normal">
@@ -2635,7 +2646,8 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">Candidate Recommendation Draft</a></em></blockquote> -->
 
 <ul>
-	<li>2014-10-20 - Update LDPC-Post non-normative text for Miguel thread (JA)</li>
+	<li>2014-10-20 - Define LDP-server-managed for Robert Sanderson thread (JA)</li>
+	<li>2014-10-20 - Update LDPC-Post adding non-normative note for Miguel thread (JA)</li>
 	<li>2014-10-20 - Update LDPC-Post bullet 1 with non-normative text for James Leigh thread (JA)</li>
 	<li>2014-09-25 - Included non-norm content to container intro to add clarity on application-specific extensions (SS)</li>
 </ul>