--- a/model/ProvenanceModel.html Wed Oct 05 15:21:40 2011 +0100
+++ b/model/ProvenanceModel.html Wed Oct 05 15:26:07 2011 +0100
@@ -303,25 +303,25 @@
<img src="overview.png" style="align=center;" alt="PROV-DM overview"/>
-<p>The model includes the following fundamental types:
+<p>The model includes the following fundamental types:</p>
<ul>
- <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 <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 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>
- <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>
+ <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>
+
+ <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>
</ul>
-</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>
+
+
+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>
+<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>. </li>
</ul>
-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.
+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='pending'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
@@ -356,12 +356,11 @@
</p>
<p>
-Event evt2: Bob appends (pe1) the following line to /share/crime.txt:
+Event evt2: Bob appends (pe1) the following line to /share/crime.txt:</p>
<pre>
There was a lot of crime in London last month.
</pre>
-We denote this e2.
-</p>
+<p>We denote this e2.</p>
<p>Event evt3: Charles emails (pe2) the contents of /share/crime.txt, as an
attachment, which we refer to as e4. (We specifically refer to a copy of the file that is uploaded on the mail server.)
@@ -389,7 +388,7 @@
In this section, the example is encoded according to the provenance data model (specified in section <a href="#data-model-concepts">PROV-DM: The Provenance Data Model</a>) and expressed in PROV-ASN.
<p>
-Entity Expressions (described in <a href="#expression-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entity expressions, corresponding to multiple characterizations, as per scenario. The entity expressions are identified by <span class="name">e0</span>, ..., <span class="name">e6</span>.
+Entity Expressions (described in <a href="#expression-Entity">Section Entity</a>). The file in its various forms and its copies are modelled as entity expressions, corresponding to multiple characterizations, as per scenario. The entity expressions are identified by <span class="name">e0</span>, ..., <span class="name">e6</span>.</p>
<pre>
entity(e0, [ type="File", location="/shared/crime.txt", creator="Alice" ])
entity(e1, [ type="File", location="/shared/crime.txt", creator="Alice", content="" ])
@@ -399,7 +398,7 @@
entity(e5, [ ])
entity(e6, [ type="File", location="/shared/crime.txt", creator="Alice", content="There was a lot of crime in London and New York last month.", spellchecked="yes"])
</pre>
-</p>
+
<p>These entity expression list attributes that have been given values during intervals delimited by events; such intervals are referred to as <em>characterization intervals</em>. The following table lists all entity identifiers and their corresponding characterization intervals. When the end of the characterization interval is not delimited by an event described in this scenario, it is marked by "...".
@@ -419,7 +418,7 @@
<p>
-Process Execution Expressions (described in <a href="#expression-ProcessExecution">Section Process Execution</a>) represent activities in the scenario.
+Process Execution Expressions (described in <a href="#expression-ProcessExecution">Section Process Execution</a>) represent activities in the scenario.</p>
<pre>
processExecution(pe0,create-file,t,,[])
processExecution(pe1,add-crime-in-london,t+1,,[])
@@ -428,11 +427,11 @@
processExecution(pe4,email,t+4,,[])
processExecution(pe5,spellcheck,,,[])
</pre>
-</p>
+
<p>
Generation Expressions (described in <a href="#expression-Generation">Section Generation</a>) represent the event at which a file is created in a specific form. To describe the modalities according to which the various characterized things are generated by a given activity, a qualifier (expression described in <a href="#expression-qualifier">Section Qualifier</a>) is introduced. The interpretation of qualifiers is application specific. Illustrations of such qualifiers for the scenario are: no qualifier is provided for <span class="name">e0</span>;
-<span class="name">e2</span> was generated by the editor's save function; <span class="name">e4</span> can be found on the smtp port, in the attachment section of the mail message; <span class="name">e6</span> was produced on the standard output of <span class="name">pe5</span>.
+<span class="name">e2</span> was generated by the editor's save function; <span class="name">e4</span> can be found on the smtp port, in the attachment section of the mail message; <span class="name">e6</span> was produced on the standard output of <span class="name">pe5</span>.</p>
<pre>
wasGeneratedBy(e0, pe0, qualifier())
wasGeneratedBy(e1, pe0, qualifier(fct="create"))
@@ -442,14 +441,14 @@
wasGeneratedBy(e5, pe4, qualifier(port="smtp", section="attachment"))
wasGeneratedBy(e6, pe5, qualifier(file="stdout"))
</pre>
-</p>
+
<p>
-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.
+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.
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>.
+<span class="name">e1</span> is used in the context of <span class="name">pe1</span>'s <span class="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>. </p>
<pre>
used(pe1,e1,qualifier(fct="load"))
used(pe3,e2,qualifier(fct="load"))
@@ -457,10 +456,10 @@
used(pe4,e3,qualifier(fct="attach"))
used(pe5,e3,qualifier(file="stdin"))
</pre>
-</p>
+
<p>
-Derivation Expressions (described in <a href="#expression-Derivation">Section Derivation</a>) express that an entity is derived from another. The first two are expressed in their compact version, whereas the following two are expressed in their full version, including the process execution underpinnng the derivation, and relevant qualifiers qualifying the use and generation of entities.
+Derivation Expressions (described in <a href="#expression-Derivation">Section Derivation</a>) express that an entity is derived from another. The first two are expressed in their compact version, whereas the following two are expressed in their full version, including the process execution underpinnng the derivation, and relevant qualifiers qualifying the use and generation of entities.</p>
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
@@ -478,11 +477,11 @@
wasComplementOf(e3,e0)
wasComplementOf(e6,e3)
</pre>
-</p>
+
<p>
-Agent Expressions (described at <a href="#expression-Agent">Section Agent</a>): the various users are represented as agents, themselves being a type of entity.
+Agent Expressions (described at <a href="#expression-Agent">Section Agent</a>): the various users are represented as agents, themselves being a type of entity.</p>
<pre>
entity(a1, [ type="Person", name="Alice" ])
agent(a1)
@@ -499,11 +498,11 @@
entity(a5, [ type="Person", name="Edith" ])
agent(a5)
</pre>
-</p>
+
<p>
-Control Expressions (described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agenr: are creator, author and communicator.
+Control Expressions (described in <a href="#expression-Control">Section Control</a>): the influence of an agent over a process execution is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#expression-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agenr: are creator, author and communicator.</p>
<pre>
wasControlledBy(pe0,a1, qualifier(role="creator"))
wasControlledBy(pe1,a2, qualifier(role="author"))
@@ -511,7 +510,6 @@
wasControlledBy(pe3,a4, qualifier(role="author"))
wasControlledBy(pe4,a5, qualifier(role="communicator"))
</pre>
-</p>
</section>
@@ -2171,14 +2169,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 <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:
+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:
<ul>
- <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.
+ <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.
</ul>
A collection expression is defined as follows.