re-structuring, etc ...
authorrmenday
Mon, 12 Aug 2013 10:51:37 +0100
changeset 270 7295cd361760
parent 269 47d11ac90954 (current diff)
parent 268 1bea5bc613b0 (diff)
child 271 4bdbd8e18c5b
re-structuring, etc ...
ldp-primer/context.json
--- a/ldp-ucr.html	Mon Aug 12 10:48:02 2013 +0100
+++ b/ldp-ucr.html	Mon Aug 12 10:51:37 2013 +0100
@@ -613,8 +613,7 @@
 	</section>
 	
 	<section>
-	<h2 id="story-process_of_science">Services Supporting the Process
-			of Science</h2>
+	<h2 id="story-process_of_science">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
@@ -624,36 +623,22 @@
 		publishing of experimental data "beyond the PDF"), and re-use.</p>
 	<ul>
 		<li><a href="#uc-aggregate_resources" title="">Aggregations</a>,
-			specifically <i>Research Objects (ROs)</i> that are exchanged
+			specifically <i>Research Objects (ROs)</i> are exchanged
 			between services and clients bringing together workflows, data
-			sets, annotations, and provenance. We use an RDF model for this.
-			While some aggregated contents are encoded using RDF and an
-			increasing number are linked data sources, others are not; while
-			some are stored locally "within" the RO, others are remote (in
-			both cases this is often due to size of the resources or access
-			policies).</li>
-		<li>Services that are distributed and linked. Some may be
-			centralising for e.g. publication, others may be local, e.g. per
-			lab. We need lightweight services that can be simply and easily
-			integrated into and scale across the wide variety of softwares
-			and data used in science: we have adopted a RESTful approach
-			where possible.
+			sets, annotations, and provenance.
+		</li>
+		<li>We need lightweight services that can be simply and easily
+			integrated into, and scale across the wide variety of softwares
+			and data used in science.
 			<ul>
-				<li>Foundation services that collect and expose ROs for
+				<li>Foundation services collect and expose ROs for
 					storage, modification, exploration, and reuse.</li>
 				<li>Services that provide added-value to ROs such as
 					seamless import/export from scientific workflow systems,
-					automated stability evaluation, or recommendation (and
-					therefore interact with the foundation services to
-					retrieve/store/modify/ROs).</li>
+					automated stability evaluation, or recommendation.</li>
 			</ul>
 		</li>
 	</ul>
-	<p>
-		seeAlso: <a href="http://www.wf4ever-project.org/"
-			title="http://www.wf4ever-project.org/"
-			rel="nofollow">Wf4Ever</a>
-	</p>
 	</section>
 	
 	<section>
@@ -765,7 +750,7 @@
 		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. The
-		research object begins life as an empty container (see below) into which
+		research object below, begins life as an empty container (see below) into which
 		workflows, datasets, results and other data will be added
 		throughout the lifecycle of the project.
 	</p>