ldp.html
changeset 116 48fabccf847c
parent 115 c8f6c689d373
child 120 edf269bcce8a
--- a/ldp.html	Tue May 21 12:00:16 2013 -0400
+++ b/ldp.html	Tue May 21 15:46:16 2013 -0400
@@ -1023,6 +1023,15 @@
 	<div id="ldpc-5_2_8" class="rule">5.2.8 LDPCs SHOULD NOT use RDF container types <code>rdf:Bag</code>,
 		<code>rdf:Seq</code> or <code>rdf:List</code>.
 	</div>
+
+	<div id="ldpc-5_2_9" class="rule">5.2.9 LDPC servers SHOULD NOT re-use URIs, 
+		regardless of the mechanism by which members are created (POST, PUT, etc.).
+		Certain specific cases exist where a LDPC server MAY delete a resource and then later re-use the
+		URI when it identifies the same resource, but only when consistent with Web architecture [[WEBARCH]].
+		While it is difficult to provide absolute implementation guarantees of non-reuse in all failure
+		scenarios, re-using URIs creates ambiguities for clients that are best avoided.
+	</div>
+	
 </section>
 
 <section>	
@@ -1201,6 +1210,11 @@
 		providing a desired string to be incorporated into the server's final choice of resource URI.
 	</div>
 	
+	<div id="ldpc-5_4_11" class="rule">5.4.11 LDPC servers that allow member creation via POST 
+		SHOULD NOT re-use URIs, per the<a href="#ldpc-5_2_9">
+		general requirements on LDPCs<a>.
+	</div>
+	
 </section>
 
 <section>
@@ -1229,6 +1243,12 @@
 		See section <a href="#ldpc-member_data">5.1.1 Container
 		Member Information</a> for additional details.
 	</div>
+	
+	<div id="ldpc-5_5_4" class="rule">5.5.4 LDPC servers that allow member creation via PUT 
+		SHOULD NOT re-use URIs, per the <a href="#ldpc-5_2_9">
+		general requirements on LDPCs<a>.
+	</div>
+	
 </section>
 
 <section>
@@ -1294,6 +1314,7 @@
 </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-35 Re-use of URIs on create; 5.2.9, 5.4.11, 5.5.4 (JA)</li>
 	<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>