Added user strory sequence numbering
authorsteve.battle <steve.battle@sysemia.co.uk>
Wed, 21 Aug 2013 10:32:25 +0100
changeset 276 93ecf9d15603
parent 275 f171c3c3b68f
child 277 41c69138a501
Added user strory sequence numbering
ldp-ucr.html
--- a/ldp-ucr.html	Wed Aug 21 10:19:08 2013 +0100
+++ b/ldp-ucr.html	Wed Aug 21 10:32:25 2013 +0100
@@ -195,7 +195,7 @@
 <h1 id="userstories">User Stories</h1>
 
 	<section>
-	<h2 id="story-social">Maintaining Social Contact Information</h2>
+	<h2 id="story-social">User Story 1: Maintaining Social Contact Information</h2>
 	<p>Many of us have multiple email accounts that include
 		information about the people and organizations we interact with –
 		names, email addresses, telephone numbers, instant messenger
@@ -241,7 +241,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-tracking_relationships">Keeping Track of Personal and
+	<h2 id="story-tracking_relationships">User Story 2: Keeping Track of Personal and
 			Business Relationships</h2>
 	<p>In our daily lives, we deal with many different
 		organizations in many different relationships, and they each have
@@ -276,7 +276,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-oslc">System and Software Development Tool Integration</h2>
+	<h2 id="story-oslc">User Story 3: System and Software Development Tool Integration</h2>
 	<p>System and software development tools typically come from a
 		diverse set of vendors and are built on various architectures and
 		technologies. These tools are purpose built to meet the needs for
@@ -322,7 +322,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-lld">Library Linked Data</h2>
+	<h2 id="story-lld">User Story 4: Library Linked Data</h2>
 	<p>
 		The W3C Library Linked Data Working Group has a number of use
 		cases cited in their <i>Use Case Report</i> [[LLD-UC]]. These referenced use cases focus on the
@@ -384,7 +384,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-meter_monitoring">Municipality Operational Monitoring</h2>
+	<h2 id="story-meter_monitoring">User Story 5: Municipality Operational Monitoring</h2>
 	<p>
 		Across various cities, towns, counties, and various municipalities
 		there is a growing number of services managed and run by
@@ -404,7 +404,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-healthcare">Healthcare</h2>
+	<h2 id="story-healthcare">User Story 6: Healthcare</h2>
 	<p>For physicians to analyze, diagnose, and propose treatment
 		for patients requires a vast amount of complex, changing and
 		growing knowledge. This knowledge needs to come from a number of
@@ -430,7 +430,7 @@
 	</section>	
 	
 	<section>
-	<h2 id="story-media">Metadata Enrichment in Broadcasting</h2>
+	<h2 id="story-media">User Story 7: Metadata Enrichment in Broadcasting</h2>
 	<p>
 		There are many different use cases when broadcasters show interest
 		in metadata <a href="#uc-update_existing" title="">
@@ -456,7 +456,7 @@
 	</section>
 		
 	<section>
-	<h2 id="story-mashup">Aggregation and Mashups of Infrastructure Data</h2>
+	<h2 id="story-mashup">User Story 8: Aggregation and Mashups of Infrastructure Data</h2>
 	<p>
 		For infrastructure management (such as storage systems, virtual
 		machine environments, and similar IaaS and PaaS concepts), it is
@@ -491,7 +491,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-low-end_devices">Sharing Payload of RDF Data Among Low-End Devices</h2>
+	<h2 id="story-low-end_devices">User Story 9: Sharing Payload of RDF Data Among Low-End Devices</h2>
 	<p>
 		Several projects around the idea of <a
 			href="http://worldwidesemanticweb.wordpress.com/"
@@ -517,7 +517,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-binary_and_metadata">Sharing Binary Resources and Metadata</h2>
+	<h2 id="story-binary_and_metadata">User Story 10: Sharing Binary Resources and Metadata</h2>
 	<p>When publishing datasets about stars one may want to publish
 		links to the pictures in which those stars appear, and this may
 		well require publishing the pictures themselves. Vice versa: when
@@ -542,7 +542,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-data_catalogs">Data Catalogs</h2>
+	<h2 id="story-data_catalogs">User Story 11: Data Catalogs</h2>
 	<p>
 		The <em>Asset Description Metadata Schema</em> (<a
 			href="http://joinup.ec.europa.eu/asset/adms/home"
@@ -575,7 +575,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-constrained_devices">Constrained Devices and Networks</h2>
+	<h2 id="story-constrained_devices">User Story 12: Constrained Devices and Networks</h2>
 	<p>
 		Information coming from resource constrained devices in the Web of
 		Things (<a href="http://en.wikipedia.org/wiki/Web_of_Things"
@@ -613,7 +613,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-process_of_science">Services Supporting the Process of Science</h2>
+	<h2 id="story-process_of_science">User Story 13: Services Supporting the Process of Science</h2>
 	<p>Many fields of science now include branches with in silico
 		data-intensive methods, e.g. bioinformatics, astronomy. To support
 		these new methods we look to move beyond the established platforms
@@ -642,7 +642,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-project_data">Project Membership Information: Information Evolution</h2>
+	<h2 id="story-project_data">User Story 14: Project Membership Information: Information Evolution</h2>
 	<p>Information about people and projects changes as roles
 		change, as organisations change and as contact details change.
 		Finding the current state of a project is important in enabling
@@ -673,7 +673,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-cloud">Cloud Infrastructure Management</h2>
+	<h2 id="story-cloud">User Story 15: Cloud Infrastructure Management</h2>
 	<p>Cloud operators offer API support to provide customers with
 		remote access for the management of Cloud infrastructure (IaaS).
 		Infrastructure consists of Systems, Computers, Networks, Discs,
@@ -1357,7 +1357,7 @@
 	</section>
 	
 	<section>
-		<h2 id="uc-pagination">Use case: Retrieve a large resource description in multiple parts</h2>
+		<h2 id="uc-pagination">Use case 8: 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>
 
@@ -1401,7 +1401,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-manage_media_resources">Use Case 8: Manage media resources</h2>
+	<h2 id="uc-manage_media_resources">Use Case 9: 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>