ldp.html
changeset 115 c8f6c689d373
parent 114 1629ff899e0e
child 116 48fabccf847c
--- a/ldp.html	Tue May 21 08:55:30 2013 -0400
+++ b/ldp.html	Tue May 21 12:00:16 2013 -0400
@@ -507,7 +507,7 @@
 		This is a consequence of the requirement to <a href="#ldpr-4_1_11">enable simple creation and modification</a> of LPDRs.
 	</div>
 	<div id="ldpr-4_7_3" class="rule">4.7.3 LDPR servers SHOULD NOT allow clients to create new resources using PATCH.
-		<a href="#ldpr-post-1">POST (to an LDPC)</a> and/or <a href="#ldpr-put">PUT</a> should be used as the standard way to create new LDPRs.
+		<a href="#ldpc-HTTP_POST">POST (to an LDPC)</a> and/or <a href="#ldpc-HTTP_PUT">PUT</a> should be used as the standard way to create new LDPRs.
 	</div>
 	
 	<div class="ldp-issue">
@@ -1181,25 +1181,26 @@
 		
 	<div class="ldp-issue">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/20">ISSUE-20</a></div>
-	Identifying and naming POSTed resources
+	Identifying and naming POSTed resources using &lt;&gt;
 	</div>	
 	</div>
 	
 	<div id="ldpc-5_4_8" class="rule">5.4.8 LDPC servers SHOULD assign the subject URI for the resource to be
-		created using server application specific rules.
+		created using server application specific rules in the absence of a <a href="#ldpc-5_4_10">client hint</a>.
 	</div>
 	
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/43">ISSUE-43</a></div>
-	hint at naming a resource on creation
-	</div>
-	
-	
 	<div id="ldpc-5_4_9" class="rule">5.4.9 LDPC servers SHOULD allow clients to create new resources without
 		requiring detailed knowledge of application-specific constraints.
 		This is a consequence of the requirement to 
 		<a href="#ldpr-4_1_11">enable simple creation and modification</a> of LPDRs.
 	</div>
+
+	<div id="ldpc-5_4_10" class="rule">5.4.10 LDPC servers MAY allow clients to suggest the URI for a resource
+		created through POST, using the HTTP <code>Slug</code> header as defined in [[!RFC5023]].  LDP adds
+		no new requirements to this usage, so its presence functions as a client hint to the server 
+		providing a desired string to be incorporated into the server's final choice of resource URI.
+	</div>
+	
 </section>
 
 <section>
@@ -1293,6 +1294,8 @@
 </p>
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130307/">Second Public Working Draft</a></em></blockquote>
 <ul>
+	<li>2013-05-21 - ISSUE-43 Slug in LDPC POSTs; 5.4.8, 5.4.10 (JA)</li>
+	<li>2013-05-21 - ISSUE-65 Remove firstPage in favor of Link rel=first, mostly hits 5.3.3/5.3.4 (JA)</li>
 	<li>2013-05-17 - ISSUE-13 Updated 5.2.3 to say any resource can be in a LDPC and inserted 5.5.3 on rejecting member data on PUT to LDPC (SS)</li>
 	<li>2013-05-17 - Tweaks to Terminology section for LDPR and LDPC (SS)</li>
 	<li>2013-05-17 - ISSUE-9 Moved section 4.1.7 out of spec to the <a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Servers_should_serve_up_canonical_URLs">deployment guide</a> (SS)</li>