ldp.html
changeset 527 b86124412c7a
parent 525 238e04f1e4f1
child 539 8ff6773d4daa
--- a/ldp.html	Tue Mar 04 13:14:38 2014 -0500
+++ b/ldp.html	Tue Mar 04 13:40:45 2014 -0500
@@ -826,15 +826,16 @@
 		including LDP-defined hints.
 	</h2></section>
 	
-	<section id="ldpr-cli-paging"><h2 class="normal">
 	<div class="atrisk" id="atrisk-paging"><p class="atrisktext">Feature At Risk</p>
 	<p>The LDP Working Group proposes incorporation of the following clause to make LDP clients paging aware:</p>
+	<section id="ldpr-cli-paging"><h2 class="normal">
 		<a title="LDP client">LDP clients</a> SHOULD 
 		be capable of processing successful HTTP <code>GET</code> responses formed by an LDP server
 		that independently initiated paging, returning a page of representation instead of full resource
 		representation [[!LDP-PAGING]].
-	</div></h2>
+	</h2>
 	</section> 
+	</div>
 	
 </section> <!-- ldprs-general -->
 
@@ -1117,7 +1118,7 @@
 	<a title="containment">containment</a> triples.  For details on the normative behavior, see appropriate sections
 	below.
 	</p>
-	<table border="1" id="ldpc-mbrcntdiff">
+	<table style="border: 1px solid gray" id="ldpc-mbrcntdiff">
 		<thead><tr><th rowspan="2">Completed Request</th><th colspan="2">Effects</th></tr>
 		       <tr class="oddrow"><th>Membership</th><th>Containment</th></tr></thead>
 		<tr><td>LDPR created in LDP-BC</td><td>New triple: (LDPC, ldp:contains, LDPR)</td><td>Same</td></tr>
@@ -1307,8 +1308,8 @@
 	requests to the newly created resource's URI as if it is an LDPC.
 	</li>
 	<li>This specification does not constrain the server's behavior in other cases.</li>
+	</ul>
 	<p>Note: A consequence of this is that LDPCs can be used to create LDPCs, if the server supports doing so.</p>
-	</ul>
 	</section>
 	
 	<section id="ldpc-post-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST accept a request entity body with a request header
@@ -1926,7 +1927,7 @@
 	<section id="prefer-uris"><h2 class="normal">
 		This specification defines the following URIs for clients to use with <code>include</code>
 		and <code>omit</code> parameters.  It assigns no meaning to other URIs, although
-		other specifications MAY do so.
+		other specifications MAY do so.</h2>
 		<table class="indented">
 		<tr>
 		<td> <a title="Containment triples">Containment triples </a></td>
@@ -1950,8 +1951,6 @@
 		could be defined.
 		</p>
 		</blockquote>
-		
-		</h2>
 	</section>
 
 </section> <!-- Prefer specification -->