--- a/model/ProvenanceModel.html Wed Oct 05 15:18:59 2011 +0100
+++ b/model/ProvenanceModel.html Wed Oct 05 15:21:40 2011 +0100
@@ -301,26 +301,27 @@
<p>
The following diagram provides a high level overview of the PROV-DM. Examples of a set of provenance assertions that conform to this schema are provided in the next section (note: cardinality constraints on the associations are 0..* unless otherwise stated)</p>
- <img src="overview.png" style="align=center;"/>
-
-<p/>The model includes the following fundamental types:
+ <img src="overview.png" style="align=center;" alt="PROV-DM overview"/>
+
+<p>The model includes the following fundamental types:
<ul>
- <li>An instance of an <strong>Entity</strong> is a representation of a <em>characterized thing</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>An instance of an <B>Entity</B> is a representation of a <em>characterized thing</em>, as defined informally above.</li> The specific nature of an entity is specified by means of a set of <B>characterizing attributes</B>. The
+ <B>wasComplementOf</B> 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>
- <li>An instance of a <strong>Process Execution</strong> represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</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>An instance of a <B>Process Execution</B> represents an activity that has an effect on entities, namely it either <em>generates</em> or <em>uses</em> one or more entities. Use and generation are modelled by means of the <B>used</B> and the <B>wasGeneratedBy</B> relationships. Additionally, one can use the <B>hadParticipant</B> 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 <B>wasDerivedFrom</B> relation.</li>
- <li>An instance of <strong>Agent</strong> represent a particular entity that can be associated to activities, meaning it is capable of controlling Process Executions.
- Agents have a rather generic connotation: their association with an activity, represented by the <strong>controlledBy</strong> relationship, can take up various meanings (attribution, responsibility, supervision, management, etc.), which are not individually specified in the model.
+ <li>An instance of <B>Agent</B> represent a particular entity that can be associated to activities, meaning it is capable of controlling Process Executions.
+ Agents have a rather generic connotation: their association with an activity, represented by the <B>controlledBy</B> relationship, can take up various meanings (attribution, responsibility, supervision, management, etc.), which are not individually specified in the model.</li>
</ul>
-
-The model includes two additional types: <strong>qualifiers</strong> and <strong>annotations</strong>. These are both structured as sets of attribute-value pairs.
- <ul><li> Qualifiers can be associated to relations, namely <strong>use</strong> and <strong>wasGeneratedBy</strong>, in order to further characterise their nature. <strong>Role</strong> is a standard qualifier.
-<li> Annotations are used to provide additional, "free-form" information regarding <strong>any</strong> identifiable construct of the model, with no prescribed meaning. The difference between attributes and annotations is further clarified <a href="#expression-annotation">here</a>.
+</p>
+
+The model includes two additional types: <B>qualifiers</B> and <B>annotations</B>. These are both structured as sets of attribute-value pairs.
+ <ul><li> Qualifiers can be associated to relations, namely <B>use</B> and <B>wasGeneratedBy</B>, in order to further characterise their nature. <B>Role</B> is a standard qualifier.</li>
+<li> Annotations are used to provide additional, "free-form" information regarding <B>any</B> identifiable construct of the model, with no prescribed meaning. The difference between attributes and annotations is further clarified <a href="#expression-annotation">here</a>. </li>
</ul>
-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.
+Attributes, qualifiers, and annotation are the main <B>extensibility points</B> 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='pending'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
@@ -445,7 +446,7 @@
<p>
-Expressions of type <strong>UsedExpressions</strong> (described in <a href="#expression-Use">Section Use</a>) represent the event by which a file is read by a process execution.
+Expressions of type <B>UsedExpressions</B> (described in <a href="#expression-Use">Section Use</a>) represent the event by which a file is read by a process execution.
Likewise, to describe the modalities according to which the various things are used by activities, a qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>) is introduced. Illustrations of such qualifiers are:
<span class="name">e1</span> is used in the context of <span class="name">pe1</span>'s <span clasfs="name">load</span> functionality; <span class="name">e2</span> is used by <span class="name">pe2</span> in the context of its attach functionality; <span class="name">e3</span> is used on the standard input by <span class="name">pe5</span>.
@@ -2170,14 +2171,14 @@
<section id="expression-Collection">
<h3>Collections</h3>
-The purpose of this section is to enable modelling of part-of relationships amongst entities. In particular, a form of <strong>collection</strong> entity type is introduced, consisting of a set of key-value pairs. Key-value pairs provide a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" in some programming languages), relational tables, ordered lists, and more.<br/>
-
-The relations introduced here are all specializations of the <a href="#expression-Derivation"><strong>wasDerivedFrom</strong></a> pe-linked derivation. They are designed to model:
+The purpose of this section is to enable modelling of part-of relationships amongst entities. In particular, a form of <B>collection</B> entity type is introduced, consisting of a set of key-value pairs. Key-value pairs provide a generic indexing structure that can be used to model commonly used data structures, including associative lists (also known as "dictionaries" in some programming languages), relational tables, ordered lists, and more.<br/>
+
+The relations introduced here are all specializations of the <a href="#expression-Derivation"><B>wasDerivedFrom</B></a> pe-linked derivation. They are designed to model:
<ul>
- <li><strong>insertion</strong>: a collection entity c' is obtained from collection entity c, by adding entity e having key k to c;
- <li><strong>removal</strong>: a collection entity c' is obtained from collection entity c, by removing entity e having key k from c;
- <li><strong>selection</strong>: an entity e was selected from collection c using key k.
+ <li><B>insertion</B>: a collection entity c' is obtained from collection entity c, by adding entity e having key k to c;
+ <li><B>removal</B>: a collection entity c' is obtained from collection entity c, by removing entity e having key k from c;
+ <li><B>selection</strong>: an entity e was selected from collection c using key k.
</ul>
A collection expression is defined as follows.