Revisions to user-stories UC&R
authorsteve.battle <>
Fri, 26 Jul 2013 15:56:53 +0100
changeset 241 6cbfa4e97a0d
parent 240 476cbb59e573
child 243 c42af18fe1c1
child 265 b67e11794076
Revisions to user-stories UC&R
--- a/ldp-ucr.html	Fri Jul 26 13:31:55 2013 +0100
+++ b/ldp-ucr.html	Fri Jul 26 15:56:53 2013 +0100
@@ -154,7 +154,9 @@
 			capture statements about system requirements written from a user
 			or application perspective. They are typically lightweight and
 			informal and can run from one line to a paragraph or two
-			(sometimes described as an 'epic') [[COHN-2004]]. Analysis of each user story will reveal a
+			(sometimes described as an 'epic') [[COHN-2004]]. 
+			This document redacts a number of user stories around the theme of read/writeable linked data.
+			Analysis of each user story reveals a
 			number of (functional) use cases and other non-functional
 			requirements. See <i>Device API Access Control Use Cases and Requirements</i> [[DAP-REQS]] for a good example
 			of user stories and their analysis.</li>
@@ -263,8 +265,6 @@
 		consistent application interface that they all supported? 
-		Our set of links would probably be a <a
-			href="#uc-aggregate_resources" title="">simple collection</a>.
 		The information held by any single organization might be a mix of
 		simple data and <a href="#uc-aggregate_resources" title="">collections
 			of other data</a>, for example, a bank account balance and a
@@ -325,7 +325,7 @@
 	<h2 id="story-lld">Library Linked Data</h2>
 		The W3C Library Linked Data Working Group has a number of use
-		cases cited in their Use Case Report [[LLD-UC]]. These referenced use cases focus on the
+		cases cited in their <i>Use Case Report</i> [[LLD-UC]]. These referenced use cases focus on the
 		need to extract and correlate library data from disparate sources.
 		Variants of these use cases that can provide consistent formats,
 		as well as ways to improve or update the data, would enable
@@ -554,8 +554,7 @@
 		repositories and efficiently retrieving <a
 			href="#uc-has_resource_changed" title="">
 			updated content</a> without having to retrieve the whole content.
-		Hence, we chose to build the integration solution capitalizing on
-		the Data Warehousing integration approach. This allows us to cope
+		The Data Warehousing integration approach allows us to cope
 		with heterogeneity of sources technologies and to benefit from the
 		optimized performance it offers, given that individual
 		repositories do not usually change frequently. With Data
@@ -573,11 +572,6 @@
 		compatible manner. ADMS provides the necessary data model to
 		enable meaningful exchange of data. However, this leaves the
 		challenge of efficient access to the data not fully addressed.</p>
-	<p>
-		Related: <a href=""
-			title=""
-			rel="nofollow">Data Catalog Schema and Protocol</a>
-	</p>