changeset 463 ae72388dbb82
parent 462 3a7f9b05bad8
child 464 77fd28c9eb94
--- a/ldp.html	Wed Feb 05 15:39:51 2014 -0500
+++ b/ldp.html	Thu Feb 06 10:11:25 2014 -0500
@@ -455,15 +455,15 @@
 <p>LDP uses the term <b><dfn>informative</dfn></b> as a synonym for non-normative.</p>
 <p>The status of the sections of Linked Data Platform 1.0 (this document) is as follows:</p>
-  <li>1. Introduction: <b>informative</b></li>
+  <li>1. Introduction: <b>non-normative</b></li>
   <li>2. Terminology: <b>normative</b></li>
   <li>3. Conformance: <b>normative</b></li>
   <li>4. Linked Data Platform Resources: <b>normative</b></li>
   <li>5. Linked Data Platform Containers: <b>normative</b></li>
   <li>6. HTTP Header Definitions: <b>normative</b></li>
-  <li>A. Acknowledgements: <b>informative</b></li> 
+  <li>A. Acknowledgements: <b>non-normative</b></li> 
   <li>B.1 Normative references: <b>normative</b></li>
-  <li>B.2 Informative references: <b>informative</b></li>
+  <li>B.2 Non-normative references: <b>non-normative</b></li>
 <p>A conforming <b><dfn>LDP client</dfn></b> is a conforming HTTP client [[!HTTP11]] that follows the rules defined by LDP in
@@ -512,7 +512,7 @@
 <h1>Linked Data Platform Resources</h1>
 <section class="informative" id="ldpr-informative">
 	<p>Linked Data Platform Resources (<dfn><abbr title="Linked Data Platform Resources">LDPRs</abbr></dfn>) are HTTP resources
 		that conform to the simple patterns and conventions in this section.
 		HTTP requests to access, modify, create or delete LDPRs are accepted
@@ -533,7 +533,7 @@
 		<li>How	do I GET the entries of a large resources broken up into pages?</li>
-	<p>Additional informative guidance is available in the <a
+	<p>Additional non-normative guidance is available in the <a
 			title="LDP Best Practices and Guidelines"
@@ -545,7 +545,7 @@
 	<p>The following sections define the conformance rules for LDP servers when serving LDPRs.
 		This document also explains <a href="#ldpr-Paging">how a server paginates an LDPR's representation</a> if it gets too big.
-		Companion informative documents describe additional guidelines for use when interacting with LDPRs. 
+		Companion non-normative documents describe additional guidelines for use when interacting with LDPRs. 
 	<p>An LDP server manages two kinds of <a title="Linked Data Platform Resources">LDPRs</a>, those resources who whose state 
 	is represented using RDF (LDP-RR) and those using other formats (LDP-BR).  LDP-RRs have the unique
@@ -734,7 +734,7 @@
 		The format of the 4xx response body is not constrained by LDP.
 	</h2></section><!-- Was / #ldpr-4_5_1_1 -->
-		Informative note: Clients might provide triples equivalent to those already in the resource's state,
+		Non-normative note: Clients might provide triples equivalent to those already in the resource's state,
 		e.g. as part of a GET/update representation/PUT sequence, and those PUT requests are intended to work as long as the 
 		server-controlled triples are identical on the GET response and the subsequent PUT request.
@@ -832,6 +832,25 @@
 <section class="informative" id="ldpr-PagingIntro">
+	<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>There is a <a href="http://lists.w3.org/Archives/Public/www-tag/2013Dec/0041.html">TAG discussion</a>
+		whose goal is to reduce the need for two request-response round trips down to one, by defining a new
+		HTTP response code in the <code>2xx</code> or <code>3xx</code> class that would allow a server to
+		respond to <code>GET request-uri</code> requests with the representation of the first page 
+		(whose URI is <code>first-page-uri</code>, not <code>request-uri</code>) of a multi-page response.
+		<p>Once LDP is in
+		Candidate Recommendation, the LDP WG will make an assessment based on the status at IETF
+		working with the W3C Director to either use the newly defined response code 
+		as documented in this section or to revert to a classic 
+		<code>303</code> response pattern.
+		</p>
+		</li>
+		</ul>
+	</div>
 	<p>It sometimes happens that a
 		resource is too large to reasonably transmit its representation in a
@@ -954,7 +973,7 @@
 		<a title="Paged resource">paged resource's</a> sequence over time,
 		but SHOULD only add pages to the end of a sequence.
 		</h2><!-- Was / #ldpr-pagingGET-sequences-change -->
-		<blockquote>Informative note: 
+		<blockquote>Non-normative note: 
 		As a result, clients retrieving any <a title="Single-page resource">single-page resource</a> several times can observe its place in the sequence
 		change as the state of the <a title="Paged resource">paged resource</a> changes.
 		For example, a nominally last page's server might provide a
@@ -1040,7 +1059,7 @@
 <h1>Linked Data Platform Containers</h1>
 <section class="informative" id="ldpc-informative">		
 	<p>Many HTTP applications and sites have organizing
 		concepts that partition the overall space of resources into smaller
 		containers. Blog posts are grouped into blogs, wiki pages are grouped
@@ -1467,7 +1486,7 @@
 		<li><code>ldp:DirectContainer</code> for <a title="">Linked Data Platform Direct Container</a></li>
 		<li><code>ldp:IndirectContainer</code> for <a title="">Linked Data Platform Indirect Container</a></li>
-		Informative note: <a href="#ldp-rdfconcepts-extra-triples-types">LDPCs
+		Non-normative note: <a href="#ldp-rdfconcepts-extra-triples-types">LDPCs
 		might have additional types</a>, like any RDF resource.
 	</h2></section><!-- Was 5.2.7 / #ldpc-5_2_7 -->
@@ -1852,7 +1871,7 @@
 		membership triples associated with the deleted member resource identified by the <code>Request-URI</code>.
-		Informative note: The <a>LDP server</a> might perform additional removal 
+		Non-normative note: The <a>LDP server</a> might perform additional removal 
 		of member resources, as described in the <a href="#ldp-http-method-side-effects">normative references</a> like [[HTTP11]]. 
 		For example, the server could perform additional cleanup tasks for resources it knows are no longer referenced or have not
 		been accessed for some period of time.
@@ -1947,7 +1966,7 @@
 references, the working group has found that certain points are particularly important to understand.
 For those thoroughly familiar with the referenced specifications, these points might seem obvious, yet
 experience has shown that few non-experts find all of them obvious.  This section enumerates these topics; 
-it is simply re-stating (informatively) information locatable via the normative references.
+it is simply re-stating (non-normatively) information locatable via the normative references.
 <section id="specs-webarch" class="informative">
@@ -2233,6 +2252,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
+	<li>2014-02-06 - ACTION-127 (still WIP) use the TAG's new [23]xx code; if that code is not sufficiently through IETF process by CR, we will use a 303 (JA)</li>
 	<li>2014-02-05 - ACTION-133 Get rid of ldp:created which is subsumed by ldp:contains (SS)</li>
 	<li>2014-02-04 - ACTION-124 LDPR-RR as named graphs  (SS)</li>
 	<li>2014-02-04 - ACTION-120 (complete) Updated LDPC general, GET and POST sections (SS)</li>