UC1 edits
authorsteve.battle <steve.battle@sysemia.co.uk>
Thu, 22 Aug 2013 12:12:11 +0100
changeset 288 26b12ae1c151
parent 287 05f4b4e8ea88
child 289 b56b6052323d
UC1 edits
ldp-ucr.html
--- a/ldp-ucr.html	Thu Aug 22 11:24:19 2013 +0100
+++ b/ldp-ucr.html	Thu Aug 22 12:12:11 2013 +0100
@@ -241,8 +241,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-tracking_relationships">Keeping Track of Personal and
-			Business Relationships</h2>
+	<h2 id="story-tracking_relationships"><dfn>Keeping Track of Personal and Business Relationships</dfn></h2>
 	<p>In our daily lives, we deal with many different
 		organizations in many different relationships, and they each have
 		data about us. However, it is unlikely that any one organization
@@ -276,7 +275,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-oslc">System and Software Development Tool Integration</h2>
+	<h2 id="story-oslc"><dfn>System and Software Development Tool Integration</dfn></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 +321,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-lld">Library Linked Data</h2>
+	<h2 id="story-lld"><dfn>Library Linked Data</dfn></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 +383,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-meter_monitoring">Municipality Operational Monitoring</h2>
+	<h2 id="story-meter_monitoring"><dfn>Municipality Operational Monitoring</dfn></h2>
 	<p>
 		Across various cities, towns, counties, and various municipalities
 		there is a growing number of services managed and run by
@@ -404,7 +403,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-healthcare">Healthcare</h2>
+	<h2 id="story-healthcare"><dfn>Healthcare</dfn></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 +429,7 @@
 	</section>	
 	
 	<section>
-	<h2 id="story-media">Metadata Enrichment in Broadcasting</h2>
+	<h2 id="story-media"><dfn>Metadata Enrichment in Broadcasting</dfn></h2>
 	<p>
 		There are many different use cases when broadcasters show interest
 		in metadata <a href="#uc-update_existing" title="">
@@ -456,7 +455,7 @@
 	</section>
 		
 	<section>
-	<h2 id="story-mashup">Aggregation and Mashups of Infrastructure Data</h2>
+	<h2 id="story-mashup"><dfn>Aggregation and Mashups of Infrastructure Data</dfn></h2>
 	<p>
 		For infrastructure management (such as storage systems, virtual
 		machine environments, and similar IaaS and PaaS concepts), it is
@@ -491,7 +490,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"><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/"
@@ -517,7 +516,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-binary_and_metadata">Sharing Binary Resources and Metadata</h2>
+	<h2 id="story-binary_and_metadata"><dfn>Sharing Binary Resources and Metadata</dfn></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 +541,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-data_catalogs">Data Catalogs</h2>
+	<h2 id="story-data_catalogs"><dfn>Data Catalogs</dfn></h2>
 	<p>
 		The <em>Asset Description Metadata Schema</em> (<a
 			href="http://joinup.ec.europa.eu/asset/adms/home"
@@ -575,7 +574,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-constrained_devices">Constrained Devices and Networks</h2>
+	<h2 id="story-constrained_devices"><dfn>Constrained Devices and Networks</dfn></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 +612,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-process_of_science">Services Supporting the Process of Science</h2>
+	<h2 id="story-process_of_science"><dfn>Services Supporting the Process of Science</dfn></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 +641,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-project_data">Project Membership Information</h2>
+	<h2 id="story-project_data"><dfn>Project Membership Information</dfn></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 +672,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-cloud">Cloud Infrastructure Management</h2>
+	<h2 id="story-cloud"><dfn>Cloud Infrastructure Management</dfn></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,
@@ -736,24 +735,20 @@
 	<section>
 	<h3 id="scen-create_container">Primary scenario: create a container</h3>
 	<p>
-		Create a new container resource within the LDP server. In <a
-			href="#story-process_of_science" title="">Services
-			supporting the process of science</a>, <a
-			href="http://wf4ever.github.com/ro-primer/" 
-			title="http://wf4ever.github.com/ro-primer/" rel="nofollow">Research
+		Create a new container resource within the LDP server. In <a>Services Supporting the Process of Science</a>, 
+			<a
+			href="http://www.wf4ever-project.org/" 
+			title="http://www.wf4ever-project.org/" rel="nofollow">Research
 			Objects</a> are semantically rich aggregations of resources that
 		bring together data, methods and people in scientific
 		investigations. A basic workflow research object will be created
 		to aggregate <a href="http://ceur-ws.org/Vol-903/paper-01.pdf"
 			title="http://ceur-ws.org/Vol-903/paper-01.pdf" rel="nofollow">scientific
-			workflows</a> and the artefacts that result from this workflow. 
+			workflows</a> and the artefacts that result from this workflow. 		
+		These artefacts will be added to the research object throughout the project lifecycle of the project.
 	</p>
-	<p>		
-		<a href="http://www.wf4ever-project.org/">Wf4Ever</a> is concerned with the challenges associated with the preservation of scientific experiments in data-intensive science.
-		In the example below, a
-		research object is defined as a composition of
-		workflows, datasets, and results which will be added
-		throughout the lifecycle of a project.
+	<p>
+		The RDF description below captures the initial state of the research object. For the purposes of the example, we have included the time of creation. It is a linked data resource addressed via URL.
 	</p>
 	<pre class='example'>
 @prefix ro:  &lt;http://purl.org/wf4ever/ro#&gt; .
@@ -767,8 +762,7 @@
 	</section>
 	
 	<section>
-	<h3 id="scen-create_a_nested_container">Alternative scenario: create a
-			nested container</h3>
+	<h3 id="scen-create_a_nested_container">Alternative scenario: create a nested container</h3>
 	<p>
 		The motivation for nested containers comes from the <a
 			href="#story-oslc" title="Story Tool Integration">