Minor edits for ISSUE-22,23 to be more inline with HTTP1.1
authorsspeiche
Sat, 03 Nov 2012 05:16:21 -0400
changeset 18 b6b72bc4c3cf
parent 17 ab4d063b3fa8
child 19 52d63fdf6ae8
Minor edits for ISSUE-22,23 to be more inline with HTTP1.1
ldp.html
--- a/ldp.html	Sat Nov 03 01:18:58 2012 -0400
+++ b/ldp.html	Sat Nov 03 05:16:21 2012 -0400
@@ -1163,12 +1163,12 @@
 		words, clients should not expect any representation in the response
 		entity body on a 201 (Created) response.
 	</div>
-	<div id="ldpc-5_4_6" class="rule">5.4.6 For LDPCs, servers MUST accept a request entity body with a content
-		type of <code>text/turtle</code> [[!TURTLE]].
+	<div id="ldpc-5_4_6" class="rule">5.4.6 For LDPCs, 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 For LDPCs, LDPR servers MAY accept a request with an entity body
-		representations as indicated by request header <code>Content-Type</code> when present or derived from the 
-		entity body [[!HTTP11]].
+	<div id="ldpc-5_4_7" class="rule">5.4.7 For LDPCs, LDPR servers SHOULD accept a request with an entity body
+		representations as indicated by request header <code>Content-Type</code> when present, otherwise it MAY be
+		derived by inspecting the entity body contents [[!HTTP11]].
 	</div>
 	<div id="ldpc-5_4_8" class="rule">5.4.8 For RDF representations, LDPC servers MUST interpret the null relative
 		URI for the subject of triples in the LDPR representation in the