ISSUE-39 Moved informative text from 5.4.5 into 5.4.1, shifted subsections .6-.10
authorsspeiche
Mon, 15 Apr 2013 08:47:09 -0400
changeset 94 2292ad834245
parent 93 598be81efe5f
child 95 68405d7a9fd6
ISSUE-39 Moved informative text from 5.4.5 into 5.4.1, shifted subsections .6-.10
ldp.html
--- a/ldp.html	Mon Apr 15 08:29:48 2013 -0400
+++ b/ldp.html	Mon Apr 15 08:47:09 2013 -0400
@@ -1111,10 +1111,12 @@
 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
 		
 	<div id="ldpc-5_4_1" class="rule">5.4.1 LDPC clients SHOULD create member resources by submitting a representation as
-		the entity body of the HTTP POST to a known LDPC. LDPC servers MUST
+		the entity body of the HTTP POST to a known LDPC. If the resource was created successfully, LDPC servers MUST
 		respond with status code 201 (Created) and the <code>Location</code>
-		header set to the new resource’s URL.
+		header set to the new resource’s URL. Clients shall not expect any representation in the response
+		entity body on a 201 (Created) response.
 	</div>
+
 	<div id="ldpc-5_4_2" class="rule">5.4.2 After a successful HTTP POST request to a LDPC, the new resource MUST
 		appear as a member of the LDPC until the new resource is deleted or
 		removed by other methods. An LDPC MAY also contain resources that were
@@ -1134,25 +1136,15 @@
 		RDF representation in the request entity body.  The LDPR could also be a LDPC, therefore servers may
 		allow the creations of LDPCs within a LDPC. 
 	</div>
-	<div id="ldpc-5_4_5" class="rule">5.4.5 LDPC servers SHOULD NOT include the representation of the created
-		resource in the entity body of a 201 (Created) response. In other
-		words, clients should not expect any representation in the response
-		entity body on a 201 (Created) response.
-	</div>
 	
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/39">ISSUE-39</a></div>
-	HTTP status codes used for creation
-	</div>
-	
-	<div id="ldpc-5_4_6" class="rule">5.4.6 LDPC servers MUST accept a request entity body with a request header
+	<div id="ldpc-5_4_5" class="rule">5.4.5 LDPC servers MUST accept a request entity body with a request header
 	    of <code>Content-Type</code> with value of <code>text/turtle</code> [[!TURTLE]].
 	</div>
-	<div id="ldpc-5_4_7" class="rule">5.4.7 LDPC servers SHOULD use the <code>Content-Type</code> request header 
+	<div id="ldpc-5_4_6" class="rule">5.4.6 LDPC servers SHOULD use the <code>Content-Type</code> request header 
 		to determine the representation format when the request has an entity body.  When the header is absent, 
 		LDPC servers MAY infer the content type by inspecting the entity body contents [[!HTTP11]].
 	</div>
-	<div id="ldpc-5_4_8" class="rule">5.4.8 In RDF representations, LDPC servers MUST interpret the null relative
+	<div id="ldpc-5_4_7" class="rule">5.4.7 In RDF representations, LDPC servers MUST interpret the null relative
 		URI for the subject of triples in the LDPR representation in the
 		request entity body as referring to the entity in the request body.
 		Commonly, that entity is the model for the “to be created” LDPR, so
@@ -1166,7 +1158,7 @@
 	</div>	
 	</div>
 	
-	<div id="ldpc-5_4_9" class="rule">5.4.9 LDPC servers SHOULD assign the subject URI for the resource to be
+	<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.
 	</div>
 	
@@ -1176,7 +1168,7 @@
 	</div>
 	
 	
-	<div id="ldpc-5_4_10" class="rule">5.4.10 LDPC servers SHOULD allow clients to create new resources without
+	<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_13">enable simple creation and modification</a> of LPDRs.
@@ -1273,9 +1265,10 @@
 </p>
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130307/">Second Public Working Draft</a></em></blockquote>
 <ul>
+	<li>2013-04-15 - ISSUE-39 Moved informative text from 5.4.5 into 5.4.1, shifted subsections .6-.10 (SS)</li>
 	<li>2013-04-15 - Expanded on wording for 4.3 to be more consistent (SS)</li>
 	<li>2013-04-08 - Fixed two old references to BPR (SS)</li>
-	<li>2013-03-17 - Inserted examples 2&3, a more complete NetWorth resource (SS)</li>
+	<li>2013-03-17 - Inserted examples 2&amp;3, a more complete NetWorth resource (SS)</li>
 	<li>2013-03-15 - Update LDPC glossary term based on Cody's feedback (SS)</li>
 	<li>2013-03-15 - Additional fix in 5.2.2 for ISSUE-34 (SS)</li>
 	<li>2013-03-15 - Remove reference to closed issues that don't require edits: ISSUE-27 & ISSUE-45 (SS)</li>