--- a/model/ProvenanceModel.html Thu Aug 04 13:38:27 2011 +0100
+++ b/model/ProvenanceModel.html Thu Aug 04 14:20:13 2011 +0100
@@ -20,7 +20,7 @@
specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "PIL-Model",
+ shortName: "PIDM-Model",
// if your specification has a subtitle that goes below the main
// formal title, define it here
@@ -121,58 +121,52 @@
<p>This scenario is concerned with the evolution of a crime statistics
-file (e0) stored on a shared file system and which journalists Alice,
-Bob, Charles, David, and Edith can share and edit. We now consider
-different events in the evolution of file (e0).</p>
+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 now consider various events in the evolution of file (e0);
+events follow each other, unless specified otherwise.</p>
<p>
-Event evt1: Alice creates an empty file in /share/crime.txt. We denote this e1.
+Event evt1: Alice creates (pe0) an empty file in /share/crime.txt. We denote this e1.
</p>
<p>
-Event evt2: Bob appends the following line to /share/crime.txt:
+Event evt2: Bob appends (pe1) the following line to /share/crime.txt:
<pre>
There was a lot of crime in London last month.
</pre>
We denote this e2.
</p>
-<p>Event evt3: Charles emails the contents of /share/crime.txt
-<pre>
-cat /share/crime.txt | sendmail ...
-</pre>
-We denote this e4.
+<p>Event evt3: Charles emails (pe2) the contents of /share/crime.txt, as an
+attachment, which refer to as e4.
</p>
<p>
-Event evt4: David edits file /share/crime.txt as follows.
+Event evt4: David edits (pe3) file /share/crime.txt as follows.
<pre>
There was a lot of crime in London and New-York last month.
</pre>
We denote this e3.
</p>
-<p>Event evt5: Edith emails the contents of /share/crime.txt
-<pre>
-cat /share/crime.txt | sendmail ...
-</pre>
-We denote this e5.
+<p>Event evt5: Edith emails (pe4) 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 on the file /share/crime.txt.
+<p>Event evt6: between events evt4 and evt5, someone (unspecified) runs a spell checker (pe5) on the file /share/crime.txt.
The file after spell checking is referred to as e6.
</p>
</section>
<section>
-<h3>Encoding in PIL</h3>
+<h3>Encoding using Abstract Syntax Notation</h3>
-In this section, the example is encoded using PIL constructs (specified in section <a href="\data-model-concepts">concepts</a>), expressed in the Abstract Syntax Notation. Details about the Abstract Syntax Notation can be found in <a href="'#ASN-convention'">appendix</a>.
+In this section, the example is encoded according to the Provenance data model (specified in section <a href="\data-model-concepts">concepts</a>), expressed in the Abstract Syntax Notation. Details about the Abstract Syntax Notation can be found in <a href="'#ASN-convention'">appendix</a>.
<p>
-Entities (construct described at <a href="#concept-Entity">entity</a>):
+Entities (construct described at <a href="#concept-Entity">entity</a>). The file in its various forms and its copies are modelled as entities.
<pre>
entity(e0, [ type: "File", location: "/shared/crime.txt", creator: "Alice" ])
entity(e1, [ type: "File", location: "/shared/crime.txt", creator: "Alice", content: "" ])
@@ -185,20 +179,23 @@
</p>
-<p>
+<p>The entities, as characterized, hold during intervals delimited by events. The following table lists all events and their corresponding validity events, where evt5 is considered to be the most recent event.
+<blockquote>
<table>
-<tr><td>e0:</td><td> holds in interval [t,t+4[</td></tr>
-<tr><td>e1:</td><td> holds in interval [t,t+1[</td></tr>
-<tr><td>e2:</td><td> holds in interval [t+1,t+3[</td></tr>
-<tr><td>e3:</td><td> holds in interval [t+3,t+4[</td></tr>
-<tr><td>e4:</td><td> the information piped to sendmail at t+2 (that's a copy of e2's content)</td></tr>
-<tr><td>e5:</td><td> the information piped to sendmail at t+4 (that's a copy of e3's content)</td></tr>
-<tr><td>e6:</td><td> holds in interval [t+3,t+4[; a different view of the characterized thing represented by e3. </td></tr>
+<tr><td>Entity</td><td>Interval</td></tr>
+<tr><td>e0</td><td>evt1 - evt5</td></tr>
+<tr><td>e1</td><td>evt1 - evt2</td></tr>
+<tr><td>e2</td><td>evt2 - evt4</td></tr>
+<tr><td>e3</td><td>evt4 - evt3</td></tr>
+<tr><td>e4</td><td>evt3 - evt5</td></tr>
+<tr><td>e5</td><td>evt3 - evt5</td></tr>
+<tr><td>e6</td><td>evt6 - evt5 </td></tr>
</table>
+</blockquote>
</p>
<p>
-Derivations (construct described at <a href="#concept-Derivation">derivation</a>):
+Derivations (construct described at <a href="#concept-Derivation">derivation</a>): derivations express that an entity is derived from another.
<pre>
isDerivedFrom(e2,e1)
isDerivedFrom(e3,e2)
@@ -208,7 +205,19 @@
</p>
<p>
-Generations (construct described at <a href="#concept-Generation">generation</a>):
+Process Executions (construct described at <a href="#concept-ProcessExecution">process execution</a>): process execution represents an activity in the scenario.
+<pre>
+processExecution(pe0,create-file,t)
+processExecution(pe1,add-crime-in-london,t+1)
+processExecution(pe2,email,t+2)
+processExecution(pe3,edit-London-New-York,t+3)
+processExecution(pe4,email,t+4)
+processExecution(pe5,spellcheck)
+</pre>
+</p>
+
+<p>
+Generations (construct described at <a href="#concept-Generation">generation</a>): generation is the event at which a file is created in a specific form.
<pre>
isGeneratedBy(e0,pe0,out)
isGeneratedBy(e1,pe0,out)
@@ -216,12 +225,13 @@
isGeneratedBy(e3,pe3,out)
isGeneratedBy(e4,pe2,out)
isGeneratedBy(e5,pe4,out)
+isGeneratedBy(e6,pe5,out)
</pre>
</p>
<p>
-Uses (construct described at <a href="#concept-Use">use</a>):
+Uses (construct described at <a href="#concept-Use">use</a>): use is the event by which a file is read by a process execution.
<pre>
uses(pe1,e1,in)
uses(pe3,e2,in)
@@ -230,32 +240,21 @@
</pre>
</p>
+
+
<p>
-Process Executions (construct described at <a href="#concept-ProcessExecution">process execution</a>):
+isComplementOf: (this relation is described at <a href="#concept-IVP-of">isComplementOf</a>). The crime statistics file (e0) has various contents over its existence (e1,e2,e3); the entites e1,e2,e3 complement e0 with an attribute content. Likewise, e6 complements e3 with an attributed spellchecked.
<pre>
-processExecution(pe0,create-file,t)
-processExecution(pe1,add-crime-in-london,t+1)
-processExecution(pe2,copy,t+2)
-processExecution(pe3,edit-London-New-York,t+3)
-processExecution(pe4,copy,t+4)
+isComplementOf(e1,e0)
+isComplementOf(e2,e0)
+isComplementOf(e3,e0)
+isComplementOf(e6,e3)
</pre>
</p>
<p>
-IVP of: (this relation is described at <a href="#concept-IVP-of">IVP-of</a>)
-<pre>
-ivpOf(e1,e0)
-ivpOf(e2,e0)
-ivpOf(e3,e0)
-ivpOf(e6,e3)
-</pre>
-Note that e6 strictly contains all of e3's attributes, and it has an extra one, "disclaimer", and is therefore an ivpOf e3. Note that no other assertions (i.e., on generation) is available for this entity.
-</p>
-
-
-<p>
-Agents (construct described at <a href="#concept-Agent">agent</a>):
+Agents (construct described at <a href="#concept-Agent">agent</a>): in the provenance model, the various users are represented as agents, themselves being a type of entity.
<pre>
entity(e7, [ type: "Person", name: "Alice" ])
agent(e7)
@@ -949,7 +948,7 @@
<h3>Provenance Container</h3>
-<p>A <dfn id="dfn-ProvenanceContainer">Provenance Container</dfn> is an identifiable wrapper for a set of PIL constructs, including other containers, which allows for additional meta-information pertaining to these constructs to be expressed.</p>
+<p>A <dfn id="dfn-ProvenanceContainer">Provenance Container</dfn> is an identifiable wrapper for a set of PIDM constructs, including other containers, which allows for additional meta-information pertaining to these constructs to be expressed.</p>
<p>Such meta-information may be authorship, date of creation, justification for assertions, and cryptographic signature. </p>