--- a/ldp-ucr.html Tue Sep 24 10:46:44 2013 +0100
+++ b/ldp-ucr.html Tue Sep 24 10:56:08 2013 +0100
@@ -496,10 +496,7 @@
<section>
<h2 id="story-low-end_devices"><dfn>Sharing Payload of RDF Data Among Low-End Devices</dfn></h2>
<p>
- Several projects around the idea of <a
- href="http://worldwidesemanticweb.wordpress.com/"
- title="http://worldwidesemanticweb.wordpress.com/" rel="nofollow">downscaling
- the Semantic Web</a> need to be able to ship payloads of RDF across
+ Several projects around the idea of <em>downscaling the Semantic Web</em> need to be able to ship payloads of RDF across
the nodes member of a given network. The transfers are done in a
constrained context in terms of bandwidth, scope of the local
semantics employed by the nodes and computing capabilities of the
@@ -626,7 +623,7 @@
publishing of experimental data "beyond the PDF"), and re-use.</p>
<ul>
<li><a href="#uc-aggregate_resources" title="">Aggregations</a>,
- specifically <i>Research Objects (ROs)</i> are exchanged
+ specifically <em>Research Objects (ROs)</em> are exchanged
between services and clients bringing together workflows, data
sets, annotations, and provenance.
</li>
@@ -721,11 +718,11 @@
<section id="uc1">
<h2><dfn>UC1</dfn>: Compose resources</h2>
<p>
- A number of user stories introduce the idea of a <i>container</i>
+ A number of user stories introduce the idea of a <em>container</em>
as a mechanism for composing resources within the
context of an application. A
composition would be identified by URI being a linked resource in its own
- right. Its properties may represent the <i>affordances</i>
+ right. Its properties may represent the <em>affordances</em>
of the application, enabling clients to determine what other
operations they can do. These operations may
include descriptions of application specific services that can be
@@ -804,7 +801,7 @@
<h2><dfn>UC2</dfn>: Manage resource lifecycle</h2>
<p>
This use case addresses the managed lifecycle of a resource and is
- concerned with resource <i>ownership</i>. The responsibility for
+ concerned with resource <em>ownership</em>. The responsibility for
managing resources belongs to their container. For example, a
container may accept a request from a client to make a new
resource. This use case focuses on creation and deletion of
@@ -1010,7 +1007,7 @@
<h2><dfn>UC4</dfn>: Update existing resource</h2>
<p>
Change the RDF description of a LDP resource, potentially removing
- or overwriting existing data. This allows applications to <i>enrich</i>
+ or overwriting existing data. This allows applications to <em>enrich</em>
the representation of a resource by addling additional links to
other resources.
</p>
@@ -1026,7 +1023,7 @@
This relates to user story <a>Metadata Enrichment in Broadcasting</a> and is based on the <a
href="http://www.bbc.co.uk/ontologies/sport/"
title="http://www.bbc.co.uk/ontologies/sport/" rel="nofollow">BBC
- Sports Ontology</a>. The <i>resource-centric</i> view of linked-data
+ Sports Ontology</a>. The <em>resource-centric</em> view of linked-data
provides a natural granularity for substituting, or overwriting a
resource and its data. The simplest kind of update would simply
replace what is currently known about a resource with a new
@@ -1124,7 +1121,7 @@
download a representation of the resource. This information can
then be compared with previous information held about that
resource to determine if it has changed. This versioning
- information can also be used in subsequent <i>conditional</i>
+ information can also be used in subsequent <em>conditional</em>
requests to ensure they are only applied if the version is
unchanged.
</p>
@@ -1164,7 +1161,7 @@
<p>
The value of the sensor changes in real-time as measurements are
taken. The LDP client can interrogate the resource below to
- determine if it has changed, <i>without</i> necessarily having to
+ determine if it has changed, <em>without</em> necessarily having to
download the RDF representation. As different sensor properties
are represented disjointly (separate RDF representations) they may
change independently.
@@ -1186,7 +1183,7 @@
<section id="uc6">
<h2><dfn>UC6</dfn>: Aggregate resources</h2>
<p>
- There is a requirement to be able to manage <i>collections</i> of
+ There is a requirement to be able to manage <em>collections</em> of
resources. The concept of a collection overlaps with, but is
distinct from that of a container. These collections are (weak)
aggregations, unrelated to the lifecycle management of resources,
@@ -1243,7 +1240,7 @@
<p>
Logically, a resource should not be owned by more than one
container. However, it may be a member of multiple collections
- which define a weaker form of <i>aggregation</i>. As this is
+ which define a weaker form of <em>aggregation</em>. As this is
simply a manipulation of the RDF description of a collection, it
should be possible to add the same resource to multiple
collections.
@@ -1378,7 +1375,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 <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 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 <em>next</em> resource in an ordered collection of resources. For the purposes of the example, we make use of the <em>next</em> 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'>
@prefix : <http://example.com/people/>.
@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.