ldp.html
changeset 500 c52f08081c8a
parent 498 9ab1339e0013
child 501 a1634728bc5d
--- a/ldp.html	Tue Feb 18 16:12:25 2014 -0500
+++ b/ldp.html	Thu Feb 20 16:16:00 2014 -0500
@@ -9,6 +9,7 @@
     TODO: Improve LDPC intro by explaining simply that LDP-DC restricts LDPC and LDP-BC restricts LDP-DC.
 	TODO: Add new "discovery of server capabilities" non-norm section
     TODO: Missing namespace definition clause?
+    TODO: 6.2.2 -- consider 6.2.2.1 rules LDP-DC MUST BE a LDPC, ... to deal with inferencing
  -->
 <html>
   <head>
@@ -659,7 +660,7 @@
 <section id="ldpr-HTTP_POST">
 <h2>HTTP POST</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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 no new requirements for LDPRs.
@@ -676,7 +677,7 @@
 <section id="ldpr-HTTP_PUT">
 <h2>HTTP PUT</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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.
@@ -750,7 +751,7 @@
 <section id="ldpr-HTTP_DELETE">
 <h2>HTTP DELETE</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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.
@@ -774,7 +775,7 @@
 <section id="ldpr-HTTP_PATCH">
 <h2>HTTP PATCH</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		Per [[RFC5789]], 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.
@@ -783,11 +784,7 @@
 	<p>
 		Any server-imposed constraints on LDPR creation or update  
 		<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
-	</p>	
-
-	<section id="ldpr-patch-create"><h2 class="normal"><a title="LDP server">LDP servers</a> SHOULD NOT allow clients to create new resources using <code>PATCH</code>.
-		<a href="#ldpc-HTTP_POST"><code>POST</code> (to an LDPC)</a> and/or <a href="#ldpr-HTTP_PUT"><code>PUT</code></a> should be used as the standard way to create new LDPRs.
-	</h2></section><!-- Was 4.8.3 / #ldpr-4_8_3 -->
+	</p>
 	
 	<section id="ldpr-patch-acceptpatch"><h2 class="normal"><a title="LDP server">LDP servers</a> that support <code>PATCH</code> MUST
 		include an <code>Accept-Patch</code> HTTP response header [[!RFC5789]] on HTTP <code>OPTIONS</code>
@@ -1302,13 +1299,14 @@
 		or MAY be another resource (as in the <a href="#ldpc-ex-membership-subj">net worth LDP-DC example</a>).  See also
 		section on <a href="#ldpc-mbrpred">LDPC membership predicates</a>.
 	</h2></section><!-- Was 5.3.1 / #ldpc-5_3_1 -->
+	<!-- TODO: Is this^ still right?  Feels like MUST should be on containment triples and SHOUDl on membership. -->
 	
 </section>
 
 <section id="ldpc-HTTP_POST">
 <h2>HTTP POST</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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 LDPCs.
@@ -1451,7 +1449,7 @@
 <section id="ldpc-HTTP_PUT">
 <h2>HTTP PUT</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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 LDPCs.
@@ -1466,6 +1464,7 @@
 		if the server receives such a request, it SHOULD respond with a 409
 		(Conflict) status code.
 	</h2></section><!-- Was 5.5.1 / #ldpc-5_5_1 -->
+	<!-- TODO: Some arguing this is too strong, should we flip to a MAY? -->
 	
 	<section id="ldpc-put-create"><h2 class="normal"><a title="LDP server">LDP servers</a> that allow member creation via <code>PUT</code> 
 		SHOULD NOT re-use URIs.  For RDF representations (LDP-RSs),the created resource
@@ -1477,7 +1476,7 @@
 <section id="ldpc-HTTP_DELETE">
 <h2>HTTP DELETE</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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 LDPCs.
@@ -1515,7 +1514,7 @@
 <section id="ldpc-HTTP_PATCH">
 <h2>HTTP PATCH</h2>
 	<p>
-		Per [HTTP11], this HTTP method is optional and 
+		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 LDPCs.
@@ -2097,6 +2096,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-20 - Removed rule on PATCH create, as it doesn't add any substantive over RFC5789 (SS) </li>
 	<li>2014-02-18 - Factored out paging and sorting into separate spec LDP-Paging (SS) </li>
 	<li>2014-02-18 - Reference cleanup and tweak LDP-RS term (SS) </li>
 	<li>2014-02-17 - Reference to RDF Document into terms (SS) </li>