ldp.html
changeset 516 b46f235b5fcc
parent 515 9f5b3854a5bb
child 517 5971b0e54055
--- a/ldp.html	Sat Mar 01 15:32:14 2014 -0500
+++ b/ldp.html	Mon Mar 03 08:11:56 2014 -0500
@@ -130,6 +130,15 @@
 				,   status:   "Editor's Working Draft"
 				,   publisher:  "W3C"
 				},
+				"Prefer": {
+					title:    "Prefer"
+				,   href:     "http://tools.ietf.org/html/draft-snell-http-prefer-18"
+				,   authors:  [
+						"J. Snell"
+					]
+				,   status:   "Internet Draft"
+				,   publisher:  "IETF"
+				},
 			},
       };
     </script>
@@ -759,7 +768,7 @@
 <section id="ldprs-general">
 <h2>General</h2>
 
-	<section id="ldprs-are-ldpr"><h2 class="normal">Each <a title="Linked Data Platform RDF Resource">LDP RDF Source</a> MUST also be 
+	<section id="ldprs-are-ldpr"><h2 class="normal">Each <a title="Linked Data Platform RDF Source">LDP RDF Source</a> MUST also be 
 		a conforming <a title="Linked Data Platform Resource">LDP Resource</a> in <a href="#ldpr-resource" class="sectionRef"></a> along the
 		following restrictions in this section. <a title="">LDP client</a>s MAY infer the following triple:
 		whose subject is <code>ldp:RDFSource</code>, 
@@ -1268,8 +1277,8 @@
 
 	<section id="ldpc-post-createdmbr-contains"><h2 class="normal">
 		When a successful HTTP <code>POST</code> request to an LDPC results in the creation of an LDPR, a 
-		<a title="Containment triple">containmemt triple</a> MUST be added to the state of LDPC.  The
-		<a title="Containment triple">containmemt triple</a> whose subject is the LDPC URI, 
+		<a title="Containment triples">containmemt triple</a> MUST be added to the state of LDPC.  The
+		<a title="Containment triples">containmemt triple</a> whose subject is the LDPC URI, 
 		whose predicate is <code>ldp:contains</code> and whose object is the URI for the newly created document (LDPR).
 		The newly created LDPR appears as a contained resource of the LDPC until the
 		newly created document is deleted or removed by other methods. Other triples may be added as well.
@@ -2071,7 +2080,7 @@
 	the header would still be required for the client to know that the <code>303</code> response entity
 	is a representation of the resource identified by the <code>Location</code> URI 
 	instead of a short hypertext note (one with a hyperlink to
-	the same URI reference provided in the <code>Location</code> header field [[HTTPbis]]).
+	the same URI reference provided in the <code>Location</code> header field [[HTTPBIS-SEMANTICS]]).
 	</p>
 	
 	<pre class="example">