--- a/ldp-ucr.html Mon Jun 17 17:08:22 2013 +0100
+++ b/ldp-ucr.html Mon Jun 24 16:39:01 2013 +0100
@@ -1492,14 +1492,38 @@
<li>It's not really the resource description that's being paginated, but the values of a particular property.</li>
<li>The server is responsible for pagination, and may decide how large the pages are.</li>
<li>Pagination should apply symmetrically to both <emph>incoming</emph> and <emph>outgoing</emph> properties.</li>
- <li>The next-page URL should be opaque.</li>
+ <li>The next-page URL should be treated as opaque.</li>
</ul>
<section>
<h3 id="scen-access_media_resources">Primary scenario: large numbers of contacts</h3>
In user-story, <a href="#story-social" title="Social Contacts">Maintaining Social Contact Information</a>, it is not uncommon for users to have a very large number of contacts.
-This leads to a very large resource description, especially if some basic information about the contacts is included as well. The size of this representation may be so large that retrieval in a single HTTP request is impractical.
+This leads to a very large resource description, especially if some basic information about the contacts is included as well. The size of this representation may be so large that retrieval in a single HTTP request is impractical.
+
+In this example the response to the first request includes a reference to the <i>next</i> resource in an ordered collection of resources. For the purposes of the example, we make use of the <i>next</i> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There should be no presumption that the LDP specification will recommend the use of this vocabulary to support this use-case.
+ <pre class='example'>
+@prefix : <http://example.com/people/>.
+@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.
+
+:alice a foaf:Person;
+ rdfs:label "Alice";
+ foaf:mbox <mailto:alice@example.com>.
+
+<> xhv:next <http://example.com/1234567890>.
+ </pre>
+
+ When the client requests the resource identified by <i>next</i>, the response includes additional content that can be merged with the earlier data to construct a more complete model of the originally requested resource. It may also contain further <i>next</i> links, which may be requested in turn.
+
+ The following representation is the response to the resource identified by <i>next</i>, completing the contacts list.
+
+ <pre class='example'>
+@prefix : <http://example.com/people/>.
+
+:bob a foaf:Person;
+ rdfs:label "Bob";
+ foaf:mbox <mailto:bob@example.com>.
+ </pre>
</section>
</section>