--- a/model/ProvenanceModel.html Tue Jul 26 22:03:26 2011 -0400
+++ b/model/ProvenanceModel.html Wed Jul 27 09:02:36 2011 +0100
@@ -203,10 +203,10 @@
<p>
Use:
<pre>
-use(pe1,e1,in)
-use(pe3,e2,in)
-use(pe2,e2,in)
-use(pe4,e3,in)
+uses(pe1,e1,in)
+uses(pe3,e2,in)
+uses(pe2,e2,in)
+uses(pe4,e3,in)
</pre>
</p>
@@ -271,7 +271,7 @@
<section>
<h3>Graphical Illustration</h3>
-Provenance assertions as graph:<br/>
+Provenance assertions can be represented as a <a href="#illustration-convention">graph</a>.<br/>
<img src="example-graphical.png"/>
<p/>
<img src="timeline.png"/>
@@ -454,7 +454,7 @@
<p><dfn id="dfn-Use">Use</dfn> represents the consumption of a characterized entity by an activity.</p>
-<p>A Use assertion, <b>use(pe,b,r,t)</b>:
+<p>A Use assertion, <b>uses(pe,b,r,t)</b>:
<ul>
<li> refers to a process execution <b>pe</b>;
<li> refers to a BOB <b>b</b>, representing the characterized entity that is used;
@@ -465,7 +465,7 @@
<p>
<pre class="example">
-use(pe1,e1,in,t)
+uses(pe1,e1,in,t)
</pre>
</p>
@@ -478,12 +478,12 @@
-<p>Given an assertion <b>Use(pe,x,r)</b> or <b>Use(pe,x,r,t)</b>,
+<p>Given an assertion <b>uses(pe,x,r)</b> or <b>uses(pe,x,r,t)</b>,
at least one value of <b>x</b>'s attributes is a pre-condition for the activity denoted by <b>pe</b> to terminate.</p>
-<p>Given an assertion <b>Use(pe,x,r)</b> or <b>Use(pe,x,r,t)</b>, one can
+<p>Given an assertion <b>uses(pe,x,r)</b> or <b>uses(pe,x,r,t)</b>, one can
infer that the use of the entity denoted by <b>x</b> precedes the end
of <b>pe</b> and follows the beginning of <b>pe</b>. Furthermore, we
can infer that the generation of the entity <b>x</b> always precedes
@@ -533,10 +533,10 @@
<p>This is formalized by a novel inference, referred to as <em>process execution introduction</em>:
if <b>isDerivedFrom(e1,e0)</b> holds, then there exists a process execution <b>pe</b>, and roles <b>r0</b>,<b>r1</b>,
such that:
- <b>isGeneratedBy(e1,pe,r1)</b> and <b>use(pe,e0,r0)</b>.</p>
+ <b>isGeneratedBy(e1,pe,r1)</b> and <b>uses(pe,e0,r0)</b>.</p>
<p>
-The converse inference does not hold. Indeed, when a generation <b>isGeneratedBy(e1,pe,r1)</b> precedes <b>use(pe,e0,r0)</b>, for some <b>e0</b>, <b>e1</b>, <b>r0</b>, <b>r1</b>, and <b>pe</b>, one cannot infer derivation <b>isDerivedFrom(e1,e0)</b> since the values of attributes of <b>e1</b> cannot possibly be determined by the values of attributes of <b>e0</b>, given the creation of <b>e1</b> precedes the use of <b>e0</b>.
+The converse inference does not hold. Indeed, when a generation <b>isGeneratedBy(e1,pe,r1)</b> precedes <b>uses(pe,e0,r0)</b>, for some <b>e0</b>, <b>e1</b>, <b>r0</b>, <b>r1</b>, and <b>pe</b>, one cannot infer derivation <b>isDerivedFrom(e1,e0)</b> since the values of attributes of <b>e1</b> cannot possibly be determined by the values of attributes of <b>e0</b>, given the creation of <b>e1</b> precedes the use of <b>e0</b>.
</p>
@@ -725,7 +725,7 @@
<b>unspecified0</b>, <b>unspecified1</b>, <b>unspecified2</b>, ....
<pre class="example">
- use(pe,e) expands to use(pe,e,unspecified)
+ uses(pe,e) expands to uses(pe,e,unspecified)
</pre>
where unspecified is an unspecified role.
</p>
@@ -856,6 +856,44 @@
<section class="appendix">
+ <h2>Illustration and Notation Conventions</h2>
+
+ <p> In this section, we summarize the conventions adopted for the graphical illustration and the abstract syntax notation appearing in this specification.
+ </p>
+
+<div class='note'>Should we formalize the graphical illustration and abstract syntax notation. Where? Should they become normative?</div>
+
+<section id='illustration-convention'>
+ <h3>Illustration Conventions</h3>
+<ul>
+<li>The graphical illustration aims to <em>illustrate</em> the provenance model. It is not intended to represent all the details of the model, and therefore, cannot be seen as a alternate notation for expressing provenance.</li>
+
+<li>The graphical illustration is a graph. </li>
+
+<li>BOBs, process executions and agents are represented as nodes, with oval, rectangular, and half-hexagonal shapes, respectively. </li>
+
+<li>Use, Generation, Derivation, IVPof are represented as directed edges.</li>
+
+<li>BOBs are laid out according to time (the time at which they are generated). Time SHOULD progress from left to right or from top to bottom. This means that edges for Use, Generation and Derivation typically point from right to left or from bottom to top.</li>
+
+</ul>
+
+
+</section>
+
+
+<section>
+ <h3>Abstract Syntax Notation Conventions</h3>
+<ul>
+<li>Language constructs are represented as <b>name(arg0, arg1, ...)</b>, where the name of the construct occurs first, and is followed by its arguments.</li>
+<li>For use, generation, and derivation event, the first argument is the 'effect' (i.e. most recent item) and the second argument is the 'cause' (i.e. least recent item). This order is compatible with the temporal layout of the graphical notation.
+</li>
+</ul>
+</section>
+
+ </section>
+
+<section class="appendix">
<h2>Acknowledgements</h2>
<p>
WG membership to be listed here.