ldp.html
changeset 634 1aaf16a1b67e
parent 601 5fc4b4b9efc2
child 636 46b0ed651256
--- a/ldp.html	Thu Jun 05 11:22:16 2014 -0400
+++ b/ldp.html	Thu Jun 05 11:50:28 2014 -0400
@@ -146,6 +146,24 @@
 				,   status:   "Internet Draft"
 				,   publisher:  "IETF"
 				},
+				"Accept-Post": {
+					title:    "The Accept-Post HTTP Header"
+				,   href:     "http:tools.ietf.org/html/draft-wilde-accept-post"
+				,   authors:  [
+						"J. Arwe", "S. Speicher", "E. Wilde"
+					]
+				,   status:   "Internet Draft"
+				,   publisher:  "IETF"
+				},
+				"LDP-Tests": {
+					title:    "Linked Data Platform 1.0 Test Cases"
+				,   href:     "https://dvcs.w3.org/hg/ldpwg/raw-file/tip/Test%20Cases/LDP%20Test%20Cases.html"
+				,   authors:  [
+						"R. Garcia-Castro", "F. Serena"
+					]
+				,   status:   "Editor's Draft of Working Group Note"
+				,   publisher:  "W3C"
+				},
 			},
       };
     </script>
@@ -241,7 +259,16 @@
    	 raised issues and as a result some significant changes have been made, see <a href="#history" class="sectionRef"></a>.  Most notably 
    	 the Working Group has decided to handle paging as an extension to LDP in a separate
    	 REC-track specification. [[LDP-PAGING]]
+	 A test suite is available at [[LDP-Tests]].
    </p>
+   <p>The following features are At Risk:</p>
+   <ol>
+   <li>The <a href="#header-accept-post">HTTP Accept-Post header</a>, 
+		that allows clients to determine which media types a server accepts on POST requests.
+	</li>
+   <li>The requirement that LDP clients be <a href="#atrisk-paging">paging-aware</a>.
+	</li>
+   </ol>
  </section>
  
 <section class="informative" id="intro">
@@ -1900,7 +1927,7 @@
 		<p>The LDP Working Group proposes incorporation of the features described in this section.</p>
 		<ul>
 		<li>The addition of <code>Accept-Post</code> in this specification is pending 
-		advancement of an <a href="https://datatracker.ietf.org/doc/draft-wilde-accept-post/">IETF draft</a>
+		advancement of an <a href="https://datatracker.ietf.org/doc/draft-wilde-accept-post/">IETF draft</a> [[Accept-Post]]
 		that would fully include it, based on the Accept-Patch header's design from [[!RFC5789]].  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>
@@ -2375,6 +2402,7 @@
 <h2>Detailed history</h2>
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-06-05 - Fixed LC1 date in change history pseudo-heading, was 2014 (JA) </li>
 	<li>2014-05-19 - Revert membership definition to be about LDPCs, not LDP-RS's (JA) </li>
 	<li>2014-05-09 - Respond to Joe Ross's LC2 comments (JA) </li>
 	<li>2014-04-28 - Added usage for ldp:NonLDPSource (SS) </li>
@@ -2476,7 +2504,7 @@
 	<li>2013-08-19 - Basic preparation for edits unto LC draft (SS)</li>
 </ul>
 
-<blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft (2014-07-30)</a></em></blockquote>
+<blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft (2013-07-30)</a></em></blockquote>
 <ul>
 	<li>2013-07-24 - Moved 4.7.2 (from HEAD) to 4.3.2 (GET), shifted rest of GET section by one (SS)</li>
 	<li>2013-07-24 - Moved 4.10.2.5-&gt;4.10.2.4.3,4.10.2.6-&gt;4.10.2.4.1,4.10.2.7-&gt;4.10.2.4.2 and added samples (SS)</li>