--- a/ldp-ucr.html Fri Aug 23 11:10:51 2013 +0100
+++ b/ldp-ucr.html Fri Aug 23 11:55:12 2013 +0100
@@ -268,7 +268,7 @@
simple data and <a href="#uc-aggregate_resources" 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_container"
+ <a href="#scen-create_a_nested_composition"
title="">a collection of accounts for each member of its collection
of customers</a>.
</p>
@@ -505,7 +505,7 @@
networks).
</p>
<p>The transfer of an arbitrary payload of RDF data could be
- implemented through the container mechanism, adding and removing
+ implemented through a container mechanism, adding and removing
sets of RDF triples to it. Currently, the
"SemanticXO" project uses named graphs and the graph store protocol to
create/delete/copy graphs across the nodes but this (almost)
@@ -715,16 +715,15 @@
not be interpreted normatively.</p>
<section id="uc1">
- <h2><dfn>UC1</dfn>: Manage containers</h2>
+ <h2><dfn>UC1</dfn>: Compose resources</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
- context of an application. Resources grouped together within the
- same container would typically belong to the same application. A
- container is identified by a URI so is a resource in its own
- right. The properties of a container may also represent the <i>affordances</i>
- of that container, enabling clients to determine what other
- operations they can do on that container. These operations may
+ 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>
+ 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
invoked by exchanging RDF documents.
</p>
@@ -795,7 +794,7 @@
</section>
<section id="uc2">
- <h2><dfn>UC2</dfn>: Manage resources</h2>
+ <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
@@ -867,8 +866,7 @@
</section>
<section>
- <h3 id="scen-delete_resource">Alternative scenario: delete
- resource</h3>
+ <h3 id="scen-delete_resource">Alternative scenario: delete resource</h3>
<p>
Delete a resource and all it's properties. If the resource resides
within a container it will be removed from that container, however
@@ -883,8 +881,7 @@
</section>
<section>
- <h3 id="scen-moving_contained_resources">Alternative scenario: moving
- contained resources</h3>
+ <h3 id="scen-moving_contained_resources">Alternative scenario: moving contained resources</h3>
<p>
Resources may have value beyond the life of their membership
in a container. This implies methods to add references to revise
@@ -1434,52 +1431,52 @@
<h2 id="reqs-functional">Functional Requirements</h2>
<dl>
<dt><dfn>F1.1</dfn>:</dt>
- <dd>Create Containers, from <a>UC1</a>
+ <dd>The system shall provide the ability to create containers, from <a>UC1</a>.
</dd>
<dt><dfn>F1.2</dfn>:</dt>
- <dd>Creation of nested containers, from <a>UC1</a>
+ <dd>The system shall provide the ability to create nested containers, from <a>UC1</a>.
</dd>
<dt><dfn>F2.1</dfn>:</dt>
- <dd>Creation of resources (within a container), from <a>UC2</a>
+ <dd>The system shall provide the ability to compose resources within a container, from <a>UC2</a>.
</dd>
<dt><dfn>F2.2</dfn>:</dt>
- <dd>Deletion of resources, from <a>UC2</a>
+ <dd>The system shall provide the ability to delete resources, from <a>UC2</a>.
</dd>
<dt><dfn>F2.3</dfn>:</dt>
- <dd>Moving contained resources, from <a>UC2</a>
+ <dd><strike>The system shall provide the ability to move resources between containers, from <a>UC2</a></strike>.
</dd>
<dt><dfn>F3.1</dfn>:</dt>
- <dd>Retrieve resource description, from <a>UC3</a>
+ <dd>The system shall provide the ability to retrieve resource descriptions, from <a>UC3</a>.
</dd>
<dt><dfn>F3.2</dfn>:</dt>
- <dd>Retrieve description of a non-document resource, from <a>UC3</a>
+ <dd><strike>The system shall provide the ability to retrieve the description of a non-document resource, from <a>UC3</a></strike>.
</dd>
<dt><dfn>F4.1</dfn>:</dt>
- <dd>Enrichment (substituting update of existing resource), from <a>UC4</a>
+ <dd>The system shall provide the ability to update an existing resource by substitution, from <a>UC4</a>.
</dd>
<dt><dfn>F4.2</dfn>:</dt>
- <dd>Selective update of a resource, from <a>UC4</a>
+ <dd>The system shall provide the ability to perform a selective update of a resource, from <a>UC4</a>.
</dd>
<dt><dfn>F5.1</dfn>:</dt>
- <dd>Determine if a resource has changed, from <a>UC5</a>
+ <dd>The system shall provide the ability to determine if a resource has changed, from <a>UC5</a>.
</dd>
<dt><dfn>F6.1</dfn>:</dt>
- <dd>Add a resource to a collection, from <a>UC6</a>
+ <dd>The system shall provide the ability to aggregate resources, from <a>UC6</a>.
</dd>
<dt><dfn>F6.2</dfn>:</dt>
- <dd>Add a resource to multiple collections, from <a>UC6</a>
- </dd>
- <dt><dfn>F13</dfn>:</dt>
- <dd>Retrieve collection-level description, from <a>UC7</a>
+ <dd>The system shall support the addition of a resource to multiple aggregations, from <a>UC6</a>.
</dd>
<dt><dfn>F7.1</dfn>:</dt>
- <dd>Retrieve item-level description of a collection, from <a>UC7</a>
+ <dd>The system shall provide the ability to retrieve a collection-level description of a composition, from <a>UC7</a>.
+ </dd>
+ <dt><dfn>F7.2</dfn>:</dt>
+ <dd>The system shall provide the ability to retrieve an item-level description of a composition or aggregation, from <a>UC7</a>.
</dd>
<dt><dfn>F9.1</dfn>:</dt>
- <dd>Access media resources, from <a>UC9</a>
+ <dd>The system shall provide the ability to store and access media resources, from <a>UC9</a>
</dd>
<dt><dfn>F9.2</dfn>:</dt>
- <dd>Media-resource attachments, from <a>UC9</a>
+ <dd><strike>The system shall provide the ability to add media-resource attachments, from <a>UC9</a>.</strike>
</dd>
</dl>
</section>
@@ -1488,40 +1485,31 @@
<h2 id="reqs-non-functional">Non-Functional Requirements</h2>
<dl>
<dt><dfn>NF1.1</dfn>:</dt>
- <dd>Provide access guidance to resources, from <a
- href="#uc1" title="">UC1: Manage containers</a>
+ <dd>The system shall provide access guidance to resources, from <a>UC1</a>.
</dd>
<dt><dfn>NF2.1</dfn>:</dt>
- <dd>Non-duplication of resources, from <a
- href="#uc2" title="">UC2: Manage resources</a>
+ <dd>The system shall encourage non-duplication of resources, from <a>UC2</a>.
</dd>
<dt><dfn>NF2.2</dfn>:</dt>
- <dd>Distribution of resources, from <a
- href="#uc2" title="">UC2: Manage resources</a>
+ <dd>The system shall support distribution of resources, from <a>UC2</a>.
</dd>
<dt><dfn>NF2.3</dfn>:</dt>
- <dd>Consistent, global naming, from <a
- href="#uc2" title="">UC2: Manage resources</a>
+ <dd>The system shall support consistent, global naming, from <a>UC2</a>.
</dd>
<dt><dfn>NF3.1</dfn>:</dt>
- <dd>Use standard vocabularies as appropriate, from <a
- href="#uc3" title="">UC3: Retrieve resource description</a>
+ <dd>The system shall support the use of standard vocabularies where appropriate, from <a>UC3</a>.
</dd>
<dt><dfn>NF3.2</dfn>:</dt>
- <dd>Scalable linking model, from <a
- href="#uc3" title="">UC3: Retrieve resource description</a>
+ <dd>The system shall provide a scalable linking model, from <a>UC3</a>.
</dd>
<dt><dfn>NF4.1</dfn>:</dt>
- <dd>Unrestricted vocabulary, from <a
- href="#uc4" title="">UC4: Update existing resource</a>
+ <dd>The system shall permit unrestricted vocabulary, from <a>UC4</a>.
</dd>
<dt><dfn>NF6.1</dfn>:</dt>
- <dd>Resource descriptions are a "mix of simple data and
- collections", from <a href="#uc6" title="">UC6: Aggregate resources</a>
+ <dd>The system shall allow resource descriptions that are a "mix of simple data and collections", from <a>UC6</a>.
</dd>
<dt><dfn>NF6.2</dfn>:</dt>
- <dd>Relative URIs enabling sharing of collections, from <a
- href="#uc6" title="">UC6: Aggregate resources</a>
+ <dd>The system shall support relative URIs enabling sharing of collections, from <a>UC6</a>.
</dd>
</dl>
</section>