--- a/ldp-ucr.html Thu Aug 22 15:33:00 2013 +0100
+++ b/ldp-ucr.html Fri Aug 23 10:31:24 2013 +0100
@@ -715,7 +715,7 @@
not be interpreted normatively.</p>
<section>
- <h2 id="uc-manage_containers">UC1: Manage containers</h2>
+ <h2 id="uc1">UC1: Manage containers</h2>
<p>
A number of user stories introduce the idea of a <i>container</i>
as a mechanism for creating and managing resources within the
@@ -729,7 +729,7 @@
invoked by exchanging RDF documents.
</p>
<ul>
- <li><a>NF1</a>: Provide "access guidance" (affordances) from user story, <a>Maintaining Social Contact Information</a>.</li>
+ <li><a>NF1.1</a>: Provide "access guidance" (affordances) from user story, <a>Maintaining Social Contact Information</a>.</li>
</ul>
<section>
@@ -795,7 +795,7 @@
</section>
<section>
- <h2 id="uc-manage_resources">UC2: Manage resources</h2>
+ <h2 id="uc2">UC2: Manage resources</h2>
<p>
This use case addresses the managed lifecycle of a resource and is
concerned with resource <i>ownership</i>. The responsibility for
@@ -809,13 +809,13 @@
container.
</p>
<ul>
- <li><a>NF2</a>: Non-duplication of resources: "Eliminate multiple
+ <li><a>NF2.1</a>: Non-duplication of resources: "Eliminate multiple
copies", representing resources in a single place (from <a>Maintaining Social Contact Information</a>).
</li>
- <li><a>NF3</a>: Distribution of resources: Linked data "may be stored on
+ <li><a>NF2.2</a>: Distribution of resources: Linked data "may be stored on
separate servers" (from <a>Maintaining Social Contact Information</a>).
</li>
- <li><a>NF4</a>: Consistent, global naming: Resources should be "linked to
+ <li><a>NF2.3</a>: Consistent, global naming: Resources should be "linked to
consistently, ... instead of maintaining various identifiers in
different formats" (from <a>Keeping Track of Personal and Business Relationships</a>).
</li>
@@ -898,7 +898,7 @@
</section>
<section>
- <h2 id="uc-retrieve_resource_description">UC3: Retrieve resource description</h2>
+ <h2 id="uc3">UC3: Retrieve resource description</h2>
<p>Access the current description of a resource, containing
properties of that resource and links to related resources. The
representation may include descriptions of related resources that
@@ -909,14 +909,10 @@
last update or entity tag) so that subsequent updates can ensure
they are being applied to the correct version.</p>
<ul>
- <li>Use standard vocabularies as appropriate to enable a
- "common understanding of the resource" (from <a
- href="#story-social" title="">Maintaining
- Social Contact Information</a>).
+ <li><a>NF3.1</a>: Use standard vocabularies as appropriate to enable a
+ "common understanding of the resource" (from <a>Maintaining Social Contact Information</a>).
</li>
- <li>A "scalable linking model is key" (from <a
- href="#story-meter_monitoring" title="">#Municipality
- Operational Monitoring</a>).
+ <li><a>NF3.2</a>: A "scalable linking model is key" (from <a>Municipality Operational Monitoring</a>).
</li>
</ul>
@@ -997,7 +993,7 @@
</section>
<section>
- <h2 id="uc-update_existing">UC4: Update existing resource</h2>
+ <h2 id="uc4">UC4: 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>
@@ -1005,19 +1001,15 @@
other resources.
</p>
<ul>
- <li>Unrestricted vocabulary: It should be possible be "able
- to add ... application-specific data" to resources (from <a
- href="#story-social" title="">#Maintaining
- Social Contact Information</a>).
+ <li><a>NF4.1</a>: Unrestricted vocabulary: It should be possible be "able
+ to add ... application-specific data" to resources (from <a>Maintaining Social Contact Information</a>).
</li>
</ul>
<section>
<h3 id="scen-update_enrichment">Primary scenario: enrichment</h3>
<p>
- This relates to user story <a
- href="#story-media" title="">
- Metadata Enrichment in Broadcasting</a> and is based on the <a
+ 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
@@ -1062,8 +1054,7 @@
<h3 id="scen-alt_selective_update">Alternative scenario: selective
update of a resource</h3>
<p>
- This relates to user story <a href="#story-data_catalogs" title="">Data
- Catalogs</a>, based on the <a href="http://vocab.deri.ie/dcat"
+ This relates to user story <a>Data Catalogs</a>, based on the <a href="http://vocab.deri.ie/dcat"
title="http://vocab.deri.ie/dcat"
rel="nofollow">Data Catalog Vocabulary</a>. A catalogue is
described by the following RDF model.
@@ -1079,10 +1070,10 @@
<p>
A catalog may contain multiple datasets, so when linking to new
datasets it would be simpler and preferable to selectively add
- just the new dataset links. A <a
+ just the new dataset links. For example, a <a
href="http://docs.api.talis.com/getting-started/changesets"
title="http://docs.api.talis.com/getting-started/changesets"
- rel="nofollow">Talis changeset</a> could be used to add a new dc:title to the
+ rel="nofollow">Talis changeset</a> might be used to add a new dc:title to the
dataset. The following update would be directed to the catalogue
to add an additional dataset.
</p>
@@ -1108,7 +1099,7 @@
</section>
<section>
- <h2 id="uc-has_resource_changed">UC5: Determine if a resource has changed</h2>
+ <h2 id="uc5">UC5: Determine if a resource has changed</h2>
<p>
It should be possible to retrieve versioning information about a
resource (e.g. last modified or entity tag) without having to
@@ -1123,9 +1114,7 @@
<section>
<h3 id="scen-primary_has_changed">Primary scenario</h3>
<p>
- Based on the user story, <a
- href="#story-constrained_devices" title="">
- Constrained Devices and Networks</a>, an LDP server could be configured to
+ Based on the user story, <a>Constrained Devices and Networks</a>, an LDP server could be configured to
act as a proxy for a CoAP [[COAP]] based <a
href="http://en.wikipedia.org/wiki/Web_of_Things"
title="http://en.wikipedia.org/wiki/Web_of_Things" rel="nofollow">Web
@@ -1171,7 +1160,7 @@
</section>
<section>
- <h2 id="uc-aggregate_resources">UC6: Aggregate resources</h2>
+ <h2 id="uc6">UC6: Aggregate resources</h2>
<p>
There is a requirement to be able to manage <i>collections</i> of
resources. The concept of a collection overlaps with, but is
@@ -1185,16 +1174,12 @@
may belong to multiple collections, or to none.
</p>
<ul>
- <li>Resource descriptions are a "mix of simple data and
- collections" (from <a
- href="#story-tracking_relationships"
- title="">#Keeping Track of Personal and Business
- Relationships</a>).
+ <li><a>NF6.1</a>: Resource descriptions are a "mix of simple data and
+ collections" (from <a>Keeping Track of Personal and Business Relationships</a>).
</li>
- <li>Relative URIs: It should be possible to "ship payloads of
+ <li><a>NF6.2</a>: Relative URIs: It should be possible to "ship payloads of
RDF" for a collection as a whole without breaking internal links
- (from <a href="#story-constrained_devices" title="">Constrained
- Devices and Networks</a>).
+ (from <a>Constrained Devices and Networks</a>).
</li>
</ul>
@@ -1202,8 +1187,7 @@
<h3 id="scen-add_a_resource_to_a_collection">Primary scenario: add a resource
to a collection</h3>
<p>
- This example is from <a href="#story-lld" title="">Library
- Linked Data</a> and LLD-UC [[LLD-UC]], specifically <a
+ This example is from <a>Library Linked Data</a> and LLD-UC [[LLD-UC]], specifically <a
href="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search"
title="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search"
rel="nofollow">Subject Search</a>.
@@ -1242,8 +1226,7 @@
As a machine-readable collection of medical terms, the <a
href="http://www.ihtsdo.org"
title="http://www.ihtsdo.org" rel="nofollow">SNOMED</a> ontology
- is of key importance in <a href="#healthcare" title="">
- healthcare</a>. SNOMED CT allows concepts with more than one parent
+ is of key importance in user story,<a>Healthcare</a>. SNOMED CT allows concepts with more than one parent
that don't fall into a lattice. In the example below, the same
concept may fall under two different parent concepts. The example
uses skos:narrowerTransitive to elide intervening concepts.
@@ -1266,7 +1249,7 @@
</section>
<section>
- <h2 id="uc-filter_resource_description">UC7: Filter resource description</h2>
+ <h2 id="uc7">UC7: Filter resource description</h2>
<p>This use case extends the normal behaviour of retrieving an
RDF description of a resource, by dynamically excluding specific
(membership) properties. For containers, it is often desirable to
@@ -1277,8 +1260,7 @@
<h3 id="scen-retrieve_collection-level_description">Primary scenario: retrieve
collection-level description</h3>
<p>
- This scenario, based on <a href="#library-linked-data" title="">
- Library Linked Data</a>, uses the Dublin Core Metadata Initiative <a
+ This scenario, based on <a>Library Linked Data</a>, uses the Dublin Core Metadata Initiative <a
href="http://dublincore.org/groups/collections/collection-application-profile/"
title="http://dublincore.org/groups/collections/collection-application-profile/"
rel="nofollow">Collection-Level</a> description. A collection can
@@ -1308,8 +1290,7 @@
<h3 id="scen-retrieve_item-level_description_of_a_collection">Alternative scenario: retrieve
item-level description of a collection</h3>
<p>
- This use case scenario, also based on <a
- href="#story-lld" title=""> Library Linked Data</a>,
+ This use case scenario, also based on <a>Library Linked Data</a>,
focuses on obtaining an item-level description of the resources
aggregated by a collection. The simplest scenario is where the
members of a collection are returned within a single
@@ -1345,7 +1326,7 @@
</section>
<section>
- <h2 id="uc-pagination">UC8: Retrieve a large resource description in multiple parts</h2>
+ <h2 id="uc8">UC8: Retrieve a large resource description in multiple parts</h2>
<p>This use case addresses a problem with the “resource-centric” approach to interacting with RDF data. The problem is that some resources participate in a very large number of triples, and therefore a “resource-centric” granularity leads to resource descriptions that are too large to be practically processed in a single HTTP request. This use case applies to all resources, not just containers.</p>
@@ -1359,7 +1340,7 @@
<section>
<h3 id="scen-access_media_resources">Primary scenario: large numbers of contacts</h3>
-<p>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.
+<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 should be no presumption that the LDP specification will recommend the use of this vocabulary to support this use case.</p>
@@ -1389,7 +1370,7 @@
</section>
<section>
- <h2 id="uc-manage_media_resources">UC9: Manage media resources</h2>
+ <h2 id="uc9">UC9: Manage media resources</h2>
<p>It should be possible to easily add non-RDF media resources
to containers that accept them. Media resources may be updated and
removed during the lifecycle of the container.</p>
@@ -1398,9 +1379,7 @@
<h3 id="scen-access_media_resources">Primary scenario: access media
resources</h3>
<p>
- From the User Story <a
- href="#sharing-binary-resources-and-metadata" title="">
- Sharing Binary Resources and Metadata</a> it should be possible to
+ From the User Story <a>Sharing Binary Resources and Metadata</a> it should be possible to
easily add non-RDF resources to containers that accept them.
Clients submit a non-RDF representation to a container in a media
type accepted by that container. The container creates a URI to
@@ -1454,81 +1433,67 @@
<section>
<h2 id="reqs-functional">Functional Requirements</h2>
<dl>
- <dt><dfn>F1</dfn>:</dt>
- <dd>Create Containers, from <a href="#uc-manage_containers"
- title="">UC1: Manage containers</a>
- </dd>
- <dt><dfn>F2</dfn>:</dt>
- <dd>Creation of nested containers, from <a
- href="#uc-manage_containers" title="">UC1: Manage
- containers</a>
- </dd>
- <dt><dfn>F3</dfn>:</dt>
- <dd>Creation of resources (within a container), from <a
- href="#uc-manage_resources" title="">Use Case: Manage resources</a>
- </dd>
- <dt><dfn>F4</dfn>:</dt>
- <dd>Deletion of resources, from <a
- href="#uc-manage_resources" title="">Use Case: Manage resources</a>
- </dd>
- <dt><dfn>F5</dfn>:</dt>
- <dd>Moving contained resources, from <a
- href="#uc-manage_resources" title="">Use Case: Manage resources</a>
- </dd>
- <dt><dfn>F6</dfn>:</dt>
- <dd>Retrieve resource description, from <a
- href="#uc-retrieve_resource_description" title="">Use Case:
- Retrieve resource description</a>
+ <dt><dfn>F1.1</dfn>:</dt>
+ <dd>Create Containers, from <a href="#uc1" title="">UC1: Manage containers</a>
</dd>
- <dt><dfn>F7</dfn>:</dt>
- <dd>Retrieve description of a non-document resource, from <a
- href="#uc-retrieve_resource_description" title="">Use Case:
- Retrieve resource description</a>
+ <dt><dfn>F1.2</dfn>:</dt>
+ <dd>Creation of nested containers, from <a href="#uc1" title="">UC1: Manage containers</a>
</dd>
- <dt><dfn>F8</dfn>:</dt>
+ <dt><dfn>F2.1</dfn>:</dt>
+ <dd>Creation of resources (within a container), from <a
+ href="#uc2" title="">UC2: Manage resources</a>
+ </dd>
+ <dt><dfn>F2.2/dfn>:</dt>
+ <dd>Deletion of resources, from <a
+ href="#uc2" title="">UC2: Manage resources</a>
+ </dd>
+ <dt><dfn>F2.3</dfn>:</dt>
+ <dd>Moving contained resources, from <a
+ href="#uc2" title="">UC2: Manage resources</a>
+ </dd>
+ <dt><dfn>F3.1</dfn>:</dt>
+ <dd>Retrieve resource description, from <a
+ href="#uc3" title="">UC3: Retrieve resource description</a>
+ </dd>
+ <dt><dfn>F3.2</dfn>:</dt>
+ <dd>Retrieve description of a non-document resource, from <a
+ href="#uc3" title="">UC3: Retrieve resource description</a>
+ </dd>
+ <dt><dfn>F4.1</dfn>:</dt>
<dd>Enrichment (substituting update of existing resource),
- from <a href="#uc-update_existing" title="">Use Case:
- Update existing resource</a>
+ from <a href="#uc4" title="">UC4: Update existing resource</a>
</dd>
- <dt><dfn>F9</dfn>:</dt>
+ <dt><dfn>F4.2</dfn>:</dt>
<dd>Selective update of a resource, from <a
- href="#uc-update_existing" title="">Use Case: Update
- existing resource</a>
- </dd>
- <dt><dfn>F10</dfn>:</dt>
- <dd>Determine if a resource has changed, from <a
- href="#uc-has_resource_changed" title="">Use Case:
- Determine if a resource has changed</a>
+ href="#uc4" title="">UC4: Update existing resource</a>
</dd>
- <dt><dfn>F11</dfn>:</dt>
+ <dt><dfn>F5.1</dfn>:</dt>
+ <dd>Determine if a resource has changed, from <a
+ href="#uc5" title="">UC5: Determine if a resource has changed</a>
+ </dd>
+ <dt><dfn>F6.1</dfn>:</dt>
<dd>Add a resource to a collection, from <a
- href="#uc-aggregate_resources" title="">Use Case: Aggregate
- resources</a>
+ href="#uc6" title="">UC6: Aggregate resources</a>
</dd>
- <dt><dfn>F12</dfn>:</dt>
+ <dt><dfn>F6.2</dfn>:</dt>
<dd>Add a resource to multiple collections, from <a
- href="#uc-aggregate_resources" title="">Use Case: Aggregate
- resources</a>
+ href="#uc6" title="">UC6: Aggregate resources</a>
</dd>
<dt><dfn>F13</dfn>:</dt>
<dd>Retrieve collection-level description, from <a
- href="#uc-filter_resource_description" title="">Use Case:
- Filter resource description</a>
- </dd>
- <dt><dfn>F14</dfn>:</dt>
- <dd>Retrieve item-level description of a collection, from <a
- href="#uc-filter_resource_description" title="">Use Case:
- Filter resource description</a>
+ href="#uc7" title="">UC7: Filter resource description</a>
</dd>
- <dt><dfn>F15</dfn>:</dt>
+ <dt><dfn>F7.1</dfn>:</dt>
+ <dd>Retrieve item-level description of a collection, from <a
+ href="#uc7" title="">UC7: Filter resource description</a>
+ </dd>
+ <dt><dfn>F9.1</dfn>:</dt>
<dd>Access media resources, from <a
- href="#uc-manage_media_resources" title="">Use Case: Manage
- media resources</a>
+ href="#uc9" title="">UC9: Manage media resources</a>
</dd>
- <dt><dfn>F16</dfn>:</dt>
+ <dt><dfn>F9.2</dfn>:</dt>
<dd>Media-resource attachments, from <a
- href="#uc-manage_media_resources" title="">Use Case: Manage
- media resources</a>
+ href="#uc9" title="">UC9: Manage media resources</a>
</dd>
</dl>
</section>
@@ -1536,46 +1501,41 @@
<section>
<h2 id="reqs-non-functional">Non-Functional Requirements</h2>
<dl>
- <dt><dfn>NF1</dfn>:</dt>
+ <dt><dfn>NF1.1</dfn>:</dt>
<dd>Provide access guidance to resources, from <a
- href="#uc-manage_containers" title="">UC1: Manage containers</a>
- </dd>
- <dt><dfn>NF2</dfn>:</dt>
- <dd>Non-duplication of resources, from <a
- href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+ href="#uc1" title="">UC1: Manage containers</a>
</dd>
- <dt><dfn>NF3</dfn>:</dt>
- <dd>Distribution of resources, from <a
- href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+ <dt><dfn>NF2.1</dfn>:</dt>
+ <dd>Non-duplication of resources, from <a
+ href="#uc2" title="">UC2: Manage resources</a>
</dd>
- <dt><dfn>NF4</dfn>:</dt>
+ <dt><dfn>NF2.2</dfn>:</dt>
+ <dd>Distribution of resources, from <a
+ href="#uc2" title="">UC2: Manage resources</a>
+ </dd>
+ <dt><dfn>NF2.3</dfn>:</dt>
<dd>Consistent, global naming, from <a
- href="#uc-manage_resources" title="">Use Case: Manage resources</a>
+ href="#uc2" title="">UC2: Manage resources</a>
</dd>
- <dt><dfn>NF5</dfn>:</dt>
+ <dt><dfn>NF3.1</dfn>:</dt>
<dd>Use standard vocabularies as appropriate, from <a
- href="#uc-retrieve_resource_description" title="">Use Case:
- Retrieve resource description</a>
+ href="#uc3" title="">UC3: Retrieve resource description</a>
</dd>
- <dt><dfn>NF6</dfn>:</dt>
+ <dt><dfn>NF3.2</dfn>:</dt>
<dd>Scalable linking model, from <a
- href="#uc-retrieve_resource_description" title="">Use Case:
- Retrieve resource description</a>
+ href="#uc3" title="">UC3: Retrieve resource description</a>
</dd>
- <dt><dfn>NF7</dfn>:</dt>
+ <dt><dfn>NF4.1</dfn>:</dt>
<dd>Unrestricted vocabulary, from <a
- href="#uc-update_existing" title="">Use Case: Update
- existing resource</a>
+ href="#uc4" title="">UC4: Update existing resource</a>
</dd>
- <dt><dfn>NF8</dfn>:</dt>
+ <dt><dfn>NF6.1</dfn>:</dt>
<dd>Resource descriptions are a "mix of simple data and
- collections", from <a href="#uc-aggregate_resources" title="">Use Case:
- Aggregate resources</a>
+ collections", from <a href="#uc6" title="">UC6: Aggregate resources</a>
</dd>
- <dt><dfn>NF9</dfn>:</dt>
+ <dt><dfn>NF6.2</dfn>:</dt>
<dd>Relative URIs enabling sharing of collections, from <a
- href="#uc-aggregate_resources" title="">Use Case: Aggregate
- resources</a>
+ href="#uc6" title="">UC6: Aggregate resources</a>
</dd>
</dl>
</section>
@@ -1588,13 +1548,13 @@
Roger Menday, Eric Prud'hommeaux, Steve Speicher, John Arwe, Kevin Page.</p>
</section>
-<section class='appendix informative' id="history">
+<!--section class='appendix informative' id="history">
<h1>Change History</h1>
<ul>
<li>2012-12-14 - Initial ReSpec'ing framework for <a href="http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements">Workgroup working wiki document</a> (SS)</li>
<li>2012-12-16 - Pulled in and ReSpec'd content from <a href="http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements">Workgroup working wiki document</a> (SS)</li>
<li>2012-12-16 - Fixed cross section links and initial pass at biblio refs (SS)</li>
-</ul></section>
+</ul></section-->
</body>
</html>