ldp.html
changeset 384 adfc713130ec
parent 374 eeff2a51723d
child 385 9686ab858357
--- a/ldp.html	Thu Oct 17 10:14:44 2013 +0100
+++ b/ldp.html	Mon Oct 21 09:52:06 2013 -0400
@@ -52,7 +52,7 @@
           // subtitle   :  "an excellent document",
 
           // if you wish the publication date to be other than today, set this
-          publishDate:  "2013-08-19",
+          publishDate:  "",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -717,8 +717,9 @@
 		- same subject, predicate and object.
 	</p>
 	<p><a title="LDP server">LDP servers</a> may respond to requests for a
-		resource by redirecting the client to the first page resource –
-		using a 303 “See Other” redirect to the actual URL for the page
+		resource by returning the first page resource –
+		using a <a href="#status-code-related-content"><code>209 Related Content</code></a> response
+		with a <code>Location</code> header containing the URL for the page
 		resource.  Alternatively, clients may introspect the resource for a paged representation 
 		and use it preferentially when available.</p>
 	<p>
@@ -826,8 +827,8 @@
 		additional details.
 	</div>
 	<div id="ldpr-pagingGET-3" class="rule">4.10.2.3 <a title="LDP server">LDP servers</a> that initiate paging SHOULD respond to requests for a LDPR
-		by redirecting the client to the first page resource using a <code>303 See
-		Other</code> response with an HTTP <code>Location</code> header providing the first page resource URL.
+		by returning the first page resource using a <code>209 Related Content</code> response 
+		with an HTTP <code>Location</code> header providing the first page resource URL.
 	</div>
 	<div id="ldpr-pagingGET-4" class="rule">4.10.2.4 <a title="LDP server">LDP servers</a> that support paging MUST include a representation for the page resource.
 	</div>
@@ -1701,6 +1702,79 @@
 </section>
 </section> <!-- Header defns -->
     
+<section>
+<h1>HTTP Status Code Definitions</h1>
+     
+<section id="status-code-related-content">
+<h2>209 Related Content</h2>
+
+	<div class="atrisk"><p class="atrisktext">Feature At Risk</p>
+		<p>The LDP Working Group proposes incorporation of the features described in this section.</p>
+		<ul>
+		<li>The addition of <a>Accept-Post</a> in this specification is pending 
+		advancement of an <a href="https://datatracker.ietf.org/doc/draft-wilde-related-content/">IETF draft</a>
+		that would fully include it, patterned after the codes defined by [[RFC6585]].  Once LDP is in
+		Candidate Recommendation status, the LDP WG will make an assessment based on the status at IETF
+		working with the W3C Director.</li>
+		</ul>
+	</div>
+		
+	<p>The <code>209 Related Content</code> status code indicates that the origin server 
+		is supplying the representation of a different resource than the target resource,
+		and the origin server believes that the supplied representation 
+		is likely to satisfy the user agent's original request.
+		The resource whose representation is supplied is descriptive of the target resource, in
+		the same way that the <code>Location</code> header in a <code>303 See Other</code>
+		response is descriptive of the target resource.
+	</p>
+	<p><code>209 Related Content</code> is intended to be used in situations where 
+		<code>303 See Other</code> could have been used and would most likely result in a
+		user agent retrieving the other resource, but saves the user agent from
+		the latency penalty of having to perform a separate retrieval request.
+	</p>
+   
+	<p>	LDP uses <code>209 Related Content</code> to provide clients with the 
+		<a href="#ldpr-Paging">first page of a large resource</a>, but it can also be used in
+		other common situations.  Linked Data clients could benefit by avoiding the latency
+		of additional requests when the target resource is a concept resource (one without any
+		representation capable of transmission over HTTP), and general HTTP clients would
+		benefit in many of the more general cases where <code>303 See Other</code> responses
+		are currently used.
+	</p>
+   
+	<div id="status-code-related-content-1" class="rule">7.1.1 A <code>209</code> response to a
+		<code>GET</code> request MUST contain a <code>Location</code> header with the same
+		<code>Location</code> field value as a <code>303 See Other</code> response would use [[!HTTP11]].
+	</div>
+
+	<div id="status-code-related-content-2" class="rule">7.1.2 A <code>209</code> response to a
+		<code>GET</code> request MUST contain a representation of the resource identified
+		by the response's <code>Location</code> header.
+	</div>
+
+	<div id="status-code-related-content-iana" class="rule">7.1.3 IANA Considerations</div>
+	<div>
+	<blockquote>
+	<p>
+	The <code>209 Related Content</code> must be added to the permanent status code registry 
+	maintained at <a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>
+	(see [[!HTTPBIS]]).
+	</p>
+	<p>
+	Value:  209
+	</p>
+	<p>
+	Description:  Related Content
+	</p>
+	<p>
+	Reference:  this specification
+	</p>
+	</blockquote>
+	</div>
+
+</section>
+</section> <!-- status code defns -->
+    
 <section id="ldpclient">
 <h1>Linked Data Platform Clients</h1>
 <div class="ldp-issue-open">
@@ -1864,6 +1938,7 @@
 
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote>  -->
 <ul>
+    <li>2013-10-21 - Mock up status code 209 Related Content (JA)</li>
     <li>2013-10-01 - Mock up new section for rules declared to be non-normative restatements of info from other specs (JA)</li>
     <li>2013-10-01 - Revising terminology - membership triples and friends (JA)</li>
     <li>2013-10-01 - Revising introduction (JA)</li>