ldp.html
changeset 204 04f24555e6aa
parent 202 8d42c2346d50
child 205 204759ef91b8
--- a/ldp.html	Mon Jul 15 10:43:47 2013 -0400
+++ b/ldp.html	Mon Jul 15 11:51:56 2013 -0400
@@ -176,33 +176,25 @@
 		information, using the standards (RDF*, <abbr title="SPARQL Protocol and RDF Query Language">SPARQL</abbr>)</p>
 	<p>4. Include links to other URIs. so that they can
 		discover more things</p>
-	<p>The best practices and
-		anti-patterns covered in this document are:</p>
-	<ul>
-		<li><p>
-			<em>Resources</em> - a summary of the
-				HTTP and RDF standard 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>
-		</li>
-		<li><p>
-			<em>Containers</em> - defines resources
-				that allow new resources to be created using HTTP POST and existing
-				resources to be found using HTTP GET. 
-			</p>
-		</li>
-	</ul>
-	<p>Additionally, it is the intention
-	of this document to enable additional rules and layered groupings of
-	rules, such 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>   
+	<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>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>
+	<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 class="ldp-issue-open">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/37">ISSUE-37</a></div>
-	Additional introductory text on the LDP data and interaction model <em>-- awaiting contribution</em>
 	</div>
 	
 </section>