--- a/ldp-ucr-wd-snapshot.html Thu Nov 07 15:28:13 2013 -0500
+++ b/ldp-ucr-wd-snapshot.html Thu Nov 07 15:29:34 2013 -0500
@@ -178,11 +178,11 @@
</p>
<h1 class="title p-name" id="title" property="dcterms:title">Linked Data Platform Use Cases and Requirements</h1>
- <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-10-28T12:23:41.000Z" id="w3c-working-draft-28-october-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft <time class="dt-published" datetime="2013-10-28">28 October 2013</time></h2>
+ <h2 property="dcterms:issued" datatype="xsd:dateTime" content="2013-10-31T00:00:00.000Z" id="w3c-working-draft-31-october-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Draft <time class="dt-published" datetime="2013-10-31">31 October 2013</time></h2>
<dl>
<dt>This version:</dt>
- <dd><a class="u-url" href="http://www.w3.org/TR/2013/WD-ldp-ucr-20131028/">http://www.w3.org/TR/2013/WD-ldp-ucr-20131028/</a></dd>
+ <dd><a class="u-url" href="http://www.w3.org/TR/2013/WD-ldp-ucr-20131031/">http://www.w3.org/TR/2013/WD-ldp-ucr-20131031/</a></dd>
<dt>Latest published version:</dt>
<dd><a href="http://www.w3.org/TR/ldp-ucr/">http://www.w3.org/TR/ldp-ucr/</a></dd>
@@ -195,7 +195,7 @@
<dt>Previous version:</dt>
- <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2012/MO-ldp-ucr-20121214/">http://www.w3.org/TR/2012/MO-ldp-ucr-20121214/</a></dd>
+ <dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2013/WD-ldp-ucr-20130131/">http://www.w3.org/TR/2013/WD-ldp-ucr-20130131/</a></dd>
<dt>Editors:</dt>
@@ -352,7 +352,7 @@
of user stories and their analysis.</li>
</ul>
<ul>
- <li><b><a href="#use%20cases" title="Use Cases">Use Cases</a></b> are
+ <li><b><a href="#usecases" title="Use Cases">Use Cases</a></b> are
used to capture and model functional requirements. Use cases
describe the system’s behavior under various conditions [<cite><a class="bibref" href="#bib-COCKBURN-2000">COCKBURN-2000</a></cite>],
cataloging who does what with the system, for what purpose, but
@@ -409,10 +409,10 @@
What would work in either case is a common understanding of the
resource, a few formats needed, and access guidance for these
resources. This would support how to acquire a link to a contact,
- how to use those links to interact with a contact (including <a href="#uc-retrieve_resource_description" title="">reading</a>,
- <a href="#uc-update_existing" title="">updating</a>,
- and <a href="#scen-delete_resource" title="">deleting</a>
- it), as well as how to easily <a href="#scen-create_resource" title="">create a
+ how to use those links to interact with a contact (including <a href="#uc3" title="">reading</a>,
+ <a href="#uc4" title="">updating</a>,
+ and <a href="#s2.2" title="">deleting</a>
+ it), as well as how to easily <a href="#s2.1" title="">create a
new contact</a>, add it to my contacts, and when deleting a
contact, how it would be removed from my list of contacts. It
would also be good to be able to add some application-specific
@@ -445,17 +445,17 @@
maintaining various identifiers in different formats and instead
of having to manually supply those identifiers to each one’s
corresponding custom application, we could essentially build a set
- of bookmarks to it all? When we want to <a href="#uc-retrieve_resource_description" title="">examine</a>
- or <a href="#uc-update_existing" title="">change</a>
+ of bookmarks to it all? When we want to <a href="#uc3" title="">examine</a>
+ or <a href="#uc4" title="">change</a>
their contents, would it not be simpler if there were a single
consistent application interface that they all supported?
</p>
<p>
The information held by any single organization might be a mix of
- simple data and <a href="#uc-aggregate_resources" title="">collections
+ simple data and <a href="#uc6" title="">collections
of other data</a>, for example, a bank account balance and a
collection of historical transactions. Our bank might easily have
- <a href="#scen-create_a_nested_composition" title="">a collection of accounts for each member of its collection
+ <a href="#s1.2" title="">a collection of accounts for each member of its collection
of customers</a>.
</p>
</section>
@@ -519,7 +519,7 @@
<p>The 'Digital Objects Cluster' contains a number of relevant
use cases:</p>
<ul>
- <li>Grouping: This should "Allow the end-users to define <a href="#uc-aggregate_resources" title="">groups of resources</a>
+ <li>Grouping: This should "Allow the end-users to define <a href="#uc6" title="">groups of resources</a>
on the web that for some reason belong together. The relationship
that exists between the resources is often left unspecified. Some
of the resources in a group may not be under control of the
@@ -527,12 +527,12 @@
</li>
</ul>
<ul>
- <li>Enrichment: "Enable end-users to <a href="#uc-update_existing" title="">link resources
+ <li>Enrichment: "Enable end-users to <a href="#uc4" title="">link resources
together</a>."
</li>
</ul>
<ul>
- <li>Browsing: "<a href="#uc-filter_resource_description" title="">Support end-user browsing through groups</a> and
+ <li>Browsing: "<a href="#uc7" title="">Support end-user browsing through groups</a> and
resources that belong to the groups."
</li>
</ul>
@@ -544,7 +544,7 @@
<p>The 'Collections' cluster also contains a number of relevant
use cases:</p>
<ul>
- <li>Collection-level description: "Provide <a href="#uc-filter_resource_description" title="">metadata
+ <li>Collection-level description: "Provide <a href="#uc7" title="">metadata
pertaining to a collection as a whole</a>, in contrast to item-level
description."
</li>
@@ -572,7 +572,7 @@
predict problems, and handle logistics. In order to effectively
and efficiently collect, produce, and analyze all this data, a
fundamental set of loosely coupled standard data sources are
- needed. A simple, low-cost way to <a href="#uc-retrieve_resource_description" title="">expose
+ needed. A simple, low-cost way to <a href="#uc3" title="">expose
data</a> from the diverse set of monitored services is needed, one
that can easily integrate into the municipalities of other systems
that inspect and analyze the data. All these services have links
@@ -611,7 +611,7 @@
<h3 id="story-media" aria-level="2" role="heading"><span class="secno">3.7 </span><dfn id="dfn-metadata-enrichment-in-broadcasting">Metadata Enrichment in Broadcasting</dfn></h3>
<p>
There are many different use cases when broadcasters show interest
- in metadata <a href="#uc-update_existing" title="">
+ in metadata <a href="#uc4" title="">
enrichment</a>:
</p>
<ul>
@@ -639,7 +639,7 @@
For infrastructure management (such as storage systems, virtual
machine environments, and similar IaaS and PaaS concepts), it is
important to provide an environment in which information from
- different sources can be <a href="#uc-aggregate_resources" title="">aggregated</a>, <a href="#uc-filter_resource_description" title="">filtered</a>,
+ different sources can be <a href="#uc6" title="">aggregated</a>, <a href="#uc7" title="">filtered</a>,
and visualized effectively. Specifically, the following use cases
need to be taken into account:
</p>
@@ -722,7 +722,7 @@
contents, but this leaves many open challenges when building a
federation of these repositories to serve the need of asset
reuse. These include accessing and querying individual
- repositories and efficiently retrieving <a href="#uc-has_resource_changed" title="">
+ repositories and efficiently retrieving <a href="#uc5" title="">
updated content</a> without having to retrieve the whole content.
The Data Warehousing integration approach allows us to cope
with heterogeneity of sources technologies and to benefit from the
@@ -783,7 +783,7 @@
through local trusted sharing, analysis, dissemination (including
publishing of experimental data "beyond the PDF"), and re-use.</p>
<ul>
- <li><a href="#uc-aggregate_resources" title="">Aggregations</a>,
+ <li><a href="#uc6" title="">Aggregations</a>,
specifically <em>Research Objects (ROs)</em> are exchanged
between services and clients bringing together workflows, data
sets, annotations, and provenance.
@@ -1085,7 +1085,7 @@
for "Resource descriptions for each person and project" allowing
project teams to review information held about these resources.
The example below illustrates the kinds of information that might
- be held about organizational structures based on the <a href="http://www.epimorphics.com" title="http://www.epimorphics.com" rel="nofollow">Epimorphics</a>
+ be held about organizational structures based on the <a href="http://www.epimorphics.com/web/" title="http://www.epimorphics.com" rel="nofollow">Epimorphics</a>
organizational ontology [<cite><a class="bibref" href="#bib-ORG-ONT">ORG-ONT</a></cite>].
</p>
<p>Examples 4 and 5 below define two resources that would be hosted on an <abbr title="Linked Data Platform">LDP</abbr> server based at
@@ -1509,7 +1509,7 @@
<p>In user story, <a href="#dfn-maintaining-social-contact-information" class="internalDFN">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.</p>
-<p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There is no presumption that the <abbr title="Linked Data Platform">LDP</abbr> specification will recommend the use of this vocabulary.</p>
+<p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab">XHTML Metainformation Vocabulary</a>. There is no presumption that the <abbr title="Linked Data Platform">LDP</abbr> specification will recommend the use of this vocabulary.</p>
<div class="example"><div class="example-title"><span>Example 17</span></div><pre class="example"><code>
@prefix : <http://example.com/people/>.
@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.
--- a/ldp-ucr-wd.html Thu Nov 07 15:28:13 2013 -0500
+++ b/ldp-ucr-wd.html Thu Nov 07 15:29:34 2013 -0500
@@ -23,7 +23,7 @@
// subtitle : "an excellent document",
// if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
+ publishDate: "2013-10-31",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -31,9 +31,9 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2012-12-14",
- previousMaturity: "MO",
- previousURI: "http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements",
+ previousPublishDate: "2013-01-31",
+ previousMaturity: "WD",
+ previousURI: "http://www.w3.org/TR/2013/WD-ldp-ucr-20130131/",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "http://www.w3.org/2012/ldp/hg/ldp-ucr.html",
@@ -253,7 +253,7 @@
of user stories and their analysis.</li>
</ul>
<ul>
- <li><b><a href="#use%20cases" title="Use Cases">Use Cases</a></b> are
+ <li><b><a href="#usecases" title="Use Cases">Use Cases</a></b> are
used to capture and model functional requirements. Use cases
describe the system’s behavior under various conditions [[COCKBURN-2000]],
cataloging who does what with the system, for what purpose, but
@@ -311,11 +311,11 @@
resource, a few formats needed, and access guidance for these
resources. This would support how to acquire a link to a contact,
how to use those links to interact with a contact (including <a
- href="#uc-retrieve_resource_description" title="">reading</a>,
- <a href="#uc-update_existing" title="">updating</a>,
- and <a href="#scen-delete_resource" title="">deleting</a>
+ href="#uc3" title="">reading</a>,
+ <a href="#uc4" title="">updating</a>,
+ and <a href="#s2.2" title="">deleting</a>
it), as well as how to easily <a
- href="#scen-create_resource" title="">create a
+ href="#s2.1" title="">create a
new contact</a>, add it to my contacts, and when deleting a
contact, how it would be removed from my list of contacts. It
would also be good to be able to add some application-specific
@@ -349,17 +349,17 @@
of having to manually supply those identifiers to each one’s
corresponding custom application, we could essentially build a set
of bookmarks to it all? When we want to <a
- href="#uc-retrieve_resource_description" title="">examine</a>
- or <a href="#uc-update_existing" title="">change</a>
+ href="#uc3" title="">examine</a>
+ or <a href="#uc4" title="">change</a>
their contents, would it not be simpler if there were a single
consistent application interface that they all supported?
</p>
<p>
The information held by any single organization might be a mix of
- simple data and <a href="#uc-aggregate_resources" title="">collections
+ simple data and <a href="#uc6" title="">collections
of other data</a>, for example, a bank account balance and a
collection of historical transactions. Our bank might easily have
- <a href="#scen-create_a_nested_composition"
+ <a href="#s1.2"
title="">a collection of accounts for each member of its collection
of customers</a>.
</p>
@@ -425,7 +425,7 @@
use cases:</p>
<ul>
<li>Grouping: This should "Allow the end-users to define <a
- href="#uc-aggregate_resources" title="">groups of resources</a>
+ href="#uc6" title="">groups of resources</a>
on the web that for some reason belong together. The relationship
that exists between the resources is often left unspecified. Some
of the resources in a group may not be under control of the
@@ -434,12 +434,12 @@
</ul>
<ul>
<li>Enrichment: "Enable end-users to <a
- href="#uc-update_existing" title="">link resources
+ href="#uc4" title="">link resources
together</a>."
</li>
</ul>
<ul>
- <li>Browsing: "<a href="#uc-filter_resource_description"
+ <li>Browsing: "<a href="#uc7"
title="">Support end-user browsing through groups</a> and
resources that belong to the groups."
</li>
@@ -453,7 +453,7 @@
use cases:</p>
<ul>
<li>Collection-level description: "Provide <a
- href="#uc-filter_resource_description" title="">metadata
+ href="#uc7" title="">metadata
pertaining to a collection as a whole</a>, in contrast to item-level
description."
</li>
@@ -482,7 +482,7 @@
and efficiently collect, produce, and analyze all this data, a
fundamental set of loosely coupled standard data sources are
needed. A simple, low-cost way to <a
- href="#uc-retrieve_resource_description" title="">expose
+ href="#uc3" title="">expose
data</a> from the diverse set of monitored services is needed, one
that can easily integrate into the municipalities of other systems
that inspect and analyze the data. All these services have links
@@ -521,7 +521,7 @@
<h2 id="story-media"><dfn>Metadata Enrichment in Broadcasting</dfn></h2>
<p>
There are many different use cases when broadcasters show interest
- in metadata <a href="#uc-update_existing" title="">
+ in metadata <a href="#uc4" title="">
enrichment</a>:
</p>
<ul>
@@ -549,9 +549,9 @@
For infrastructure management (such as storage systems, virtual
machine environments, and similar IaaS and PaaS concepts), it is
important to provide an environment in which information from
- different sources can be <a href="#uc-aggregate_resources"
+ different sources can be <a href="#uc6"
title="">aggregated</a>, <a
- href="#uc-filter_resource_description" title="">filtered</a>,
+ href="#uc7" title="">filtered</a>,
and visualized effectively. Specifically, the following use cases
need to be taken into account:
</p>
@@ -635,7 +635,7 @@
federation of these repositories to serve the need of asset
reuse. These include accessing and querying individual
repositories and efficiently retrieving <a
- href="#uc-has_resource_changed" title="">
+ href="#uc5" title="">
updated content</a> without having to retrieve the whole content.
The Data Warehousing integration approach allows us to cope
with heterogeneity of sources technologies and to benefit from the
@@ -696,7 +696,7 @@
through local trusted sharing, analysis, dissemination (including
publishing of experimental data "beyond the PDF"), and re-use.</p>
<ul>
- <li><a href="#uc-aggregate_resources" title="">Aggregations</a>,
+ <li><a href="#uc6" title="">Aggregations</a>,
specifically <em>Research Objects (ROs)</em> are exchanged
between services and clients bringing together workflows, data
sets, annotations, and provenance.
@@ -1003,7 +1003,7 @@
project teams to review information held about these resources.
The example below illustrates the kinds of information that might
be held about organizational structures based on the <a
- href="http://www.epimorphics.com"
+ href="http://www.epimorphics.com/web/"
title="http://www.epimorphics.com" rel="nofollow">Epimorphics</a>
organizational ontology [[ORG-ONT]].
</p>
@@ -1428,7 +1428,7 @@
<p>In user story, <a>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.</p>
-<p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There is no presumption that the LDP specification will recommend the use of this vocabulary.</p>
+<p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab">XHTML Metainformation Vocabulary</a>. There is no presumption that the LDP specification will recommend the use of this vocabulary.</p>
<pre class='example'><code>
@prefix : <http://example.com/people/>.
@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.
--- a/ldp-ucr.html Thu Nov 07 15:28:13 2013 -0500
+++ b/ldp-ucr.html Thu Nov 07 15:29:34 2013 -0500
@@ -31,9 +31,9 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2012-12-14",
- previousMaturity: "MO",
- previousURI: "http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements",
+ previousPublishDate: "2013-01-31",
+ previousMaturity: "WD",
+ previousURI: "http://www.w3.org/TR/2013/WD-ldp-ucr-20130131/",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "http://www.w3.org/2012/ldp/hg/ldp-ucr.html",
@@ -253,7 +253,7 @@
of user stories and their analysis.</li>
</ul>
<ul>
- <li><b><a href="#use%20cases" title="Use Cases">Use Cases</a></b> are
+ <li><b><a href="#usecases" title="Use Cases">Use Cases</a></b> are
used to capture and model functional requirements. Use cases
describe the system’s behavior under various conditions [[COCKBURN-2000]],
cataloging who does what with the system, for what purpose, but
@@ -311,11 +311,11 @@
resource, a few formats needed, and access guidance for these
resources. This would support how to acquire a link to a contact,
how to use those links to interact with a contact (including <a
- href="#uc-retrieve_resource_description" title="">reading</a>,
- <a href="#uc-update_existing" title="">updating</a>,
- and <a href="#scen-delete_resource" title="">deleting</a>
+ href="#uc3" title="">reading</a>,
+ <a href="#uc4" title="">updating</a>,
+ and <a href="#s2.2" title="">deleting</a>
it), as well as how to easily <a
- href="#scen-create_resource" title="">create a
+ href="#s2.1" title="">create a
new contact</a>, add it to my contacts, and when deleting a
contact, how it would be removed from my list of contacts. It
would also be good to be able to add some application-specific
@@ -349,17 +349,17 @@
of having to manually supply those identifiers to each one’s
corresponding custom application, we could essentially build a set
of bookmarks to it all? When we want to <a
- href="#uc-retrieve_resource_description" title="">examine</a>
- or <a href="#uc-update_existing" title="">change</a>
+ href="#uc3" title="">examine</a>
+ or <a href="#uc4" title="">change</a>
their contents, would it not be simpler if there were a single
consistent application interface that they all supported?
</p>
<p>
The information held by any single organization might be a mix of
- simple data and <a href="#uc-aggregate_resources" title="">collections
+ simple data and <a href="#uc6" title="">collections
of other data</a>, for example, a bank account balance and a
collection of historical transactions. Our bank might easily have
- <a href="#scen-create_a_nested_composition"
+ <a href="#s1.2"
title="">a collection of accounts for each member of its collection
of customers</a>.
</p>
@@ -425,7 +425,7 @@
use cases:</p>
<ul>
<li>Grouping: This should "Allow the end-users to define <a
- href="#uc-aggregate_resources" title="">groups of resources</a>
+ href="#uc6" title="">groups of resources</a>
on the web that for some reason belong together. The relationship
that exists between the resources is often left unspecified. Some
of the resources in a group may not be under control of the
@@ -434,12 +434,12 @@
</ul>
<ul>
<li>Enrichment: "Enable end-users to <a
- href="#uc-update_existing" title="">link resources
+ href="#uc4" title="">link resources
together</a>."
</li>
</ul>
<ul>
- <li>Browsing: "<a href="#uc-filter_resource_description"
+ <li>Browsing: "<a href="#uc7"
title="">Support end-user browsing through groups</a> and
resources that belong to the groups."
</li>
@@ -453,7 +453,7 @@
use cases:</p>
<ul>
<li>Collection-level description: "Provide <a
- href="#uc-filter_resource_description" title="">metadata
+ href="#uc7" title="">metadata
pertaining to a collection as a whole</a>, in contrast to item-level
description."
</li>
@@ -482,7 +482,7 @@
and efficiently collect, produce, and analyze all this data, a
fundamental set of loosely coupled standard data sources are
needed. A simple, low-cost way to <a
- href="#uc-retrieve_resource_description" title="">expose
+ href="#uc3" title="">expose
data</a> from the diverse set of monitored services is needed, one
that can easily integrate into the municipalities of other systems
that inspect and analyze the data. All these services have links
@@ -521,7 +521,7 @@
<h2 id="story-media"><dfn>Metadata Enrichment in Broadcasting</dfn></h2>
<p>
There are many different use cases when broadcasters show interest
- in metadata <a href="#uc-update_existing" title="">
+ in metadata <a href="#uc4" title="">
enrichment</a>:
</p>
<ul>
@@ -549,9 +549,9 @@
For infrastructure management (such as storage systems, virtual
machine environments, and similar IaaS and PaaS concepts), it is
important to provide an environment in which information from
- different sources can be <a href="#uc-aggregate_resources"
+ different sources can be <a href="#uc6"
title="">aggregated</a>, <a
- href="#uc-filter_resource_description" title="">filtered</a>,
+ href="#uc7" title="">filtered</a>,
and visualized effectively. Specifically, the following use cases
need to be taken into account:
</p>
@@ -635,7 +635,7 @@
federation of these repositories to serve the need of asset
reuse. These include accessing and querying individual
repositories and efficiently retrieving <a
- href="#uc-has_resource_changed" title="">
+ href="#uc5" title="">
updated content</a> without having to retrieve the whole content.
The Data Warehousing integration approach allows us to cope
with heterogeneity of sources technologies and to benefit from the
@@ -696,7 +696,7 @@
through local trusted sharing, analysis, dissemination (including
publishing of experimental data "beyond the PDF"), and re-use.</p>
<ul>
- <li><a href="#uc-aggregate_resources" title="">Aggregations</a>,
+ <li><a href="#uc6" title="">Aggregations</a>,
specifically <em>Research Objects (ROs)</em> are exchanged
between services and clients bringing together workflows, data
sets, annotations, and provenance.
@@ -1003,7 +1003,7 @@
project teams to review information held about these resources.
The example below illustrates the kinds of information that might
be held about organizational structures based on the <a
- href="http://www.epimorphics.com"
+ href="http://www.epimorphics.com/web/"
title="http://www.epimorphics.com" rel="nofollow">Epimorphics</a>
organizational ontology [[ORG-ONT]].
</p>
@@ -1428,7 +1428,7 @@
<p>In user story, <a>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.</p>
-<p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There is no presumption that the LDP specification will recommend the use of this vocabulary.</p>
+<p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab">XHTML Metainformation Vocabulary</a>. There is no presumption that the LDP specification will recommend the use of this vocabulary.</p>
<pre class='example'><code>
@prefix : <http://example.com/people/>.
@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.