address subset of sandro's originall-off-list comments; rest being handled on-list
--- a/ldp-paging.html Tue Jun 10 11:39:03 2014 -0400
+++ b/ldp-paging.html Tue Jun 10 16:33:59 2014 -0400
@@ -251,7 +251,7 @@
</head>
<body>
<section id='abstract'>
-This document describes a model for clients and servers to be able to efficiently retrieve large Linked Data Platform
+This document describes a HTTP-based protocol for clients and servers to be able to efficiently retrieve large Linked Data Platform
Resource representations by splitting up the responses into separate URL-addressable page resources.
</section>
@@ -329,7 +329,8 @@
</p>
<dl class="glossary">
<dt><dfn>Paged resource</dfn></dt>
- <dd>A LDPR whose representation may be too large to fit in a single HTTP response, for which an
+ <dd>A LDPR whose representation may be too large for a server to construct in a single HTTP response
+ (e.g. without running out of memory), for which an
<a>LDP Paging server</a> offers a sequence of single-page <a title="Linked Data Platform Resource">LDPRs</a>.
<p>
When the representations of the sequence's resources
@@ -583,7 +584,7 @@
we’ll split the response across two pages.
The client
retrieves <code>http://example.org/customer-relations</code>, and
- the server responds with <a href="#atrisk-333">status code <code>333 Returning Related</code></a>,
+ the server responds with <a href="#atrisk-2NN">status code <code>2NN Returning Related</code></a>,
a <code>Location: http://example.org/customer-relations?page1</code> HTTP response header
identifying the first page as the resource whose representation is enclosed in the response,
and the following representation:
@@ -624,7 +625,7 @@
<p>
Because the server includes a <code>Link: <http://example.org/customer-relations?p=2>; rel='next'</code>
- response header, and the status code is 3xx (<code>333 Returning Related</code> in this case),
+ response header, and the status code is 2xx (<code>2NN Returning Related</code> in this case),
the client knows that more data exists and where to find it.
The server determines the size of the pages using application specific methods not defined
within this specificiation. The next page link's target URI is also
@@ -765,7 +766,7 @@
</h2></section>
<!-- TODO: Need to rework this^ and possibly relocate it ... does not apply only to LDPCs -->
- <div class="atrisk" id="atrisk-333"><p class="atrisktext">Feature At Risk</p>
+ <div class="atrisk" id="atrisk-2NN"><p class="atrisktext">Feature At Risk</p>
<p>The LDP Working Group proposes incorporation of the features described in the next compliance clause.</p>
<ul>
<li><p>
@@ -778,19 +779,21 @@
</p></li>
<li><p>
For the purposes of drafting this section, we assume that the
- new code's value is <code>333 Returning Related</code>,
- <a href="http://lists.w3.org/Archives/Public/www-tag/2014Jan/0023.html">an LDP extrapolation from TAG discussions,</a>
+ new code's value is <code>2NN Returning Related</code>,
+ <a href="http://lists.w3.org/Archives/Public/www-tag/2014Jan/0023.html">an LDP extrapolation from TAG discussions</a>,
and its definition is given by
- <a href="http://lists.w3.org/Archives/Public/www-tag/2014Jan/0015.html">Henry Thompson's strawman</a>, with the substitution of 333 for 2xx.
+ <a href="http://lists.w3.org/Archives/Public/www-tag/2014Jan/0015.html">Henry Thompson's strawman</a>,
+ with the substitution of 2NN for 2xx as suggested in
+ <a href="https://github.com/w3ctag/spec-reviews/blob/master/2014/04/http-209.md">the TAG's draft comments, item 2</a>.
Note: nothing prevents servers or clients from using <code>303 See Other</code> responses to
- requests for <a title="Paged resource">paged resources</a>. The only significant differences between 303 and 333 responses
+ requests for <a title="Paged resource">paged resources</a>. The only significant differences between 303 and 2NN responses
are the extra round trip required for the client to retrieve the representation of the first page when using 303,
and the non-cacheable nature of 303 responses.
</p></li>
<li><p>
Once LDP-Paging is a
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 333
+ working with the W3C Director, to either use the newly defined response code 2NN
as documented in this section or to revert to a classic
<code>303</code> response pattern.
</p></li>
@@ -799,7 +802,7 @@
<section id="ldpr-status-code"><h2 class="normal">
<a title="LDP Paging server">LDP Paging servers</a> SHOULD respond
- with HTTP status code <code>333 Returning Related</code>
+ with HTTP status code <code>2NN Returning Related</code>
to successful <code>GET</code> requests with any <a title="Paged resource">paged resource</a>
as the <code>Request-URI</code>, although any appropriate code such as <code>303 See Other</code> MAY be used.
</h2></section>