--- a/model/ProvenanceModel.html Mon Nov 07 12:27:09 2011 +0000
+++ b/model/ProvenanceModel.html Mon Nov 07 12:43:25 2011 +0000
@@ -536,12 +536,12 @@
<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"))
-wasGeneratedBy(e2, pe1, qualifier(fct="save"))
-wasGeneratedBy(e3, pe3, qualifier(fct="save"))
-wasGeneratedBy(e4, pe2, qualifier(port="smtp", section="attachment"))
-wasGeneratedBy(e5, pe4, qualifier(port="smtp", section="attachment"))
-wasGeneratedBy(e6, pe5, qualifier(file="stdout"))
+wasGeneratedBy(e1, pe0, qualifier(ex:fct="create"))
+wasGeneratedBy(e2, pe1, qualifier(ex:fct="save"))
+wasGeneratedBy(e3, pe3, qualifier(ex:fct="save"))
+wasGeneratedBy(e4, pe2, qualifier(ex:port="smtp", ex:section="attachment"))
+wasGeneratedBy(e5, pe4, qualifier(ex:port="smtp", ex:section="attachment"))
+wasGeneratedBy(e6, pe5, qualifier(ex:file="stdout"))
</pre>
@@ -552,11 +552,11 @@
Likewise, to describe the modalities according to which the various entities are used by activities, a qualifier (construct described in <a href="#record-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 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"))
-used(pe2,e2,qualifier(fct="attach"))
-used(pe4,e3,qualifier(fct="attach"))
-used(pe5,e3,qualifier(file="stdin"))
+used(pe1,e1,qualifier(ex:fct="load"))
+used(pe3,e2,qualifier(ex:fct="load"))
+used(pe2,e2,qualifier(ex:fct="attach"))
+used(pe4,e3,qualifier(ex:fct="attach"))
+used(pe5,e3,qualifier(ex:file="stdin"))
</pre>
@@ -565,8 +565,8 @@
<pre>
wasDerivedFrom(e2,e1)
wasDerivedFrom(e3,e2)
-wasDerivedFrom(e4,e2,pe2,qualifier(port=smtp, section="attachment"),qualifier(fct="attach"))
-wasDerivedFrom(e5,e3,pe4,qualifier(port=smtp, section="attachment"),qualifier(fct="attach"))
+wasDerivedFrom(e4,e2,pe2,qualifier(ex:port=smtp, ex:section="attachment"),qualifier(ex:fct="attach"))
+wasDerivedFrom(e5,e3,pe4,qualifier(ex:port=smtp, ex:section="attachment"),qualifier(ex:fct="attach"))
</pre>
@@ -606,11 +606,11 @@
<p>
Control Records (described in <a href="#record-Control">Section Control</a>): the influence of an agent over an activity is expressed as control, and the nature of this influence is described by qualifier (construct described in <a href="#record-qualifier">Section Qualifier</a>). Illustrations of such qualifiers include the role of the participating agent, as creator, author and communicator.</p>
<pre>
-wasControlledBy(pe0,a1, qualifier(role="creator"))
-wasControlledBy(pe1,a2, qualifier(role="author"))
-wasControlledBy(pe2,a3, qualifier(role="communicator"))
-wasControlledBy(pe3,a4, qualifier(role="author"))
-wasControlledBy(pe4,a5, qualifier(role="communicator"))
+wasControlledBy(pe0,a1, qualifier(prov:role="creator"))
+wasControlledBy(pe1,a2, qualifier(prov:role="author"))
+wasControlledBy(pe2,a3, qualifier(prov:role="communicator"))
+wasControlledBy(pe3,a4, qualifier(prov:role="author"))
+wasControlledBy(pe4,a5, qualifier(prov:role="communicator"))
</pre>
</section>
@@ -884,7 +884,7 @@
<pre class="example">
entity(e1, [employee="1234", name="Alice"]) and agent(e1)
-entity(e2) and wasControlledBy(pe,e2,qualifier(role="author"))
+entity(e2) and wasControlledBy(pe,e2,qualifier(prov:role="author"))
</pre>
<p>the entity record identified by <span class="name">e1</span> is accompanied by an explicit assertion of an agent record, and this assertion holds irrespective of activities it may be involved in. On the other hand, from the entity record identified by <span class="name">e2</span>, one can infer an agent record, as per the following inference.
</p>
@@ -1000,8 +1000,8 @@
<p>
The following generation assertions</p>
<pre class="example">
- wasGeneratedBy(e1,pe1,qualifier(port="p1", order=1),t1)
- wasGeneratedBy(e2,pe1,qualifier(port="p1", order=2),t2)
+ wasGeneratedBy(e1,pe1,qualifier(ex:port="p1", ex:order=1),t1)
+ wasGeneratedBy(e2,pe1,qualifier(ex:port="p1", ex:order=2),t2)
</pre>
<p>state the existence of two events in the world (with respective times <span class="name">t1</span> and <span class="name">t2</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">pe1</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.
@@ -1086,8 +1086,8 @@
<p>The following use assertions</p>
<pre class="example">
- used(pe1,e1,qualifier(parameter="p1"),t1)
- used(pe1,e2,qualifier(parameter="p2"),t2)
+ used(pe1,e1,qualifier(ex:parameter="p1"),t1)
+ used(pe1,e2,qualifier(ex:parameter="p2"),t2)
</pre>
<p>state that the activity, represented by the activity record identified by <span class="name">pe1</span>, consumed two entities, represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">t1</span> and <span class="name">t2</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these records is application specific.</p>
@@ -1205,7 +1205,7 @@
<p>The following derivation assertions</p>
<pre class="example">
-wasDerivedFrom(e5,e3,pe4,qualifier(channel="out"),qualifier(channel="in"))
+wasDerivedFrom(e5,e3,pe4,qualifier(ex:channel="out"),qualifier(ex:channel="in"))
wasDerivedFrom(e3,e2)
</pre>
<p>
@@ -1436,7 +1436,7 @@
<p>
The following control assertion</p>
<pre class="example">
-wasControlledBy(pe3,a4,qualifier[role="author"])
+wasControlledBy(pe3,a4,qualifier(prov:role="author"))
</pre>
<p>states that the activity, represented by the activity record denoted by <span class="name">pe3</span> saw the involvement of an entity, represented by entity record denoted by <span class="name">a4</span> in the capacity of author. This specification reserves the qualifier name <span class="name">role</span> (see Section <a href="#record-qualifier">Qualifier</a>) to denote the function of an entity with respect to an activity.
</p>
@@ -1632,9 +1632,9 @@
the record <span class="name">wasScheduledAfter(pe2,pe1)</span>
holds, <span class='conditional'>if and only if</span>
there are two entity records identified by <span class="name">e1</span> and <span class="name">e2</span>,
-such that <span class="name">wasControlledBy(pe1,e1,qualifier(role="end"))</span> and <span class="name">wasControlledBy(pe2,e2,qualifier(role="start"))</span> and <span class="name">wasDerivedFrom(e2,e1)</span>.
+such that <span class="name">wasControlledBy(pe1,e1,qualifier(prov:role="end"))</span> and <span class="name">wasControlledBy(pe2,e2,qualifier(prov:role="start"))</span> and <span class="name">wasDerivedFrom(e2,e1)</span>.
</div>
-<p>This definition assumes that the activities represented by activity records identified by <span class="name">pe1</span> and <span class="name">pe2</span> are controlled by some agents (with identifiers <span class="name">e1</span> and <span class="name">e2</span>), where the first agent terminates (control qualifier <span class="name">qualifier(role="end")</span>) the first activity, and the second agents initiates (control qualifier <span class="name">qualifier(role="start")</span>) the second activity. The second agent being "derived" from the first enforces temporal ordering. </p>
+<p>This definition assumes that the activities represented by activity records identified by <span class="name">pe1</span> and <span class="name">pe2</span> are controlled by some agents (with identifiers <span class="name">e1</span> and <span class="name">e2</span>), where the first agent terminates (control qualifier <span class="name">qualifier(prov:role="end")</span>) the first activity, and the second agents initiates (control qualifier <span class="name">qualifier(prov:role="start")</span>) the second activity. The second agent being "derived" from the first enforces temporal ordering. </p>
<p>
In the following assertions, we find two activity records, identified by <span class="name">pe1</span> and <span class="name">pe2</span>, representing two activities, which took place on two separate hosts.</p>
@@ -1643,8 +1643,8 @@
activity(pe2,long-workflow,t3,t4,[host="server2.example.org"])
entity(e1,[type="scheduler",state=1])
entity(e2,[type="scheduler",state=2])
-wasControlledBy(pe1,e1,qualifier(role="end"))
-wasControlledBy(pe2,e2,qualifier(role="start"))
+wasControlledBy(pe1,e1,qualifier(prov:role="end"))
+wasControlledBy(pe2,e2,qualifier(prov:role="start"))
wasDerivedFrom(e2,e1)
wasScheduledAfter(pe2,pe1)
</pre>
@@ -1817,15 +1817,15 @@
entity(e1,[type="document"])
entity(e2,[type="document"])
activity(pe,transform,t1,t2,[])
-used(pe,e1,qualifier(file="stdin"))
-wasGeneratedBy(e2, pe, qualifier(file="stdout"))
+used(pe,e1,qualifier(prov:file="stdin"))
+wasGeneratedBy(e2, pe, qualifier(prov:file="stdout"))
annotation(ann1,[icon="doc.png"])
hasAnnotation(e1,ann1)
hasAnnotation(e2,ann1)
annotation(ann2,[style="dotted"])
-hasAnnotation(relation(pe,e1,qualifier(file="stdin")),ann2)
+hasAnnotation(relation(pe,e1,qualifier(prov:file="stdin")),ann2)
</pre>
<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these records with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>. It also asserts an activity, its use of the first entity, and its generation of the second entity. The <span class="name">used</span> relation is annotated with a style (an application specific way of rendering this edge graphically).
</p>
@@ -1894,7 +1894,7 @@
...
wasGeneratedBy(e0,pe0,qualifier())
...
- wasControlledBy(pe4,a5, qualifier(role="communicator")) )
+ wasControlledBy(pe4,a5, qualifier(prov:role="communicator")) )
</pre>
<p>contains the set of provenance records of section <a href="#example-prov-asn-encoding">example-prov-asn-encoding</a>, is asserted by agent <span class="name">http://example.org/asserter</span>, and is identified by identifier <span class="name">acc0</span>.
</p>
@@ -1945,7 +1945,7 @@
...
activity(pe1,create-file,t1)
...
- wasGeneratedBy(e0,pe1,qualifier(fct="create"))
+ wasGeneratedBy(e0,pe1,qualifier(ex:fct="create"))
... )
</pre>
<p>with identifier <span class="name">acc2</span>, containing assertions by asserter by <span class="name">http://example.org/asserter2</span> stating that the entity represented by entity record identified by <span class="name">e0</span> was generated by an activity represented by activity record identified by <span class="name">pe1</span> instead of <span class="name">pe0</span> in the previous account <span class="name">acc0</span>. If accounts <span class="name">acc0</span> and <span class="name">acc2</span> are merged together, the resulting set of records violates <a href="#generation-unicity">generation-unicity</a>.</p>
@@ -1964,7 +1964,7 @@
http://example.org/asserter2,
entity(e1, [ type="File", location="/shared/crime.txt", creator="Alice", content="" ])
activity(pe0,copy-file,t)
- wasGeneratedBy(e1,pe0,qualifier(fct="create"))
+ wasGeneratedBy(e1,pe0,qualifier(ex:fct="create"))
isComplement(e1,e0)))
</pre>
<p>Alternatively, an activity record identified by <span class="name">pe0</span> occurs in each of the two accounts. Therefore, each activity record is asserted in a separate scope, and therefore may represent different activities in the world.
@@ -2098,7 +2098,7 @@
<p>
The following control record qualifies the role of the agent identified by <span class="name">a5</span> in this control relation. </p>
<pre class="example">
- wasControlledBy(pe4,a5, qualifier(role="communicator"))
+ wasControlledBy(pe4,a5, qualifier(prov:role="communicator"))
</pre>