Paging HTML validation fixes
authorSteve Speicher <sspeiche@gmail.com>
Wed, 27 Aug 2014 13:53:34 -0400
changeset 786 218a3a675085
parent 785 e8762f0e7cee
child 787 b7710971002f
Paging HTML validation fixes
TR/WD-ldp-paging-20140828/Overview.html
ldp-paging.html
--- a/TR/WD-ldp-paging-20140828/Overview.html	Wed Aug 27 13:39:58 2014 -0400
+++ b/TR/WD-ldp-paging-20140828/Overview.html	Wed Aug 27 13:53:34 2014 -0400
@@ -244,7 +244,7 @@
   </p>
   <h1 class="title p-name" id="title" property="dcterms:title">Linked Data Platform Paging 1.0</h1>
   
-  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-08-27T21:34:59.000Z" id="w3c-last-call-working-draft-27-august-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Last Call Working Draft <time class="dt-published" datetime="2014-08-27">27 August 2014</time></h2>
+  <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2014-08-27T21:52:29.000Z" id="w3c-last-call-working-draft-27-august-2014"><abbr title="World Wide Web Consortium">W3C</abbr> Last Call Working Draft <time class="dt-published" datetime="2014-08-27">27 August 2014</time></h2>
   <dl>
     
       <dt>This version:</dt>
@@ -262,7 +262,7 @@
     
     
       <dt>Previous version:</dt>
-      <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2013/WD-ldp-paging-20130730/">http://www.w3.org/TR/2013/WD-ldp-paging-20130730/</a></dd>
+      <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2013/WD-ldp-20130730/">http://www.w3.org/TR/2013/WD-ldp-20130730/</a></dd>
     
     
     <dt>Editors:</dt>
@@ -1492,7 +1492,7 @@
 			process <code>2NN Contents of Related</code> responses [<cite><a class="bibref" href="#bib-2NN">2NN</a></cite>].
 			<a title="LDP Paging server" href="#dfn-ldp-paging-server" class="internalDFN">LDP Paging servers</a> initiating paging <em class="rfc2119" title="SHOULD">SHOULD</em> respond
 			to successful <code>GET</code> requests with any <a title="Paged resource" href="#dfn-paged-resource" class="internalDFN">paged resource</a> 
-			as the <code>Request-URI</code> in one of the following ways:
+			as the <code>Request-URI</code> in one of the following ways:</h4>
 			<ul>
 			<li>
 				If the client supports <code>2NN</code> responses, respond
@@ -1520,6 +1520,7 @@
 				choose another status code appropriate to the specific situation.
 			</li>
 			</ul>
+			
 			<blockquote>
 				<em>Non-normative note:</em>
 				<a title="LDP Paging server" href="#dfn-ldp-paging-server" class="internalDFN">LDP Paging servers</a> could choose to make any resource
@@ -1534,7 +1535,7 @@
 				but some existing HTTP clients are known to treat <code>303 See Other</code> redirects as if they were 
 				equivalent to the original request-URI, despite this being explicitly disclaimed in [<cite><a class="bibref" href="#bib-RFC7231">RFC7231</a></cite>].
 			</blockquote>
-	</h4></section>
+	</section>
 
 	<section id="ldpr-guarantee-show-unchanged" typeof="bibo:Chapter" resource="#ldpr-guarantee-show-unchanged" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldpr-guarantee-show-unchanged"><span class="secno">6.2.7 </span>
 		<a title="LDP Paging server" href="#dfn-ldp-paging-server" class="internalDFN">LDP Paging servers</a> <em class="rfc2119" title="MUST">MUST</em> 
@@ -2136,7 +2137,7 @@
 		a triple
 		whose subject is the sort criterion identifier, 
 		whose predicate is <code>ldp:pageSortOrder</code> 
-		and whose object describes the order used.
+		and whose object describes the order used.</h4>
 		<blockquote>
 		<p>
 		LDP defines two values,
@@ -2145,7 +2146,7 @@
 		assigns no meaning to them and interoperability will be limited.
 		</p>
 		</blockquote>
-	 </h4></section><!-- Was 5.3.4 / #ldpc-5_3_4 -->
+	</section><!-- Was 5.3.4 / #ldpc-5_3_4 -->
 	
 	<section id="ldpc-sortcollation" typeof="bibo:Chapter" resource="#ldpc-sortcollation" rel="bibo:Chapter"><h4 class="normal" aria-level="3" role="heading" id="h4_ldpc-sortcollation"><span class="secno">7.3.6 </span>
 		<a title="LDP Paging server" href="#dfn-ldp-paging-server" class="internalDFN">LDP Paging servers</a> <a href="#ldpc-sort-criteria-consistent">communicating order</a> <em class="rfc2119" title="MAY">MAY</em> 
@@ -2156,7 +2157,7 @@
 		whose predicate is <code>ldp:pageSortCollation</code> 
 		and whose object identifies the collation used.
 		The <code>ldp:pageSortCollation</code> triple <em class="rfc2119" title="MUST">MUST</em> be omitted for comparisons
-		involving <a title="page-ordering values" href="#dfn-page-ordering-values" class="internalDFN">page-ordering values</a> for which [<cite><a class="bibref" href="#bib-sparql11-query">sparql11-query</a></cite>] does not use collations.
+		involving <a title="page-ordering values" href="#dfn-page-ordering-values" class="internalDFN">page-ordering values</a> for which [<cite><a class="bibref" href="#bib-sparql11-query">sparql11-query</a></cite>] does not use collations.</h4>
 		<blockquote>
 		<p>
 		LDP defines no values for use
@@ -2180,7 +2181,7 @@
 		specified collation.
 		</p>
 		</blockquote>
-	</h4></section><!-- Was 5.3.5 / #ldpc-5_3_5 -->
+	</section><!-- Was 5.3.5 / #ldpc-5_3_5 -->
 
 </section> <!-- h2 -->
 
@@ -2258,7 +2259,7 @@
 	</div>
 
 </section>
-</section> <!-- status code defns -->
+</section>  -->
 
 
 <section class="informative" id="security" typeof="bibo:Chapter" resource="#security" rel="bibo:Chapter">
@@ -2406,7 +2407,7 @@
 </dd><dt id="bib-sparql11-query">[sparql11-query]</dt><dd rel="dcterms:requires">Steven Harris; Andy Seaborne. <a href="http://www.w3.org/TR/sparql11-query/"><cite>SPARQL 1.1 Query Language</cite></a>. 21 March 2013. W3C Recommendation. URL: <a href="http://www.w3.org/TR/sparql11-query/">http://www.w3.org/TR/sparql11-query/</a>
 </dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:Chapter"><h3 aria-level="2" role="heading" id="h3_informative-references"><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-LDP-UCR">[LDP-UCR]</dt><dd rel="dcterms:references">Steve Battle; Steve Speicher. <a href="http://www.w3.org/TR/ldp-ucr/"><cite>Linked Data Platform Use Cases and Requirements</cite></a>. 13 March 2014. W3C Note. URL: <a href="http://www.w3.org/TR/ldp-ucr/">http://www.w3.org/TR/ldp-ucr/</a>
 </dd><dt id="bib-NON-REPEATABLE-READS">[NON-REPEATABLE-READS]</dt><dd rel="dcterms:references">Various. <a href="http://en.wikipedia.org/wiki/Isolation_(database_systems)#Non-repeatable_reads"><cite>Wikipedia: Isolation (database systems)</cite></a>. N/A. URL: <a href="http://en.wikipedia.org/wiki/Isolation_(database_systems)#Non-repeatable_reads">http://en.wikipedia.org/wiki/Isolation_(database_systems)#Non-repeatable_reads</a>
-</dd><dt id="bib-READ-COMMITTED">[READ-COMMITTED]</dt><dd rel="dcterms:references">Various. <a href="http://en.wikipedia.org/wiki/Isolation_%28database_systems%29#Read_committed"><cite>Wikipedia: Isolation (database systems)</cite></a>. N/A. URL: <a href="http://en.wikipedia.org/wiki/Isolation_%28database_systems%29#Read_committed">http://en.wikipedia.org/wiki/Isolation_%28database_systems%29#Read_committed</a>
+</dd><dt id="bib-READ-COMMITTED">[READ-COMMITTED]</dt><dd rel="dcterms:references">Various. <a href="http://en.wikipedia.org/wiki/Isolation_(database_systems)#Read_committed"><cite>Wikipedia: Isolation (database systems)</cite></a>. N/A. URL: <a href="http://en.wikipedia.org/wiki/Isolation_(database_systems)#Read_committed">http://en.wikipedia.org/wiki/Isolation_(database_systems)#Read_committed</a>
 </dd><dt id="bib-RFC5005">[RFC5005]</dt><dd rel="dcterms:references">M. Nottingham. <a href="http://www.ietf.org/rfc/rfc5005.txt"><cite>Feed Paging and Archiving</cite></a>. September 2007. Proposed Standard. URL: <a href="http://www.ietf.org/rfc/rfc5005.txt">http://www.ietf.org/rfc/rfc5005.txt</a>
 </dd><dt id="bib-turtle">[turtle]</dt><dd rel="dcterms:references">Eric Prud'hommeaux; Gavin Carothers. <a href="http://www.w3.org/TR/turtle/"><cite>RDF 1.1 Turtle</cite></a>. 25 February 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/turtle/">http://www.w3.org/TR/turtle/</a>
 </dd></dl></section></section></body></html>
\ No newline at end of file
--- a/ldp-paging.html	Wed Aug 27 13:39:58 2014 -0400
+++ b/ldp-paging.html	Wed Aug 27 13:53:34 2014 -0400
@@ -105,7 +105,7 @@
 			localBiblio:  {
 				"READ-COMMITTED": {
 					title:    "Wikipedia: Isolation (database systems)"
-				,   href:     "http://en.wikipedia.org/wiki/Isolation_%28database_systems%29#Read_committed"
+				,   href:     "http://en.wikipedia.org/wiki/Isolation_(database_systems)#Read_committed"
 				,   authors:  [
 						"Various"
 					]
@@ -1360,7 +1360,7 @@
 			process <code>2NN Contents of Related</code> responses [[!2NN]].
 			<a title="LDP Paging server">LDP Paging servers</a> initiating paging SHOULD respond
 			to successful <code>GET</code> requests with any <a title="Paged resource">paged resource</a> 
-			as the <code>Request-URI</code> in one of the following ways:
+			as the <code>Request-URI</code> in one of the following ways:</h2>
 			<ul>
 			<li>
 				If the client supports <code>2NN</code> responses, respond
@@ -1388,6 +1388,7 @@
 				choose another status code appropriate to the specific situation.
 			</li>
 			</ul>
+			
 			<blockquote>
 				<em>Non-normative note:</em>
 				<a title="LDP Paging server">LDP Paging servers</a> could choose to make any resource
@@ -1402,7 +1403,7 @@
 				but some existing HTTP clients are known to treat <code>303 See Other</code> redirects as if they were 
 				equivalent to the original request-URI, despite this being explicitly disclaimed in [[RFC7231]].
 			</blockquote>
-	</h2></section>
+	</section>
 
 	<section id="ldpr-guarantee-show-unchanged"><h2 class="normal">
 		<a title="LDP Paging server">LDP Paging servers</a> MUST 
@@ -2011,7 +2012,7 @@
 		a triple
 		whose subject is the sort criterion identifier, 
 		whose predicate is <code>ldp:pageSortOrder</code> 
-		and whose object describes the order used.
+		and whose object describes the order used.</h2>
 		<blockquote>
 		<p>
 		LDP defines two values,
@@ -2020,7 +2021,7 @@
 		assigns no meaning to them and interoperability will be limited.
 		</p>
 		</blockquote>
-	 </h2></section><!-- Was 5.3.4 / #ldpc-5_3_4 -->
+	</section><!-- Was 5.3.4 / #ldpc-5_3_4 -->
 	
 	<section id="ldpc-sortcollation"><h2 class="normal">
 		<a title="LDP Paging server">LDP Paging servers</a> <a href="#ldpc-sort-criteria-consistent">communicating order</a> MAY 
@@ -2031,7 +2032,7 @@
 		whose predicate is <code>ldp:pageSortCollation</code> 
 		and whose object identifies the collation used.
 		The <code>ldp:pageSortCollation</code> triple MUST be omitted for comparisons
-		involving <a title="page-ordering values">page-ordering values</a> for which [[!sparql11-query]] does not use collations.
+		involving <a title="page-ordering values">page-ordering values</a> for which [[!sparql11-query]] does not use collations.</h2>
 		<blockquote>
 		<p>
 		LDP defines no values for use
@@ -2055,7 +2056,7 @@
 		specified collation.
 		</p>
 		</blockquote>
-	</h2></section><!-- Was 5.3.5 / #ldpc-5_3_5 -->
+	</section><!-- Was 5.3.5 / #ldpc-5_3_5 -->
 
 </section> <!-- h2 -->
 
@@ -2133,7 +2134,7 @@
 	</div>
 
 </section>
-</section> <!-- status code defns -->
+</section>  -->
 
 
 <section class='informative' id='security'>