ldp.html
changeset 485 195cdbad4852
parent 484 3b857f66ed6d
child 486 974b4886835b
--- a/ldp.html	Wed Feb 12 08:03:05 2014 -0500
+++ b/ldp.html	Wed Feb 12 08:55:47 2014 -0500
@@ -721,12 +721,12 @@
 		Per [HTTP11], this HTTP method is optional and 
 		this specification does not require <a title="LDP server">LDP servers</a> to support it.
 		When a LDP server chooses to support this method, 
-		this specification imposes the following new requirements for LDPRs.
+		this specification imposes no new requirements for LDPRs.
 	</p>
 
-	<p>Clients can create LDPRs via <code>POST</code> (<a href="#ldpc-HTTP_POST" class="sectionRef"></a>) or
-		<code>PUT</code> (<a href="#ldpc-HTTP_PUT" class="sectionRef"></a>) to a LDPC, see those 
-		sections for more details.  Any server-imposed constraints on LDPR creation or update  
+	<p>Clients can create LDPRs via <code>POST</code> (<a href="#ldpc-HTTP_POST" class="sectionRef"></a>) to a LDPC, 
+		via <code>PUT</code> (<a href="#ldpr-HTTP_PUT" class="sectionRef"></a>), or any other methods allowed
+		for HTTP resources.  Any server-imposed constraints on LDPR creation or update  
 		<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
 
 	</p>
@@ -2574,6 +2574,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-02-12 - Updated LDPR Post reference to Put, which had implied that clients could PUT (to an LDPC) to create an LDPR (JA)</li>
 	<li>2014-02-12 - Updated containerResource on examples 6 and 7, section 6.1, in resp to public-ldp email (JA)</li>
 	<li>2014-02-12 - Updated LDP-IC definition per email thread (JA)</li>
 	<li>2014-02-11 - Updated LDPC create ldp:contains (errant MAY to MUST, resolving conflicting statements) (JA)</li>