--- a/model/ProvenanceModel.html Wed Nov 23 12:55:47 2011 +0000
+++ b/model/ProvenanceModel.html Wed Nov 23 14:57:03 2011 +0000
@@ -375,13 +375,13 @@
<h4>Event Ordering</h4>
<p>To allow for minimalistic clock assumptions, like Lamport
-[[CLOCK]], PROV-DM relies on a notion of relative ordering of <a>event</a>s,
-without using physical clocks. This specification assumes that a partial order exists between <a>event</a>s.
+[[CLOCK]], PROV-DM relies on a notion of relative ordering of <a title="event">events</a>,
+without using physical clocks. This specification assumes that a partial order exists between <a title="event">events</a>.
</p>
<p>Specifically, <dfn id="dfn-follows">follows</dfn> is a partial
-order between <a>event</a>s, indicating that an <a>event</a> occurs after another.
+order between <a title="event">events</a>, indicating that an <a>event</a> occurs after another.
For convenience, <dfn id="dfn-precedes">precedes</dfn> is defined as
the symmetric of follows. </p>
@@ -489,7 +489,7 @@
</div>
-<p>The data model is designed to capture events that happened in the past, as opposed to events
+<p>The data model is designed to capture activities that happened in the past, as opposed to activities
that may or will happen.
However, this distinction is not formally enforced.
Therefore, all PROV-DM assertions SHOULD be interpreted as a record of what has happened, as opposed to what may or will happen.</p>
@@ -571,28 +571,28 @@
<p>This scenario is concerned with the evolution of a crime statistics
file (referred to as e0) stored on a shared file system and which
journalists Alice, Bob, Charles, David, and Edith can share and
-edit. We consider various events in the evolution of file e0;
-events listed below follow each other, unless otherwise specified.</p>
+edit. We consider various <a title="event">events</a> in the evolution of file e0;
+<a title="event">events</a> listed below follow each other, unless otherwise specified.</p>
<p>
-Event evt1: Alice creates (a0) an empty file in /share/crime.txt. We denote this e1.
+<a>Event</a> evt1: Alice creates (a0) an empty file in /share/crime.txt. We denote this e1.
</p>
<p>
-Event evt2: Bob appends (a1) the following line to /share/crime.txt:</p>
+<a>Event</a> evt2: Bob appends (a1) the following line to /share/crime.txt:</p>
<pre>
There was a lot of crime in London last month.
</pre>
<p>We denote this e2.</p>
-<p>Event evt3: Charles emails (a2) the contents of /share/crime.txt, as an
+<p><a>Event</a> evt3: Charles emails (a2) 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.)
</p>
<p>
-Event evt4: David edits (a3) file /share/crime.txt as follows.</p>
+<a>Event</a> evt4: David edits (a3) file /share/crime.txt as follows.</p>
<pre>
There was a lot of crime in London and New-York last month.
</pre>
@@ -600,10 +600,10 @@
We denote this e3.
</p>
-<p>Event evt5: Edith emails (a4) the contents of /share/crime.txt as an attachment, referred to as e5.
+<p><a>Event</a> evt5: Edith emails (a4) the contents of /share/crime.txt as an attachment, referred to as e5.
</p>
-<p>Event evt6: between events evt4 and evt5, someone (unspecified) runs a spell checker (a5) on the file /share/crime.txt.
+<p><a>Event</a> evt6: between <a title="event">events</a> evt4 and evt5, someone (unspecified) runs a spell checker (a5) on the file /share/crime.txt.
The file after spell checking is referred to as e6.
</p>
@@ -627,7 +627,7 @@
-<p>These entity records 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 "...".</p>
+<p>These entity records list attributes that have been given values during intervals delimited by <a title="event">events</a>; 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 <a>event</a> described in this scenario, it is marked by "...".</p>
<blockquote>
<table>
<tr><td>Entity</td><td>Characterization Interval</td></tr>
@@ -656,7 +656,7 @@
<p>
-Generation Records (described in <a href="#record-Generation">Section Generation</a>) represent the event at which a file is created in a specific form. Attributes are used to describe the modalities according to which a given entity is generated by a given activity. The interpretation of attributes is application specific. Illustrations of such attributes for the scenario are: no attribute is provided for <span class="name">e0</span>;
+Generation Records (described in <a href="#record-Generation">Section Generation</a>) represent the <a>event</a> at which a file is created in a specific form. Attributes are used to describe the modalities according to which a given entity is generated by a given activity. The interpretation of attributes is application specific. Illustrations of such attributes for the scenario are: no attribute 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">a5</span>. Two identifiers <span class="name">g1</span> and <span class="name">g2</span> identify the generation records referenced in derivations introduced below.</p>
<pre>
wasGeneratedBy(e0, a0, [])
@@ -671,7 +671,7 @@
<p>
-Usage Records (described in <a href="#record-Usage">Section Usage</a>) represent the event by which a file is read by an activity.
+Usage Records (described in <a href="#record-Usage">Section Usage</a>) represent the <a>event</a> by which a file is read by an activity.
Likewise, attributes describe the modalities according to which the various entities are used by activities. Illustrations of such attributes are:
<span class="name">e1</span> is used in the context of <span class="name">a1</span>'s <span class="name">load</span> functionality; <span class="name">e2</span> is used by <span class="name">a2</span> in the context of its attach functionality; <span class="name">e3</span> is used on the standard input by <span class="name">a5</span>. Two identifiers <span class="name">u1</span> and <span class="name">u2</span> identify the Usage records referenced in derivations introduced below.</p>
@@ -827,7 +827,7 @@
<p>
-The assertion of an entity record, <span class="name">entity(id, [ attr1=val1, ...])</span>, states, from a given asserter's viewpoint, the existence of an entity, whose situation in the world is represented by the attribute-value pairs, which remain unchanged during a characterization interval, i.e. a continuous interval between two events in the world.
+The assertion of an entity record, <span class="name">entity(id, [ attr1=val1, ...])</span>, states, from a given asserter's viewpoint, the existence of an entity, whose situation in the world is represented by the attribute-value pairs, which remain unchanged during a characterization interval, i.e. a continuous interval between two <a title="event">events</a> in the world.
</p>
<p>
@@ -902,7 +902,7 @@
<p>In PROV-DM, an <dfn id="dfn-activity">activity record</dfn> is a representation of an identifiable activity, which performs a piece of work.</p>
-<p>An activity, represented by an activity record, is delimited by its start and its end events; hence, it occurs over an interval delimited by two events. However, an activity record need not mention time information, nor duration, because they may not be known.</p>
+<p>An activity, represented by an activity record, is delimited by its <a title="activity start event">start</a> and its <a title="activity end event">end</a> events; hence, it occurs over an interval delimited by two <a title="event">events</a>. However, an activity record need not mention time information, nor duration, because they may not be known.</p>
<p>Such start and end times constitute <em>attributes</em> of an activity, where the interpretation of attribute in the context of an activity record is the same as the interpretation of attribute for entity record: an activity record's attribute remains constant for the duration of the activity it represents. Further characteristics of the activity in the world can be represented by other attribute-value pairs, which MUST also remain unchanged during the activity duration.</p>
@@ -945,7 +945,7 @@
<p>identified by identifier <span class="name">id</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span> (declared in some namespace with prefix <span class="name">app</span>). The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity. The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for subtyping to be expressed.</p>
</div>
-<p>The mere existence of an activity assertion entails some event ordering in the world, since the <a>activity start event</a> <a>precedes</a> the <a>activity end event</a>. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
+<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since the <a>activity start event</a> <a>precedes</a> the <a>activity end event</a>. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
<div class='interpretation' id='start-precedes-end'> From an activity record, one can infer that the
<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a> of the represented activity.</div>
@@ -1111,8 +1111,8 @@
<h4>Generation Record</h4>
-<p>In PROV-DM, a <dfn id="dfn-Generation">generation record</dfn> is a representation of a world event, the creation of a new entity by an activity. This entity did not exist before creation.
-The representation of this event encompasses a description of the modalities of generation of this entity by this activity.</p>
+<p>In PROV-DM, a <dfn id="dfn-Generation">generation record</dfn> is a representation of a world <a title="entity generation event">event</a>, the creation of a new entity by an activity. This entity did not exist before creation.
+The representation of this <a>event</a> encompasses a description of the modalities of generation of this entity by this activity.</p>
<p>A generation record, written <span class="name">wasGeneratedBy(id,e,a,attrs,t)</span> in PROV-ASN, has the following components:</p>
@@ -1157,14 +1157,14 @@
wasGeneratedBy(e1,a1,[ex:port="p1", ex:order="1" %% xsd:integer], 2001-10-26T21:32:52)
wasGeneratedBy(e2,a1,[ex:port="p1", ex:order="2" %% xsd:integer], 2001-10-26T10:00:00)
</pre>
-<p>state the existence of two events in the world (with respective times <span class="name">2001-10-26T21:32:52</span> and <span class="name">2001-10-26T10:00:00</span>), at which new entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by an activity record identified by <span class="name">a1</span>.
+<p>state the existence of two <a title="event">events</a> in the world (with respective times <span class="name">2001-10-26T21:32:52</span> and <span class="name">2001-10-26T10:00:00</span>), at which new entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by an activity record identified by <span class="name">a1</span>.
The first one is available as the first value on port p1, whereas the other is the second value on port p1. The semantics of <span class="name">port</span> and <span class="name">order</span> in these records are application specific.
</p>
</div>
-<p>The assertion of a generation event implies ordering of events in the world.</p>
+<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world.</p>
<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,pe,attrs)</span> or <span class="name">wasGeneratedBy(x,pe,attrs,t)</span>, <span class='conditional'>then</span> generation of the entity denoted by <span class="name">x</span> <a>precedes</a> the end
@@ -1175,7 +1175,7 @@
<p>A given entity record can be referred to in a single generation record in the scope of a given <a href="#record-Account">account</a>.
The rationale for this constraint is as follows.
-If two activities sequentially set different values to some attribute by means of two different generate events, then they generate distinct entities. Alternatively, for two activities to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this synchronization would constitute the actual generation of the entity, but is performed by a single activity. This unicity constraint is formalized as follows.
+If two activities sequentially set different values to some attribute by means of two different <a title="entity generation event">generation events</a>, then they generate distinct entities. Alternatively, for two activities to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this synchronization would constitute the actual generation of the entity, but is performed by a single activity. This unicity constraint is formalized as follows.
<div class='constraint' id='generation-unicity'>Given an entity record denoted by <span class="name">e</span>, two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, and two sets of attribute-value pairs <span class="name">attrs1</span> and <span class="name">attrs2</span>,
<span class='conditional'>if</span> the records <span class="name">wasGeneratedBy(e,a1,attrs1)</span> and <span class="name">wasGeneratedBy(e,a2,attrs2)</span> exist in the scope of a given account,
@@ -1193,7 +1193,7 @@
-<p>In PROV-DM, a <dfn id="dfn-Use">usage record</dfn> is a representation of a world event: the consumption of an entity by an activity. The representation includes a description of the modalities of usage of this entity by this activity.</p>
+<p>In PROV-DM, a <dfn id="dfn-Use">usage record</dfn> is a representation of a world <a title="entity usage event">event</a>: the consumption of an entity by an activity. The representation includes a description of the modalities of usage of this entity by this activity.</p>
<p>A usage record, written <span class="name">used(id,a,e,attrs,t)</span> in PROV-ASN, has the following constituent:</p>
@@ -1663,7 +1663,7 @@
<div class='interpretation' id='derivation-generation-generation-ordering'>
Given two entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the record <span class="name">wasBasedOn(e2,e1)</span>
holds, <span class='conditional'>then</span> the
-generation event of the entity represented by the entity record denoted by <span class="name">e1</span> <a>precedes</a> the generation event of
+<a title="entity generation event">generation event</a> of the entity represented by the entity record denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a> of
the entity represented by the entity record denoted by <span class="name">e2</span>.
</div>
@@ -1744,6 +1744,8 @@
<p>A <dfn id="complementOf">complementarity record</dfn> is a relationship between two entities stated to have compatible characterization over some continuous interval between two events.</p>
+<!-- PAOLO, which event do you refer to? <a>event</a>?? -->
+
<p>
The rationale for introducing this relationship is that in general, at any given time, for an entity in the world, there may be multiple ways of characterizing it, and hence multiple representations can be asserted by different asserters. In the example that follows, suppose thing "Royal Society" is represented by two asserters, each using a different set of attributes. If the asserters agree that both representations refer to "The Royal Society", the question of whether any correspondence can be established between the two representations arises naturally. This is particularly relevant when (a) the sets of attributes used by the two representations overlap partially, or (b) when one set is subsumed by the other. In both these cases, we have a situation where each of the two asserters has a partial view of "The Royal Society", and establishing a correspondence between them on the shared attributes is beneficial, as in case (a) each of the two representation <em>complements</em> the other, and in case (b) one of the two (that with the additional attributes) complements the other.</p>
@@ -2570,7 +2572,7 @@
<div class='interpretation' id='wasInformedBy-ordering'>
Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasInformedBy(a2,a1)</span>
holds, <span class='conditional'>then</span> the
-start event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the end event of
+<a title="activity start event">start event</a> of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity end event">end event</a> of
the activity record denoted by <span class="name">a2</span>.
</div>
@@ -2639,7 +2641,7 @@
<div class='interpretation' id='wasStartedBy-ordering'>
Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasStartedBy(a2,a1)</span>
holds, <span class='conditional'>then</span> the
-start event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the start event of
+<a title="activity start event">start</a> event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity start event">start event</a> of
the activity record denoted by <span class="name">a2</span>.
</div>
@@ -2994,8 +2996,8 @@
<section class="appendix">
<h2>Changes Since Previous Version</h2>
<ul>
-<li>11/21/11: Consolidation of event in section 2.1.2</li>
-<li>11/21/11: Added wasStartedBy between activities</li>
+<li>11/21/11: Consolidation of event in section 2.1.2 and linking to definitions from the rest of document. </li>
+<li>11/21/11: Added wasStartedBy between activities.</li>
<li>11/21/11: Added wasInformedBy-ordering constraint.</li>
<li>11/17/11: Added Traceability Record.</li>
<li>11/17/11: Rewrote the whole section on Derivation Record.</li>