Moved 4.7.2 (from HEAD) to 4.3.2 (GET), shifted rest of GET section by one
authorsspeiche
Wed, 24 Jul 2013 08:54:11 -0400
changeset 228 ec118c66c122
parent 227 1bb410ec95dd
child 229 8ddd81e6113c
Moved 4.7.2 (from HEAD) to 4.3.2 (GET), shifted rest of GET section by one
ldp.html
--- a/ldp.html	Wed Jul 24 08:44:34 2013 -0400
+++ b/ldp.html	Wed Jul 24 08:54:11 2013 -0400
@@ -454,18 +454,21 @@
 <h2 id="ldpr-HTTP_GET">HTTP GET</h2>
 	<div id="ldpr-4_3_1" class="rule">4.3.1 LDPR servers MUST support the HTTP <code>GET</code> Method for LDPRs.
 	</div>
-	<div id="ldpr-4_3_2" class="rule">4.3.2 LDPR servers SHOULD provide a <code>text/turtle</code>
+	<div id="ldpr-4_3_2" class="rule">4.3.2 LDPR servers MUST support the HTTP response headers defined in 
+		<a href="#ldpr-HTTP_OPTIONS" class="sectionRef"></a>.
+	</div>
+	<div id="ldpr-4_3_3" class="rule">4.3.3 LDPR servers SHOULD provide a <code>text/turtle</code>
 		representation of the requested LDPR [[!TURTLE]].
 	</div>
-	<div id="ldpr-4_3_3" class="rule">4.3.3 LDPR servers MAY provide 
+	<div id="ldpr-4_3_4" class="rule">4.3.4 LDPR servers MAY provide 
 		representations of the requested LDPR beyond those
 		necessary to conform to this specification, using standard HTTP content negotiation. 
 		If the client does not indicate a preference, <code>text/turtle</code> SHOULD be returned.
 	</div>
-	<div id="ldpr-4_3_4" class="rule">4.3.4 In the absence of special knowledge of the application or domain, LDPR
+	<div id="ldpr-4_3_5" class="rule">4.3.5 In the absence of special knowledge of the application or domain, LDPR
 		clients MUST assume that any LDPR can have multiple values for <code>rdf:type</code>.
 	</div>
-	<div id="ldpr-4_3_5" class="rule">4.3.5 In the absence of special knowledge of the application or domain, LDPR
+	<div id="ldpr-4_3_6" class="rule">4.3.6 In the absence of special knowledge of the application or domain, LDPR
 		clients MUST assume that the <code>rdf:type</code> values
 		of a given LDPR can change over time.
 	</div>
@@ -562,8 +565,6 @@
 		<code>HEAD</code> responses include the same headers as <code>GET</code> responses.  
 		Thus, implementers should also carefully read <a href="#ldpr-HTTP_GET" class="sectionRef"></a>.</p>
 	<div id="ldpr-4_7_1" class="rule">4.7.1 LDPR servers MUST support the HTTP <code>HEAD</code> method.</div>
-	<div id="ldpr-4_7_2" class="rule">4.7.2 LDPR servers MUST support the HTTP response headers defined in <a href="#ldpr-HTTP_OPTIONS" class="sectionRef"></a>.
-	</div>
 </section>
 
 <section>
@@ -1796,6 +1797,7 @@
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
 -->
 <ul>
+	<li>2013-07-24 - Moved 4.7.2 (from HEAD) to 4.3.2 (GET), shifted rest of GET section by one (SS)</li>
 	<li>2013-07-24 - Moved 4.10.2.5->4.10.2.4.3,4.10.2.6->4.10.2.4.1,4.10.2.7->4.10.2.4.2 and added samples (SS)</li>
 	<li>2013-07-24 - Changed ldp:ascending->ldp:Ascending, ldp:descending->ldp:Descending, ldp:non-member-resource ->ldp:nonMemberResource (SS)</li>
 	<li>2013-07-24 - Added term <a title="Page resource"></a> (SS)</li>