ldp.html
changeset 863 59e549d8cdbb
parent 862 952456f33375
child 864 ea6049ed6590
--- a/ldp.html	Mon Oct 20 14:32:08 2014 -0400
+++ b/ldp.html	Mon Oct 20 16:18:56 2014 -0400
@@ -27,7 +27,7 @@
     <script class='remove'>
       var respecConfig = {
           // specification status (e.g. ED, WD, LC, NOTE, etc.). If in doubt use ED.
-          specStatus:           "WD",
+          specStatus:           "PR",
           
           // the specification's short name, as in http://www.w3.org/TR/short-name/
           shortName:            "ldp",
@@ -37,7 +37,7 @@
           // subtitle   :  "an excellent document",
 
           // if you wish the publication date to be other than today, set this
-          //publishDate:  "2014-09-16",
+          publishDate:  "2014-11-06",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -55,7 +55,8 @@
           edDraftURI:           "http://www.w3.org/2012/ldp/hg/ldp.html",
 
           // if this is a LCWD, uncomment and set the end of its review period
-          //lcEnd: "2014-10-07",
+          lcEnd: "2014-10-07",
+          prEnd: "2014-12-04",
           //crEnd: "2014-07-17",
           
           testSuiteURI: "https://dvcs.w3.org/hg/ldpwg/raw-file/tip/tests/ldp-testsuite.html",
@@ -242,13 +243,9 @@
 
  <section id='sotd'>
    <p>
-   	 This is the 3rd Last Call working draft where the Working Group has addressed all
-   	 raised issues and seeks to gather additional implementation feedback.  
-   	 The Working Group has decided to go from Candidate Recommendation to Last Call based on implementation feedback.
-   	 This feedback caused the Working Group to refine a conformance requirements for Turtle, JSON-LD and marking 
-   	 feature of Indirect Containers At Risk.
-   	 For changes since 
-   	 last publication, see <a href="#history" class="sectionRef"></a>. 
+   	 This is the Proposed Recommendation working draft where the Working Group has received community feedback,
+   	 addressed all raised issues, produced a test suite and received implementation feedback. 
+   	 For changes since last publication, see <a href="#history" class="sectionRef"></a>. 
 	 A test suite is available at [[LDP-Tests]].
    </p>
  </section>
@@ -670,7 +667,7 @@
 		<a title="LDP server">LDP servers</a> MUST
 		replace the entire persistent state of the identified resource with
 		the entity representation in the body of the request. 
-		<a title="LDP server">LDP servers</a> MAY ignore <a>LDP-server-managed properties</a>,
+		<a title="LDP server">LDP servers</a> MAY ignore <a title="LDP-server-managed triples">LDP-server-managed properties</a>,
 		and MAY ignore other properties such as <code>dcterms:modified</code> 
 		and <code>dcterms:creator</code> if they are <a href="#ldpr-gen-pubclireqs">handled specially by the server</a>.
 		Any <a title="LDP server">LDP servers</a> that wish
@@ -2434,80 +2431,6 @@
 
 </section> <!-- Prefer defns -->
 </section> <!-- Header defns -->
-    
-<!-- Removed for action-113
-<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>209 Related Content</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 [[RFC7231]], [[!RFC2817]]).
-	</p>
-	<p>
-	Value:  209
-	</p>
-	<p>
-	Description:  Related Content
-	</p>
-	<p>
-	Reference:  this specification
-	</p>
-	</blockquote>
-	</div>
-
-</section>
-</section> -->
 
 <section id='link-relations'>
 <h1>Link Relations</h1>
@@ -2580,6 +2503,16 @@
 public draft it has been changed from.
 </p>
 
+
+<h2>Summary</h2>
+<p>Summary of notable changes from the <a href="http://www.w3.org/TR/2014/WD-ldp-20140916/">previous public working draft</a>.</p>
+<ul>
+	<li>No longer AT RISK: Indirect Containers, JSON-LD and Accept-Post</li>
+	<li>AT RISK that was removed: client should requirement to handle server-initiated paging</li>
+	<li>Improvements to sections about LDP-server-managed triples and client requested interaction models</li>
+</ul> 
+
+
 <!-- 
 <h2>Summary</h2>
 <p>Summary of notable changes from the <a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">previous public working draft</a>.</p>
@@ -2591,11 +2524,12 @@
 </ul> 
  -->
 
-
-<h2>Detailed history</h2>
+<!-- 
+<h2>Detailed history</h2> -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">Candidate Recommendation Draft</a></em></blockquote> -->
-
+<!-- 
 <ul>
+	<li>2014-10-20 - Prepare PR draft (SS)</li>
 	<li>2014-10-20 - Removed at-risk label for Accept-Post, leaving a note about references and dependency (SS)</li>
 	<li>2014-10-20 - Removed at-risk label for Indirect Containers (SS)</li>
 	<li>2014-10-20 - Removed at-risk label for json-ld requirement (SS)</li>
@@ -2839,6 +2773,7 @@
 	<li>2012-09-18 - Fixed up some links and worked on references, work left to do. (SS)</li>
 </ul>
 <blockquote><em><a href="http://www.w3.org/Submission/2012/SUBM-ldbp-20120326/">Submission</a></em></blockquote>
+ -->
 </section>
 
   <div class="removeOnSave showCoverage">