section 3
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 19 Sep 2011 09:23:10 +0100
changeset 314 0d46e292281f
parent 313 928d5d106ad8
child 315 e0b26e0802e6
section 3
model/ProvenanceModel.html
--- a/model/ProvenanceModel.html	Mon Sep 19 09:12:29 2011 +0100
+++ b/model/ProvenanceModel.html	Mon Sep 19 09:23:10 2011 +0100
@@ -285,7 +285,7 @@
     <section> 
 <h2>PROV-DM Overview </h2>
 
-<div class='issue'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
+
 
 <!--
 <div class='note'>
@@ -304,12 +304,12 @@
   <img src="overview.png" align="center"/>
 
 
-<p/>The model includes the following fundamental entity types:
+<p/>The model includes the following fundamental types:
 <ul>
   <li><strong>Entities</strong>: these are representations of <em>characterized things</em>, as defined informally above.</li> The specific nature of an entity is specified by means of a set of <strong>characterizing attributes</strong>. The
       <strong>wasComplementOf</strong> relationship is used to denote that two entities <em>complement</em> each other, in the sense that they each represent a partial, but mutually compatible characterization of the same thing.
   
-  <li><strong>Process Execution </strong>: these represent activities that have an effect on entities, namely they either <em>generate</em> or <em>use</em> one or more entites. Use and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an Entity in a Process Execution.  Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on entities.
+  <li><strong>Process Execution </strong>: these represent activities that have an effect on entities, namely they either <em>generate</em> or <em>use</em> one or more entities. Use and generation are modelled by means of the <strong>used</strong> and the <strong>wasGeneratedBy</strong> relationships. Additionally, one can use the <strong>hadParticipant</strong> relation to indicate participation of an Entity in a Process Execution.  Activities may include not only computations, but also any other type of activity that can be described in terms of their effect on entities.
 Note that multiple Process Executions may <em>use</em> the same entity, and each may use multiple entities. Finally, entities can be derived from other entities, and this is specified using the <strong>wasDerivedFrom</strong> relation.
   
   <li><strong>Agents</strong>: these represent particular entities that can be associated to activities, meaning they are capable of controlling Process Executions.
@@ -323,7 +323,10 @@
     
 Attributes, qualifiers,  and annotation are the main <strong>extensibility points</strong> in the model: individual interest groups  are expected to extend PROV-DM by introducing new sets of attributes, qualifiers, and annotations as needed to address applications-specific provenance modelling requirements. 
     
-
+<div class='note'>Note time is not explicit in the figure.</div>
+<div class='note'>Potentially there is terminology misalignment with section 5. For instance, here the text says entities are representations of characterized things, whereas section 5 says entity expressions are representations of characterized things.</div>
+
+<div class='pending'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
     </section>