ldp.html
changeset 208 0cd38b1b5d41
parent 207 efd0bea81a54
child 210 c2479399b854
--- a/ldp.html	Mon Jul 15 12:48:22 2013 -0400
+++ b/ldp.html	Mon Jul 15 13:06:38 2013 -0400
@@ -178,24 +178,19 @@
 	<p>This specification discusses standard HTTP and RDF techniques and best practices that you 
 	should use, and anti-patterns you should avoid, when constructing clients and servers that 
 	read and write Linked Data.</p> 
-		<p>A special type of Linked Data Resource is a Container.  Containers are very useful 
-		in building application models.  For example, universities offer a collection of classes 
-		and have a collection of faculty members.  Each faculty member teaches a collection of courses, etc.  
-		This specification discusses how to work with Containers.  Resources can be added to containers in 
-		several ways. As a special case, members can both be created and added to a container by overloading 
-		the POST operation.  See <a href="#ldpr-5_4">5.4</a>.
-	</p>
+	<p>A special type of Linked Data Platform Resource is a Container.  Containers are very useful 
+	in building application models.  For example, universities offer a collection of classes 
+	and have a collection of faculty members.  Each faculty member teaches a collection of courses, etc.  
+	This specification discusses how to work with containers.  Resources can be added to containers in 
+	several ways. As a special case, members can both be created and added to a container by overloading 
+	the POST operation.  See <a href="#ldpc-HTTP_POST" class="sectionRef"></a>.</p>
 	<p>Another contribution of this specification is how to deal with large amounts of data.  
 	Depending on the server’s capabilities, a GET request on a Linked Data Platform Resource 
-	returns a set of pages and uses a convention to access any single page. See <a href="#ldpr-4_9">4.9</a>. </p>
+	returns a set of pages and uses a convention to access any subsequent page. See <a href="#ldpr-Paging" class="sectionRef"></a>. </p>
 	<p>The intention of this document is to enable additional rules and layered groupings of rules as 
 	additional specifications.  The scope is intentionally narrow to provide a set of key rules for 
 	reading and writing Linked Data that most, if not all, other specifications will depend upon and 
-	implementations will support.
-	</p>
-	
-	</div>
-	
+	implementations will support.</p>
 </section>
 	
 <section>