--- a/model/ProvenanceModel.html Wed Dec 14 00:09:57 2011 +0000
+++ b/model/ProvenanceModel.html Wed Dec 14 00:11:16 2011 +0000
@@ -430,7 +430,6 @@
timeline. It can also help with the verification of associated
temporal constraints (though, again, this verification is outside the
scope of this specfication).
-
</p>
@@ -710,12 +709,12 @@
<p>
Activity Records (described in <a href="#record-Activity">Section Activity</a>) represent activities in the scenario.</p>
<pre>
-activity(a0, create-file, 2011-11-16T16:00:00,)
-activity(a1, add-crime-in-london, 2011-11-16T16:05:00,)
-activity(a2, email, 2011-11-16T17:00:00,)
-activity(a3, edit-London-New-York, 2011-11-17T09:00:00,)
-activity(a4, email, 2011-11-17T09:30:00,)
-activity(a5, spellcheck,,)
+activity(a0, 2011-11-16T16:00:00,,[prov:type="createFile"])
+activity(a1, 2011-11-16T16:05:00,,[prov:type="edit"])
+activity(a2, 2011-11-16T17:00:00,,[prov:type="email"])
+activity(a3, 2011-11-17T09:00:00,,[prov:type="edit"])
+activity(a4, 2011-11-17T09:30:00,,[prov:type="email"])
+activity(a5, , ,[prov:type="spellcheck"])
</pre>
@@ -993,10 +992,10 @@
<p>
Examples of activities include assembling a data set based on a set of measurements, performing a statistical analysis over a data set, sorting news items according to some criteria, running a sparql query over a triple store, editing a file, and publishing a web page. </p>
-<p> An activity record, written <span class="name">activity(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN, contains:</p>
+<p> An activity record, written <span class="name">activity(id, st, et, [ attr1=val1, ...])</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an identifier <span class="name">id</span> identifying an activity; the identifier of the activity record is defined to be the same as the identifier of the activity;</li>
-<li><em>recipeLink</em>: an OPTIONAL <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific specification of the activity;</li>
+<!--<li><em>recipeLink</em>: an OPTIONAL <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific specification of the activity;</li>-->
<li><em>startTime</em>: an OPTIONAL time <span class="name">st</span> indicating the start of the activity;</li>
<li><em>endTime</em>: an OPTIONAL time <span class="name">et</span> indicating the end of the activity;</li>
<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs <span class="name">[ attr1=val1, ...]</span>, representing other attributes of this activity that hold for its whole duration.</li>
@@ -1012,8 +1011,10 @@
<span class="name">(</span>
<span class="nonterminal">identifier</span>
<span class="optional"><span class="name">,</span>
+<!--
<span class="nonterminal">recipeLink</span> </span>
<span class="name">,</span>
+-->
<span class="optional"><span class="nonterminal">time</span></span>
<span class="name">,</span>
<span class="optional"><span class="nonterminal">time</span></span>
@@ -1025,7 +1026,7 @@
<p>
The following activity assertion</p>
<pre class="codeexample">
-activity(a1,add-crime-in-london,2011-11-16T16:05:00,2011-11-16T16:06:00,[ex:host="server.example.org",prov:type="ex:edit" %% xsd:QName])
+activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,[ex:host="server.example.org",prov:type="ex:edit" %% xsd:QName])
</pre>
<p>identified by identifier <span class="name">a1</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">ex</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>
@@ -1074,8 +1075,14 @@
<li><span class="name">Organization</span>: agents of type Organization are social institutions such as companies, societies etc. (This type is equivalent to a "foaf:organization" [[FOAF]])</li>
<li><span class="name">SoftwareAgent</span>: a software agent is a piece of software. </li>
</ul>
+<p>Furthermore, section <a href="#record-planLink">Plan Link Record</a>, introduces the idea of <em>plans</em> being associated with activities:</p>
+<ul>
+<li><span class="name">Plan</span>: agents of type <a >plan</a> are entities that represent a set of
+actions or steps intended to achieve some goal.</li>
+</ul>
<p>These types are mutually exclusive, though they do not cover all kinds of agent. </p>
+
<p>An agent record, noted <span class="name">agent(id, [ attr1=val1, ...])</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an identifier <span class="name">id</span> identifying an agent; the identifier of the agent record is defined to be the same as the identifier of the agent;</li>
@@ -1185,7 +1192,7 @@
<caption>PROV-DM Core Relation Summary</caption>
<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
<tr><td>Entity</td><td><a title="derivation record">wasDerivedFrom</a><br><a title="complementarity record">wasComplementOf</a></td><td><a title="generation record">wasGeneratedBy</a></td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
-<tr><td>Activity</td><td><a title="usage record">used</a></td><td>-</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="activity association record">wasAssociatedWith</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
+<tr><td>Activity</td><td><a title="usage record">used</a></td><td>-</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="activity association record">wasAssociatedWith</a><br><a title="plan link record">hadPlan</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Agent</td><td>-</td><td>-</td><td><a title="responsibility record">actedOnBehalfOf</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Note</td><td>-</td><td>-</td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
</table>
@@ -1487,12 +1494,84 @@
was started and ended by an agent, represented by record denoted by <span class="name">ah</span>, in "manual" mode, an application specific characterization of these relations.
</p>
</div>
-</section>
+
<div class="note">Temporal constraints for these relations remain to be
written. The temporal constraints should ensure that the agent started
its existence before the effect it may have on the activity. </div>
-
+</section>
+
+
+<section id="record-planLink">
+<h4>Plan Link Record</h4>
+
+<p>In the context of PROV-DM, a <dfn>plan</dfn> should be understood as a set of
+actions or steps intended to achieve some goal. PROV-DM is not
+prescriptive about the nature of plans, their representation, the
+actions and steps they consist of, and their intended goals. Hence,
+for the purpose of this specification, a plan can be a workflow for a
+scientific experiment, a recipe for a cooking activity, or a list of
+instructions for a micro-processor execution. While PROV-DM does not
+specify the representations of plans, it allows for activities to be
+associated with plans. Furthermore, since plans may evolve over time,
+it may become necessary to track their provenance, and hence, plans are
+entities. An activity MAY be associated with multiple plans. This
+allows for descriptions of activities initially associated with a
+plan, which was changed, on the fly, as the activity progresses. Plans
+can be successfully executed or they can fail. We expect applications
+to exploit PROV-DM <a href="#extensibility-section">extensibility
+mechanisms</a> to capture the rich nature of plans and associations
+between activities and plans.</p>
+
+
+<p>A
+<dfn>plan link record</dfn> is a representation of an association
+between an activity and a plan. It is a specialization of
+an <a>activity association record</a>. Hence, a plan is also a PROV-DM
+agent, by virtue of being associated with an activity (cf. constraint <a href="#association-agent">association-agent</a>).</p>
+
+
+
+
+<p>A plan link record, written <span class="name">hadPlan(id,a,e,attrs)</span> in PROV-ASN, contains:</p>
+<ul>
+<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the plan link record;</li>
+<li><em>activity</em>: an identifier <span class="name">a</span> denoting an activity record;
+<li><em>e</em>: an identifier <span class="name">e</span> for an entity, representing a plan;
+<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs <span class="name">attrs</span>, describing modalities of this relation.
+</ul>
+
+
+<div class='grammar'>
+<span class="nonterminal">planLink</span> ::=
+<span class="name">hadPlan</span>
+<span class="name">(</span>
+<span class="optional"> <span class="nonterminal">identifier</span>,</span>
+<span class="nonterminal">aIdentifier</span>,
+<span class="nonterminal">eIdentifier</span>
+<span class="nonterminal">optional-attribute-values</span>
+<span class="name">)</span>
+</div>
+
+
+<div class="anexample">
+<p>Below, we find assertions about
+activity <span class="name">ex:a2</span>. It is said to be associated
+with two plans <span class="name">ex:s1</span>
+and <span class="name">ex:s2</span>, two strategy documents at
+specific URLs. The first one is supersed, whereas the second, derived
+from the first, is the most recent.</p>
+<pre class="codeexample">
+entity(ex:s1,[prov:type="prov:Plan"%% xsd:QName, ex:label="Communication Strategy 1",
+ ex:url="http://example.org/strategy1.html" %% xsd:anyURI])
+entity(ex:s2,[prov:type="prov:Plan"%% xsd:QName, ex:label="Communication Strategy 2",
+ ex:url="http://example.org/strategy2.html" %% xsd:anyURI])
+wasDerivedFrom(ex:s2,ex:s1)
+hadPlan(ex:a2, ex:s1,[ex:kind="supersed"])
+hadPlan(ex:a2, ex:s2,[ex:kind="newest"])
+</pre>
+</div>
+</section>
<!--
@@ -2136,7 +2215,7 @@
<pre class="codexample">
entity(e1,[prov:type="document"])
entity(e2,[prov:type="document"])
-activity(a,transform,t1,t2,[])
+activity(a,t1,t2)
used(u1,a,e1,[ex:file="stdin"])
wasGeneratedBy(e2, a, [ex:file="stdout"])
@@ -2215,9 +2294,9 @@
...
wasDerivedFrom(e2,e1)
...
- activity(a0,create-file,t)
+ activity(a0,t,,[prov:type="createFile"])
...
- wasGeneratedBy(e0,a0,[])
+ wasGeneratedBy(e0,a0)
...
wasAssociatedWith(a4, ag5, [prov:role="communicator"]) )
</pre>
@@ -2270,7 +2349,7 @@
http://example.org/asserter2,
entity(e0, [ prov:type="File", ex:path="/shared/crime.txt", ex:creator="Alice" ])
...
- activity(a1,create-file,t1)
+ activity(a1,t1,,[prov:type="createFile"])
...
wasGeneratedBy(e0,a1,[ex:fct="create"])
... )
@@ -2287,12 +2366,12 @@
account(ex:acc3,
http://example.org/asserter1,
entity(e0, [ prov:type="File", ex:path="/shared/crime.txt", ex:creator="Alice" ])
- activity(a0,create-file,t)
+ activity(a0,t,,[prov:type="createFile"])
wasGeneratedBy(e0,a0,[])
account(ex:acc4,
http://example.org/asserter2,
entity(e1, [ prov:type="File", ex:path="/shared/crime.txt", ex:creator="Alice", ex:content="" ])
- activity(a0,copy-file,t)
+ activity(a0,t,,[prov:type="copyFile"])
wasGeneratedBy(e1,a0,[ex:fct="create"])
wasComplementOf(e1,e0)))
</pre>
@@ -2547,6 +2626,7 @@
</section>
+<!--
<section id="record-RecipeLink">
<h3>Recipe Link</h3>
@@ -2582,7 +2662,7 @@
</section>
-
+-->
@@ -2915,8 +2995,8 @@
<p>
In the following assertions, we find two activity records, identified by <span class="name">a1</span> and <span class="name">a2</span>, representing two activities, which took place on two separate hosts. The third record indicates that the latter activity was started by the former.</p>
<pre class="codeexample">
-activity(a1,workflow,t1,t2,[ex:host="server1.example.org"])
-activity(a2,sub-workflow,t3,t4,[ex:host="server2.example.org"])
+activity(a1,t1,t2,[ex:host="server1.example.org",prov:type="workflow"])
+activity(a2,t3,t4,[ex:host="server2.example.org",prov:type="subworkflow"])
wasStartedBy(a2,a1)
</pre>
@@ -3056,7 +3136,7 @@
<span class="name">e</span> and <span class="name">ag</span>,
<span class='conditional'>then</span> there exists an activity identified by <span class="name">pe</span> such that the following statements hold:
<pre>
-activity(pe,recipe,t1,t2,attr1)
+activity(pe,t1,t2,attr1)
wasGenerateBy(e,pe)
wasAssociatedWith(pe,ag,attr2)
</pre>
@@ -3190,76 +3270,146 @@
<section id="interpretation">
<h2>PROV-DM Interpretation</h2>
-<div class="note">
-Work in progress: we are consolidating here all interpretation constraints. Need to recap some of the overview material about events. </div>
-
-<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since an <a>activity start event</a> always <a>precedes</a> the corresponding <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'> The following temporal constraint holds for any activity record: the
+<p>Section <a href="#section-time-event">section-time-event</a>
+introduced a notion of <a title="event">instantaneous event</a>
+marking changes in the world, in its activities and entities. PROV-DM
+identifies four kinds of events, namely <a>entity generation
+event</a>, <a>entity usage event</a>, <a>activity start event</a>
+and <a>activity end event</a>. PROV-DM adopts Lamport's clock
+assumptions [[CLOCK]] in the form of a partial order <a>follows</a>
+(and its inverse <a>precedes</a>) between events. Furthermore,
+PROV-DM assumes the existence of a mapping from events to time clocks,
+though the actual mapping is not in scope of this specification.</p>
+
+<p>Given that provenance records offer a description of past entities
+and activities, to be meaningful provenance records MUST
+satisfy <em>event ordering constraints</em>, which we introduce in
+this section. For instance, an entity can only be used after it was
+generated; hence, we say that an entity's <a title="entity generation
+event">generation event</a> precedes any of this
+entity's <a title="entity usage event">usage event</a>. Should this
+ordering constraint be proven invalid, the associated generation and
+usage records could not be credible. The rest of this section defines
+the <dfn>temporal interpretation</dfn> of provenance records as the
+set of event ordering constraints associated with provenance
+records. </p>
+
+
+<p>PROV-DM also allows for time observations to be inserted in
+specific provenance records, for each of the four kinds
+of <a title="event">events</a> introduced in this specification. The
+presence of a time observation for a given <a>event</a> fixes the
+mapping of this <a>event</a> to the timeline. The presence of time
+information in a provenance instantiates the ordering constraint with
+that time information. It is expected that such instantiated
+constraint can help corroborate provenance information. We anticipate
+that verification algorithms could be developed though this
+verification is outside the scope of this specfication.
+</p>
+
+<p>The following figure summarizes the ordering constraints in a
+graphical manner. For each subfigure, an event time line points to the
+right. Activities are represented by rectangles, whereas entities are
+represented by circles. Usage, generation and derivation records are
+represented by the corresponding edges between entities and
+activities. The four kind of events are represented by vertical
+dotted lines (adjacent to the vertical sides of an activity's
+rectangle, or intersecting usage and generation edges). The ordering
+constraints are represented by triangles.</p>
+
+<div style="text-align: center;">
+<img src="constraints.png" alt="constraints between events" />
+<figcaption id="constraint-summary">Summary of event ordering constraints</figcaption>
+</div>
+
+
+<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since an <a>activity start event</a> always <a>precedes</a> the corresponding <a>activity end event</a>. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (a) and expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
+
+<div class='interpretation' id='start-precedes-end'> The following ordering constraint holds for any activity record: the
<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a>.</div>
-<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,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
+<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world, since the corresponding event had to occur during the associated activity. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (c) and expressed by constraint <a href="#generation-activity-ordering">generation-activity-ordering</a>.</p>
+
+<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following ordering constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
of <span class="name">a</span> and <a>follows</a> the <a title="activity start event">start</a> of <span class="name">a</span>.
</div>
-<p>The assertion of a usage record implies ordering of <a title="event">events</a> in the world.</p>
-
-<div class='interpretation' id='usage-generation-ordering'>For any entity, the following temporal constraint holds: the <a title="entity generation event">generation</a> of an entity always <a>precedes</a> any of its <a title="entity usage event">usages</a>.
-</div>
-
+
+<p>The assertion of a usage record implies ordering of <a title="event">events</a> in the world, since the corresponding event had to occur during the associated activity. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (e) and expressed by constraint <a href="#usage-activity-ordering">usage-activity-ordering</a>.</p>
<div class='interpretation' id='usage-activity-ordering'>Given an activity record identified by <span class="name">a</span>, an entity record identified by <span class="name">e</span>, a set of attribute-value pairs <span class="name">attrs</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
- assertion <span class="name">used(a,e,attrs)</span> or <span class="name">used(a,e,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint holds:
+ assertion <span class="name">used(a,e,attrs)</span> or <span class="name">used(a,e,attrs,t)</span> holds, <span class='conditional'>then</span> the following ordering constraint holds:
the <a title="entity usage event">usage</a> of the entity represented by entity record identified by <span class="name">e</span> <a>precedes</a> the <a title="activity end event">end</a> of activity represented by record identified by <span class="name">a</span> and <a>follows</a> its <a title="activity start event">start</a>.
</div>
-
-<p>
+<p>Furthemore, assertion of a usage record and a generation record for a given entity implies ordering of <a title="event">events</a> in the world, since the <a title="entity generation event">generation event</a> had to precede the <a title="entity usage event">usage event</a>. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (b) and expressed by constraint <a href="#usage-generation-ordering">usage-generation-ordering</a>.</p>
+
+<div class='interpretation' id='usage-generation-ordering'>For any entity, the following ordering constraint holds: the <a title="entity generation event">generation</a> of an entity always <a>precedes</a> any of its <a title="entity usage event">usages</a>.
+</div>
+
+
<p>If a derivation record holds for <span class="name">e2</span> and <span class="name">e1</span>, then
-this means that the entity represented by entity record identified by <span class="name">e1</span> has an influence on the entity represented entity record identified by <span class="name">e2</span>,
- which at the minimum implies temporal ordering, specified as follows.
-First, we consider one-activity derivations.</p>
+this means that the entity <span class="name">e1</span> had some form of influence on the entity <span class="name">e2</span>; for this to be possible, some event ordering must be satisfied.
+First, we consider one-activity derivations. In that case, the <a title="entity usage event">usage</a> of <span class="name">e1</span> has to precede the <a title="entity generation event">generation</a> of <span class="name">e2</span>.
+This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (d) and expressed by constraint <a href="#derivation-usage-generation-ordering">derivation-usage-generation-ordering</a>.</p>
+
<div class='interpretation' id='derivation-usage-generation-ordering'>Given an activity record identified by <span class="name">a</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, <span class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,a,g2,u1,attrs)</span>
or <span class="name">wasDerivedFrom(e2,e1,[prov:steps="1"] ∪ attrs)</span> holds, <span class='conditional'>then</span>
-the following temporal constraint holds:
+the following ordering constraint holds:
the <a title="entity usage event">usage</a>
of entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation</a> of
the entity denoted by <span class="name">e2</span>.
</div>
-<p>Then, imprecise-n derivations.</p>
+<p>For imprecise-n derivations, a similar constraint exists, but in this case, no usage record can be inferred for <span class="name">e1</span>. Instead, the constraint refers to its generation event, as
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (f) and expressed by constraint <a href="#derivation-generation-generation-ordering">derivation-generation-generation-ordering</a>.</p>
<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">wasDerivedFrom(e2,e1,[prov:steps="n"] ∪ attrs)</span>
- holds, <span class='conditional'>then</span> the following temporal constraint holds:
+ holds, <span class='conditional'>then</span> the following ordering constraint holds:
the <a title="entity generation event">generation event</a> of the entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a> of
the entity denoted by <span class="name">e2</span>.
</div>
-<p>Note that temporal ordering is between generations of <span class="name">e1</span>
+<p>Note that event ordering is between generations of <span class="name">e1</span>
and <span class="name">e2</span>, as opposed to precise-1 derivation,
-which implies temporal ordering between the usage of <span class="name">e1</span> and
+which implies ordering ordering between the usage of <span class="name">e1</span> and
generation of <span class="name">e2</span>. Indeed, in the case of
imprecise-n derivation, nothing is known about the usage of <span class="name">e1</span>,
since there is no associated activity.</p>
+<p>The assertion of an information flow ordering record between two activities of <span class="name">a1</span> and <span class="name">a2</span> also implies ordering of <a title="event">events</a> in the world, since some entity must have been generated by the former and used by the later, which implies that the start event of <span class="name">a1</span> cannot follow the end event of <span class="name">a2</span>. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (g) and expressed by constraint <a href="#wasInformedBy-ordering">wasInformedBy-ordering</a>.</p>
+
<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 following temporal constraint holds:
+ holds, <span class='conditional'>then</span> the following ordering constraint holds:
the <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>
+<p>The assertion of a control flow ordering record between two activities of <span class="name">a1</span> and <span class="name">a2</span> also implies ordering of <a title="event">events</a> in the world, since <span class="name">a1</span> must have been active before <span class="name">a2</span> started. This is
+illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (h) and expressed by constraint <a href="#wasStartedBy-ordering">wasStartedBy-ordering</a>.</p>
+
+
<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 following temporal constraint holds: the
+ holds, <span class='conditional'>then</span> the following ordering constraint holds: the
<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>
+<div class="note">
+For completeness, we should define ordering constraint for wasAssociatedWith and actedOnBehalfOf.
+For wasAssociatedWith(a,ag), it feels that ag must have some overlap with a.
+For actedOnBehalfOf(ag1,ag2,a), it seem that ag2 should have existed before the overlap between ag1 and a.
+</div>
</section>
@@ -3392,6 +3542,8 @@
<section class="appendix">
<h2>Changes Since Second Public Working Draft</h2>
<ul>
+<li>12/13/11: Introduced hadPlan as a specialization of wasAssociatedWith. </li>
+<li>12/12/11: Section 7 on interpretation. </li>
<li>12/08/11: Restructuring of Constraints. </li>
</ul>
</section>
Binary file model/constraints.png has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/constraints.svg Wed Dec 14 00:11:16 2011 +0000
@@ -0,0 +1,2622 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="744.09448819"
+ height="1052.3622047"
+ id="svg6710"
+ version="1.1"
+ inkscape:version="0.47 r22583"
+ sodipodi:docname="constraints.svg"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/constraints.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <defs
+ id="defs6712">
+ <inkscape:path-effect
+ effect="skeletal"
+ id="path-effect6032"
+ is_visible="true"
+ pattern="M 0,5 C 0,2.24 2.24,0 5,0 7.76,0 10,2.24 10,5 10,7.76 7.76,10 5,10 2.24,10 0,7.76 0,5 z"
+ copytype="single_stretched"
+ prop_scale="1"
+ scale_y_rel="false"
+ spacing="0"
+ normal_offset="0"
+ tang_offset="0"
+ prop_units="false"
+ vertical_pattern="false"
+ fuse_tolerance="0" />
+ <inkscape:path-effect
+ effect="spiro"
+ id="path-effect6030"
+ is_visible="true" />
+ <inkscape:path-effect
+ effect="spiro"
+ id="path-effect6026"
+ is_visible="true" />
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057" />
+ </linearGradient>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0.0"
+ refX="0.0"
+ id="Arrow1Lend"
+ style="overflow:visible;">
+ <path
+ id="path4091"
+ d="M 0.0,0.0 L 5.0,-5.0 L -12.5,0.0 L 5.0,5.0 L 0.0,0.0 z "
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1.0pt;marker-start:none;"
+ transform="scale(0.8) rotate(180) translate(12.5,0)" />
+ </marker>
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 526.18109 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="744.09448 : 526.18109 : 1"
+ inkscape:persp3d-origin="372.04724 : 350.78739 : 1"
+ id="perspective6718" />
+ <inkscape:perspective
+ id="perspective6728"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective6728-3"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective6794"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective6840"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective6877"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective6959"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective8909"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="Arrow1Lend-2"
+ style="overflow:visible">
+ <path
+ id="path4091-9"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective8937"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="Arrow1Lend-4"
+ style="overflow:visible">
+ <path
+ id="path4091-0"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943"
+ style="overflow:visible">
+ <path
+ id="path8945"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective3000"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="Arrow1Lend-9"
+ style="overflow:visible">
+ <path
+ id="path4091-1"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker3006"
+ style="overflow:visible">
+ <path
+ id="path3008"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker3010"
+ style="overflow:visible">
+ <path
+ id="path3012"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker3014"
+ style="overflow:visible">
+ <path
+ id="path3016"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-9"
+ style="overflow:visible">
+ <path
+ id="path8945-6"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053"
+ id="linearGradient4059"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805"
+ gradientUnits="userSpaceOnUse" />
+ <inkscape:perspective
+ id="perspective4069"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-96"
+ style="overflow:visible">
+ <path
+ id="path8945-61"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective4555"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3"
+ style="overflow:visible">
+ <path
+ id="path8945-0"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3" />
+ </linearGradient>
+ <inkscape:perspective
+ id="perspective4663"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective4930"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective4952"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-5"
+ id="linearGradient4714-7"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-5">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-8" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-9" />
+ </linearGradient>
+ <inkscape:perspective
+ id="perspective5046"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3-7"
+ style="overflow:visible">
+ <path
+ id="path8945-0-7"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-92"
+ style="overflow:visible">
+ <path
+ id="path8945-2"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-9"
+ id="linearGradient4714-4"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-9">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-7" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-94" />
+ </linearGradient>
+ <linearGradient
+ y2="126.8805"
+ x2="139.6636"
+ y1="108.27257"
+ x1="114.53841"
+ gradientUnits="userSpaceOnUse"
+ id="linearGradient4961-4"
+ xlink:href="#linearGradient4053-6-5-8"
+ inkscape:collect="always" />
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-5-8">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-8-7" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-9-2" />
+ </linearGradient>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6"
+ id="linearGradient5189"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-5"
+ id="linearGradient5191"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <inkscape:perspective
+ id="perspective5442"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3-2"
+ style="overflow:visible">
+ <path
+ id="path8945-0-79"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-6"
+ style="overflow:visible">
+ <path
+ id="path8945-64"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-5-3">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-8-3" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-9-8" />
+ </linearGradient>
+ <inkscape:perspective
+ id="perspective5643"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3-8"
+ style="overflow:visible">
+ <path
+ id="path8945-0-77"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-5-3"
+ id="linearGradient5711"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <inkscape:perspective
+ id="perspective5745"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3-71"
+ style="overflow:visible">
+ <path
+ id="path8945-0-4"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-97"
+ style="overflow:visible">
+ <path
+ id="path8945-8"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-5-3-7">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-8-3-2" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-9-8-2" />
+ </linearGradient>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker5757"
+ style="overflow:visible">
+ <path
+ id="path5759"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-5-3-7"
+ id="linearGradient5901"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <inkscape:perspective
+ id="perspective5927"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective5970"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective5992"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective6486"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker5757-4"
+ style="overflow:visible">
+ <path
+ id="path5759-4"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3-86"
+ style="overflow:visible">
+ <path
+ id="path8945-0-9"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-60"
+ style="overflow:visible">
+ <path
+ id="path8945-7"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker6500"
+ style="overflow:visible">
+ <path
+ id="path6502"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective6718-1"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-3-9"
+ style="overflow:visible">
+ <path
+ id="path8945-0-93"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-90"
+ style="overflow:visible">
+ <path
+ id="path8945-4"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-5-3-7-5"
+ id="linearGradient5901-1"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-5-3-7-5">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-8-3-2-28" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-9-8-2-1" />
+ </linearGradient>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker6730"
+ style="overflow:visible">
+ <path
+ id="path6732"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker5757-7"
+ style="overflow:visible">
+ <path
+ id="path5759-6"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective7216"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-929"
+ style="overflow:visible">
+ <path
+ id="path8945-80"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-9-8">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-7-7" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-94-2" />
+ </linearGradient>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-92-3"
+ style="overflow:visible">
+ <path
+ id="path8945-2-6"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective7402"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective7424"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-92-2"
+ style="overflow:visible">
+ <path
+ id="path8945-2-8"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <inkscape:perspective
+ id="perspective7452"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective7480"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-9-8"
+ id="linearGradient7514"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <inkscape:perspective
+ id="perspective7727"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-2"
+ style="overflow:visible">
+ <path
+ id="path8945-82"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ id="linearGradient4053-6-9-8-3">
+ <stop
+ style="stop-color:#f19353;stop-opacity:1;"
+ offset="0"
+ id="stop4055-8-7-7-1" />
+ <stop
+ style="stop-color:#f19353;stop-opacity:0;"
+ offset="1"
+ id="stop4057-3-94-2-7" />
+ </linearGradient>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker8943-92-0"
+ style="overflow:visible">
+ <path
+ id="path8945-2-9"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <marker
+ inkscape:stockid="Arrow1Lend"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="marker7739"
+ style="overflow:visible">
+ <path
+ id="path7741"
+ d="M 0,0 5,-5 -12.5,0 5,5 0,0 z"
+ style="fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none"
+ transform="matrix(-0.8,0,0,-0.8,-10,0)" />
+ </marker>
+ <linearGradient
+ inkscape:collect="always"
+ xlink:href="#linearGradient4053-6-9-8-3"
+ id="linearGradient7925"
+ gradientUnits="userSpaceOnUse"
+ x1="114.53841"
+ y1="108.27257"
+ x2="139.6636"
+ y2="126.8805" />
+ <inkscape:perspective
+ id="perspective7943"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective7968"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective7997"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective8022"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective8047"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ <inkscape:perspective
+ id="perspective8072"
+ inkscape:persp3d-origin="0.5 : 0.33333333 : 1"
+ inkscape:vp_z="1 : 0.5 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_x="0 : 0.5 : 1"
+ sodipodi:type="inkscape:persp3d" />
+ </defs>
+ <sodipodi:namedview
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="0.71458288"
+ inkscape:cx="372.04724"
+ inkscape:cy="526.18109"
+ inkscape:document-units="px"
+ inkscape:current-layer="g8502"
+ showgrid="false"
+ inkscape:window-width="1280"
+ inkscape:window-height="1003"
+ inkscape:window-x="0"
+ inkscape:window-y="0"
+ inkscape:window-maximized="1"
+ showguides="true"
+ inkscape:guide-bbox="true" />
+ <metadata
+ id="metadata6715">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ <dc:title></dc:title>
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Layer 1"
+ inkscape:groupmode="layer"
+ id="layer1">
+ <g
+ id="g8502"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ sodipodi:nodetypes="csc"
+ id="path6912"
+ d="m 603.93499,539.09188 c 0,0 -12.93587,10.62589 -36.12693,-7.28384 -17.5161,-13.52713 -27.3689,-29.13535 -27.3689,-29.13535"
+ style="fill:none;stroke:#000000;stroke-width:0.92256683;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:url(#marker5757-7)"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <g
+ id="g5585"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ id="path6949"
+ d="m 205.48904,21.15029 c 0,139.42782 0,139.12603 0,139.12603"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1.99999999, 1.99999999;stroke-dashoffset:0" />
+ <path
+ id="path6949-9"
+ d="m 94.931401,21.15029 c 0,139.42782 0,139.12603 0,139.12603"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1.99999999, 1.99999999;stroke-dashoffset:0" />
+ <rect
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2923"
+ width="109.65764"
+ height="37.468384"
+ x="95.381401"
+ y="51.987629" />
+ <g
+ id="g2917"
+ transform="matrix(0.6,0,0,0.6,-93.834021,-107.61567)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-5"
+ y="303.30817"
+ x="391.29538"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ id="tspan2915"
+ sodipodi:role="line"
+ x="391.29538"
+ y="303.30817">a</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-4"
+ y="303.74017"
+ x="409.47354"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="303.74017"
+ x="409.47354"
+ id="tspan2843-8"
+ sodipodi:role="line" /></text>
+ </g>
+ <path
+ id="path6941"
+ d="m 39.624089,39.058357 c 220.836191,0 221.172261,0.005 221.172261,0.005"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ sodipodi:nodetypes="cc" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text6943"
+ y="35.829124"
+ x="31.395864"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="35.829124"
+ x="31.395864"
+ id="tspan6945"
+ sodipodi:role="line"
+ style="font-size:9.60000038px">Event line</tspan></text>
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient4059);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,23.611065,53.194293)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="37.824203"
+ y="113.98219"
+ id="text3211"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3213"
+ x="37.824203"
+ y="113.98219">start of a</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="207.77724"
+ y="113.98219"
+ id="text3215"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3217"
+ x="207.77724"
+ y="113.98219">end of a</tspan></text>
+ <path
+ id="path6941-7"
+ d="m 39.624091,132.87891 c 220.836189,0 221.172259,0.005 221.172259,0.005"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ sodipodi:nodetypes="cc" />
+ </g>
+ <g
+ transform="translate(0,-32)"
+ id="g5005"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline"
+ d="M 178.66438,327.24598 116.84854,302.129"
+ id="path4716"
+ inkscape:connector-type="polyline"
+ inkscape:connection-start="#g4705" />
+ <path
+ id="path6949-5"
+ d="m 205.48904,234.75007 c 0,164.59929 0,164.24301 0,164.24301"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <path
+ id="path6949-9-7"
+ d="m 94.931401,234.75007 c 0,164.59929 0,164.24301 0,164.24301"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <rect
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2923-2"
+ width="109.65764"
+ height="37.468384"
+ x="95.381401"
+ y="265.5874" />
+ <g
+ id="g2917-0"
+ transform="matrix(0.6,0,0,0.6,-101.83402,105.98411)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-5-7"
+ y="303.30817"
+ x="391.29538"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ id="tspan2915-3"
+ sodipodi:role="line"
+ x="391.29538"
+ y="303.30817">a</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-4-8"
+ y="303.74017"
+ x="409.47354"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="303.74017"
+ x="409.47354"
+ id="tspan2843-8-72"
+ sodipodi:role="line" /></text>
+ </g>
+ <path
+ id="path6941-1"
+ d="m 39.624089,252.65814 c 220.836191,0 221.172261,0.005 221.172261,0.005"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ sodipodi:nodetypes="cc" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text6943-33"
+ y="249.42891"
+ x="31.395864"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="249.42891"
+ x="31.395864"
+ id="tspan6945-9"
+ sodipodi:role="line"
+ style="font-size:9.60000038px">Event line</tspan></text>
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient5189);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209-5"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,-4.388935,290.79407)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="37.824203"
+ y="327.58197"
+ id="text3211-3"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3213-2"
+ x="37.824203"
+ y="327.58197">start of a</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="207.77724"
+ y="327.58197"
+ id="text3215-4"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3217-8"
+ x="207.77724"
+ y="327.58197">end of a</tspan></text>
+ <path
+ id="path6941-7-3"
+ d="m 39.624091,370.47869 c 220.836189,0 221.172259,0.005 221.172259,0.005"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ sodipodi:nodetypes="cc" />
+ <g
+ id="g4705"
+ transform="matrix(0.85747563,0,0,0.85747563,-210.50872,92.524119)">
+ <path
+ sodipodi:type="arc"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path2816-5-4"
+ sodipodi:cx="93.832016"
+ sodipodi:cy="294.48819"
+ sodipodi:rx="31.75853"
+ sodipodi:ry="31.75853"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ transform="matrix(0.45261198,0,0,0.45261198,411.38959,140.44702)" />
+ <g
+ transform="matrix(0.45261198,0,0,0.45261198,408.11357,146.768)"
+ id="g2845-6-0">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="91.530045"
+ y="289.34262"
+ id="text2835-6-4"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2837-3-0"
+ x="91.530045"
+ y="289.34262">e<tspan
+ style="font-size:20px"
+ id="tspan2839-3-5" /></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="107.70822"
+ y="289.77463"
+ id="text2841-1-3"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-2-5"
+ x="107.70822"
+ y="289.77463"
+ style="font-size:18px" /></text>
+ </g>
+ </g>
+ <path
+ id="path6949-5-0"
+ d="m 148.26181,234.75007 c 0,164.59929 0,164.24301 0,164.24301"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient5191);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209-5-8"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,50.814112,290.79407)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="122.97539"
+ y="323.93674"
+ id="text4999"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan5001"
+ x="122.97539"
+ y="323.93674">gen.</tspan><tspan
+ sodipodi:role="line"
+ x="122.97539"
+ y="337.93674"
+ id="tspan5003">of e</tspan></text>
+ </g>
+ <g
+ id="g6677"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ id="path6949-5-1"
+ d="m 205.48904,417.35914 c 0,164.59929 0,164.24301 0,164.24301"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <path
+ id="path6949-9-7-5"
+ d="m 94.931401,417.35914 c 0,164.59929 0,164.24301 0,164.24301"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <rect
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2923-2-5"
+ width="109.65764"
+ height="37.468384"
+ x="95.381401"
+ y="494.19647" />
+ <g
+ id="g2917-0-4"
+ transform="matrix(0.6,0,0,0.6,-101.83402,334.59318)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-5-7-4"
+ y="303.30817"
+ x="391.29538"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ id="tspan2915-3-5"
+ sodipodi:role="line"
+ x="391.29538"
+ y="303.30817">a</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-4-8-9"
+ y="303.74017"
+ x="409.47354"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="303.74017"
+ x="409.47354"
+ id="tspan2843-8-72-0"
+ sodipodi:role="line" /></text>
+ </g>
+ <path
+ id="path6941-1-8"
+ d="m 39.624089,435.26721 c 220.836191,0 221.172261,0.005 221.172261,0.005"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ sodipodi:nodetypes="cc" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text6943-33-9"
+ y="432.03799"
+ x="31.395864"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="432.03799"
+ x="31.395864"
+ id="tspan6945-9-8"
+ sodipodi:role="line"
+ style="font-size:9.60000038px">Event line</tspan></text>
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient4714-4);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209-5-81"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,-4.388935,473.40314)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="37.824203"
+ y="516.19104"
+ id="text3211-3-0"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3213-2-4"
+ x="37.824203"
+ y="516.19104">start of a</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="207.77724"
+ y="516.19104"
+ id="text3215-4-8"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3217-8-7"
+ x="207.77724"
+ y="516.19104">end of a</tspan></text>
+ <path
+ id="path6941-7-3-5"
+ d="m 39.624091,553.08776 c 220.836189,0 221.172259,0.005 221.172259,0.005"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ sodipodi:nodetypes="cc" />
+ <g
+ id="g4705-1"
+ transform="matrix(0.85747563,0,0,0.85747563,-268.50872,231.13319)">
+ <path
+ sodipodi:type="arc"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path2816-5-4-9"
+ sodipodi:cx="93.832016"
+ sodipodi:cy="294.48819"
+ sodipodi:rx="31.75853"
+ sodipodi:ry="31.75853"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ transform="matrix(0.45261198,0,0,0.45261198,411.38959,140.44702)" />
+ <g
+ transform="matrix(0.45261198,0,0,0.45261198,408.11357,146.768)"
+ id="g2845-6-0-9">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="91.530045"
+ y="289.34262"
+ id="text2835-6-4-2"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2837-3-0-7"
+ x="91.530045"
+ y="289.34262">e<tspan
+ style="font-size:20px"
+ id="tspan2839-3-5-0" /></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="107.70822"
+ y="289.77463"
+ id="text2841-1-3-6"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-2-5-1"
+ x="107.70822"
+ y="289.77463"
+ style="font-size:18px" /></text>
+ </g>
+ </g>
+ <path
+ id="path6949-5-0-8"
+ d="m 148.26181,417.35914 c 0,164.59929 0,164.24301 0,164.24301"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient4961-4);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209-5-8-3"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,50.814112,473.40314)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="149.95467"
+ y="452.95712"
+ id="text4999-5"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan5001-9"
+ x="149.95467"
+ y="452.95712">initiated</tspan><tspan
+ sodipodi:role="line"
+ x="149.95467"
+ y="466.95712"
+ id="tspan3228">usage</tspan><tspan
+ sodipodi:role="line"
+ x="149.95467"
+ y="480.95712"
+ id="tspan5003-8">of e</tspan></text>
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:url(#marker8943-92)"
+ d="M 178.46189,494.64502 133.97882,469.49088"
+ id="path5224"
+ inkscape:connector-type="polyline" />
+ </g>
+ <g
+ id="g5713"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline"
+ d="M 541.0127,73.249296 493.75431,46.312625"
+ id="path4716-3"
+ inkscape:connector-type="polyline" />
+ <path
+ id="path6949-5-9"
+ d="m 578.408,21.15029 c 0,128.9879 0,128.7087 0,128.7087"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <path
+ id="path6949-9-7-2"
+ d="m 515.85036,21.15029 c 0,128.9879 0,128.7087 0,128.7087"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2, 2;stroke-dashoffset:0" />
+ <path
+ id="path6941-1-1"
+ d="m 432.54305,39.05836 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ sodipodi:nodetypes="cc" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text6943-33-6"
+ y="35.829128"
+ x="424.31482"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="35.829128"
+ x="424.31482"
+ id="tspan6945-9-6"
+ sodipodi:role="line"
+ style="font-size:9.60000038px">Event line</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="583.40753"
+ y="74.536339"
+ id="text3215-4-3"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3217-8-3"
+ x="583.40753"
+ y="74.536339">initiated</tspan><tspan
+ sodipodi:role="line"
+ x="583.40753"
+ y="88.536339"
+ id="tspan3222">usage of e</tspan></text>
+ <path
+ id="path6941-7-3-0"
+ d="m 432.54305,130.87891 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ sodipodi:nodetypes="cc" />
+ <g
+ id="g4705-9"
+ transform="matrix(0.85747563,0,0,0.85747563,157.95605,-159.47257)">
+ <path
+ sodipodi:type="arc"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path2816-5-4-1"
+ sodipodi:cx="93.832016"
+ sodipodi:cy="294.48819"
+ sodipodi:rx="31.75853"
+ sodipodi:ry="31.75853"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ transform="matrix(0.45261198,0,0,0.45261198,411.38959,140.44702)" />
+ <g
+ transform="matrix(0.45261198,0,0,0.45261198,408.11357,146.768)"
+ id="g2845-6-0-6">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="91.530045"
+ y="289.34262"
+ id="text2835-6-4-3"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2837-3-0-4"
+ x="91.530045"
+ y="289.34262">e<tspan
+ style="font-size:20px"
+ id="tspan2839-3-5-00" /></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="107.70822"
+ y="289.77463"
+ id="text2841-1-3-0"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-2-5-4"
+ x="107.70822"
+ y="289.77463"
+ style="font-size:18px" /></text>
+ </g>
+ </g>
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient5711);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209-5-8-0"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,420.53,51.194293)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="443.69424"
+ y="77.94664"
+ id="text4999-4"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ x="443.69424"
+ y="77.94664"
+ id="tspan5003-9">completed</tspan><tspan
+ sodipodi:role="line"
+ x="443.69424"
+ y="77.94664"
+ id="tspan3220">generation</tspan><tspan
+ sodipodi:role="line"
+ x="443.69424"
+ y="91.94664"
+ id="tspan5700">of e</tspan></text>
+ <path
+ style="fill:none;stroke:#000000;stroke-width:0.99999994px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline"
+ d="M 598.64833,104.67512 559.76047,81.37781"
+ id="path4716-3-7"
+ inkscape:connector-type="polyline" />
+ </g>
+ <g
+ id="g6539"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline"
+ d="M 541.0127,278.84908 493.75431,251.9124"
+ id="path4716-3-9"
+ inkscape:connector-type="polyline" />
+ <path
+ id="path6949-5-9-1"
+ d="m 578.408,202.75006 c 0,155.65407 0,155.31715 0,155.31715"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1.99999997, 1.99999997;stroke-dashoffset:0" />
+ <path
+ id="path6949-9-7-2-8"
+ d="m 515.85036,202.75006 c 0,155.65407 0,155.31715 0,155.31715"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1.99999997, 1.99999997;stroke-dashoffset:0" />
+ <path
+ id="path6941-1-1-2"
+ d="m 432.54305,220.65814 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ sodipodi:nodetypes="cc" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text6943-33-6-8"
+ y="217.42891"
+ x="424.31482"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="217.42891"
+ x="424.31482"
+ id="tspan6945-9-6-5"
+ sodipodi:role="line"
+ style="font-size:9.60000038px">Event line</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="579.40753"
+ y="282.13611"
+ id="text3215-4-3-9"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3217-8-3-6"
+ x="579.40753"
+ y="282.13611">completed</tspan><tspan
+ sodipodi:role="line"
+ x="579.40753"
+ y="296.13611"
+ id="tspan3226">generation of e2</tspan></text>
+ <path
+ id="path6941-7-3-0-9"
+ d="m 432.54305,336.47869 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ sodipodi:nodetypes="cc" />
+ <g
+ id="g5910">
+ <path
+ sodipodi:type="arc"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path2816-5-4-1-8"
+ sodipodi:cx="93.832016"
+ sodipodi:cy="294.48819"
+ sodipodi:rx="31.75853"
+ sodipodi:ry="31.75853"
+ d="m 125.59055,294.48819 a 31.75853,31.75853 0 1 1 -63.517064,0 31.75853,31.75853 0 1 1 63.517064,0 z"
+ transform="matrix(0.38810374,0,0,0.38810374,444.7126,130.55711)" />
+ <g
+ transform="matrix(0.38810374,0,0,0.38810374,438.62243,135.97719)"
+ id="g2845-6-0-6-8">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="91.530045"
+ y="289.34262"
+ id="text2835-6-4-3-2"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2837-3-0-4-5"
+ x="91.530045"
+ y="289.34262">e1<tspan
+ style="font-size:20px"
+ id="tspan2839-3-5-00-0" /></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="107.70822"
+ y="289.77463"
+ id="text2841-1-3-0-7"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-2-5-4-2"
+ x="107.70822"
+ y="289.77463"
+ style="font-size:18px" /></text>
+ </g>
+ </g>
+ <path
+ sodipodi:type="star"
+ style="fill:url(#linearGradient5901);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path3209-5-8-0-1"
+ sodipodi:sides="3"
+ sodipodi:cx="120.80072"
+ sodipodi:cy="116.88141"
+ sodipodi:r1="23.193739"
+ sodipodi:r2="11.596869"
+ sodipodi:arg1="0"
+ sodipodi:arg2="1.0471976"
+ inkscape:flatsided="true"
+ inkscape:rounded="0"
+ inkscape:randomized="0"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ transform="matrix(1,0,0,0.68177752,420.53,256.79407)" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="445.69424"
+ y="283.54642"
+ id="text4999-4-1"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ x="445.69424"
+ y="283.54642"
+ id="tspan5700-0">initiated</tspan><tspan
+ sodipodi:role="line"
+ x="445.69424"
+ y="297.54642"
+ id="tspan3224">usage of e1</tspan></text>
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline"
+ d="M 598.64832,310.27491 561.40859,291.138"
+ id="path4716-3-7-4"
+ inkscape:connector-type="polyline" />
+ <g
+ transform="translate(129.45902,71.445153)"
+ id="g5910-9">
+ <path
+ sodipodi:type="arc"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path2816-5-4-1-8-0"
+ sodipodi:cx="93.832016"
+ sodipodi:cy="294.48819"
+ sodipodi:rx="31.75853"
+ sodipodi:ry="31.75853"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ transform="matrix(0.38810374,0,0,0.38810374,444.7126,130.55711)" />
+ <g
+ transform="matrix(0.38810374,0,0,0.38810374,438.62243,135.97719)"
+ id="g2845-6-0-6-8-7">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="91.530045"
+ y="289.34262"
+ id="text2835-6-4-3-2-3"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2837-3-0-4-5-6"
+ x="91.530045"
+ y="289.34262">e2</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="107.70822"
+ y="289.77463"
+ id="text2841-1-3-0-7-6"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-2-5-4-2-9"
+ x="107.70822"
+ y="289.77463"
+ style="font-size:18px" /></text>
+ </g>
+ </g>
+ <rect
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2923-0-2"
+ width="37.086308"
+ height="37.468384"
+ x="526.94922"
+ y="265.12067" />
+ <g
+ id="g2917-7-2"
+ transform="matrix(0.6,0,0,0.6,304.51594,107.16196)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-5-3-0"
+ y="303.30817"
+ x="391.29538"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ id="tspan2915-5-80"
+ sodipodi:role="line"
+ x="391.29538"
+ y="303.30817">a</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-4-4-7"
+ y="303.74017"
+ x="409.47354"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="303.74017"
+ x="409.47354"
+ id="tspan2843-8-7-7"
+ sodipodi:role="line" /></text>
+ </g>
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;stroke-miterlimit:4;stroke-dasharray:none;marker-end:url(#marker5757)"
+ d="m 610.8376,301.54097 c 0,0 4.62756,-30.07913 -27.76534,-50.90314 -31.65359,-20.34872 -90.23738,-11.56889 -90.23738,-11.56889"
+ id="path6036"
+ sodipodi:nodetypes="csc" />
+ </g>
+ <path
+ inkscape:connector-type="polyline"
+ id="path4716-3-9-0"
+ d="M 528.76661,481.08375 502.77836,440.62831"
+ style="fill:none;stroke:#000000;stroke-width:0.90879405px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1.99999997, 1.99999997;stroke-dashoffset:0"
+ d="m 578.408,417.35914 c 0,155.65407 0,155.31715 0,155.31715"
+ id="path6949-5-9-1-0"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1.99999997, 1.99999997;stroke-dashoffset:0"
+ d="m 515.85036,417.35914 c 0,155.65407 0,155.31715 0,155.31715"
+ id="path6949-9-7-2-8-8"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <path
+ sodipodi:nodetypes="cc"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ d="m 432.54305,435.26722 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ id="path6941-1-1-2-3"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="424.31482"
+ y="432.03799"
+ id="text6943-33-6-8-9"
+ sodipodi:linespacing="100%"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ style="font-size:9.60000038px"
+ sodipodi:role="line"
+ id="tspan6945-9-6-5-3"
+ x="424.31482"
+ y="432.03799">Event line</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text3215-4-3-9-3"
+ y="461.29361"
+ x="579.40753"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="461.29361"
+ x="579.40753"
+ id="tspan3217-8-3-6-8"
+ sodipodi:role="line">completed</tspan><tspan
+ y="475.29361"
+ x="579.40753"
+ sodipodi:role="line"
+ id="tspan3230">generation</tspan><tspan
+ id="tspan7150"
+ y="489.29361"
+ x="579.40753"
+ sodipodi:role="line">of e2</tspan></text>
+ <path
+ sodipodi:nodetypes="cc"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ d="m 432.54305,551.08777 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ id="path6941-7-3-0-9-4"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <g
+ transform="translate(54.567271,245.78696)"
+ id="g5910-6"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ transform="matrix(0.38810374,0,0,0.38810374,444.7126,130.55711)"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ sodipodi:ry="31.75853"
+ sodipodi:rx="31.75853"
+ sodipodi:cy="294.48819"
+ sodipodi:cx="93.832016"
+ id="path2816-5-4-1-8-3"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ sodipodi:type="arc" />
+ <g
+ id="g2845-6-0-6-8-9"
+ transform="matrix(0.38810374,0,0,0.38810374,438.62243,135.97719)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-6-4-3-2-4"
+ y="289.34262"
+ x="91.530045"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="289.34262"
+ x="91.530045"
+ id="tspan2837-3-0-4-5-3"
+ sodipodi:role="line">e1<tspan
+ id="tspan2839-3-5-00-0-8"
+ style="font-size:20px" /></tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-1-3-0-7-2"
+ y="289.77463"
+ x="107.70822"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="289.77463"
+ x="107.70822"
+ id="tspan2843-2-5-4-2-6"
+ sodipodi:role="line" /></text>
+ </g>
+ </g>
+ <path
+ transform="matrix(1,0,0,0.68177752,420.53,471.40315)"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ inkscape:randomized="0"
+ inkscape:rounded="0"
+ inkscape:flatsided="true"
+ sodipodi:arg2="1.0471976"
+ sodipodi:arg1="0"
+ sodipodi:r2="11.596869"
+ sodipodi:r1="23.193739"
+ sodipodi:cy="116.88141"
+ sodipodi:cx="120.80072"
+ sodipodi:sides="3"
+ id="path3209-5-8-0-1-9"
+ style="fill:url(#linearGradient5901-1);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ sodipodi:type="star"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text4999-4-1-3"
+ y="479.11594"
+ x="515.95068"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:end;line-height:100%;writing-mode:lr-tb;text-anchor:end;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ id="tspan5700-0-9"
+ y="479.11594"
+ x="515.95068"
+ sodipodi:role="line">completed</tspan><tspan
+ y="493.11594"
+ x="515.95068"
+ sodipodi:role="line"
+ id="tspan3232">generation</tspan><tspan
+ id="tspan6910"
+ y="507.11594"
+ x="515.95068"
+ sodipodi:role="line"> of e1</tspan></text>
+ <path
+ inkscape:connector-type="polyline"
+ id="path4716-3-7-4-1"
+ d="M 597.81081,526.0849 569.66664,485.49861"
+ style="fill:none;stroke:#000000;stroke-width:0.903;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-end:url(#marker8943-3);display:inline;stroke-miterlimit:4;stroke-dasharray:none"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <g
+ id="g5910-9-3"
+ transform="translate(129.45902,286.05423)"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ transform="matrix(0.38810374,0,0,0.38810374,444.7126,130.55711)"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ sodipodi:ry="31.75853"
+ sodipodi:rx="31.75853"
+ sodipodi:cy="294.48819"
+ sodipodi:cx="93.832016"
+ id="path2816-5-4-1-8-0-5"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ sodipodi:type="arc" />
+ <g
+ id="g2845-6-0-6-8-7-4"
+ transform="matrix(0.38810374,0,0,0.38810374,438.62243,135.97719)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-6-4-3-2-3-1"
+ y="289.34262"
+ x="91.530045"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="289.34262"
+ x="91.530045"
+ id="tspan2837-3-0-4-5-6-7"
+ sodipodi:role="line">e2</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-1-3-0-7-6-2"
+ y="289.77463"
+ x="107.70822"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="289.77463"
+ x="107.70822"
+ id="tspan2843-2-5-4-2-9-2"
+ sodipodi:role="line" /></text>
+ </g>
+ </g>
+ <g
+ id="g7680"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ id="path6949-5-1-9"
+ d="m 227.46994,625.37304 c 0,216.77224 0,216.30303 0,216.30303"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2.00000001, 2.00000001;stroke-dashoffset:0" />
+ <path
+ id="path6949-9-7-5-8"
+ d="m 47.684335,625.37304 c 0,216.77224 0,216.30303 0,216.30303"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2.00000001, 2.00000001;stroke-dashoffset:0" />
+ <rect
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2923-2-5-8"
+ width="109.65764"
+ height="37.468384"
+ x="117.3623"
+ y="758.99347" />
+ <g
+ id="g2917-0-4-2"
+ transform="matrix(0.6,0,0,0.6,-79.853122,599.39016)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-5-7-4-0"
+ y="303.30817"
+ x="391.29538"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ id="tspan2915-3-5-5"
+ sodipodi:role="line"
+ x="391.29538"
+ y="303.30817">a<tspan
+ style="font-size:23.33333333"
+ id="tspan7508">2</tspan></tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-4-8-9-8"
+ y="303.74017"
+ x="409.47354"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="303.74017"
+ x="409.47354"
+ id="tspan2843-8-72-0-4"
+ sodipodi:role="line" /></text>
+ </g>
+ <path
+ id="path6941-1-8-3"
+ d="m 39.624089,643.2811 c 220.836191,0 221.172261,0.005 221.172261,0.005"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ sodipodi:nodetypes="cc" />
+ <text
+ sodipodi:linespacing="100%"
+ id="text6943-33-9-9"
+ y="640.05188"
+ x="31.395864"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="640.05188"
+ x="31.395864"
+ id="tspan6945-9-8-0"
+ sodipodi:role="line"
+ style="font-size:9.60000038px">Event line</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="13.196648"
+ y="741.08624"
+ id="text3211-3-0-3"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3213-2-4-5"
+ x="13.196648"
+ y="741.08624">start</tspan><tspan
+ sodipodi:role="line"
+ x="13.196648"
+ y="755.08624"
+ id="tspan7516"> of a1</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="230.91504"
+ y="726.04669"
+ id="text3215-4-8-5"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan3217-8-7-5"
+ x="230.91504"
+ y="726.04669">end of a2</tspan></text>
+ <g
+ id="g7510"
+ transform="translate(-1e-6,-50)">
+ <path
+ transform="matrix(1,0,0,0.68177752,23.611066,797.41703)"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ inkscape:randomized="0"
+ inkscape:rounded="0"
+ inkscape:flatsided="true"
+ sodipodi:arg2="1.0471976"
+ sodipodi:arg1="0"
+ sodipodi:r2="11.596869"
+ sodipodi:r1="23.193739"
+ sodipodi:cy="116.88141"
+ sodipodi:cx="120.80072"
+ sodipodi:sides="3"
+ id="path3209-5-81-0"
+ style="fill:url(#linearGradient7514);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ sodipodi:type="star" />
+ <path
+ sodipodi:nodetypes="cc"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ d="m 39.624091,877.10165 c 220.836189,0 221.172259,0.005 221.172259,0.005"
+ id="path6941-7-3-5-0" />
+ </g>
+ <g
+ id="g4705-1-4"
+ transform="matrix(0.85747563,0,0,0.85747563,-246.52782,495.93017)">
+ <path
+ sodipodi:type="arc"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="path2816-5-4-9-3"
+ sodipodi:cx="93.832016"
+ sodipodi:cy="294.48819"
+ sodipodi:rx="31.75853"
+ sodipodi:ry="31.75853"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ transform="matrix(0.45261198,0,0,0.45261198,411.38959,140.44702)" />
+ <g
+ transform="matrix(0.45261198,0,0,0.45261198,408.11357,146.768)"
+ id="g2845-6-0-9-0">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="91.530045"
+ y="289.34262"
+ id="text2835-6-4-2-4"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2837-3-0-7-3"
+ x="91.530045"
+ y="289.34262">e<tspan
+ style="font-size:20px"
+ id="tspan2839-3-5-0-8" /></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="107.70822"
+ y="289.77463"
+ id="text2841-1-3-6-9"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-2-5-1-8"
+ x="107.70822"
+ y="289.77463"
+ style="font-size:18px" /></text>
+ </g>
+ </g>
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:url(#marker8943-92)"
+ d="M 200.44279,759.442 155.95972,734.28786"
+ id="path5224-3"
+ inkscape:connector-type="polyline" />
+ <rect
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ id="rect2923-2-5-8-1"
+ width="109.65764"
+ height="37.468384"
+ x="48.134335"
+ y="661.10962" />
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:url(#marker8943-92)"
+ d="M 131.36294,725.20667 86.87987,700.05253"
+ id="path5224-3-4"
+ inkscape:connector-type="polyline" />
+ <g
+ id="g2917-0-4-2-5"
+ transform="matrix(0.6,0,0,0.6,-144.76237,504.78134)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-5-7-4-0-0"
+ y="303.30817"
+ x="391.29538"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ id="tspan2915-3-5-5-7"
+ sodipodi:role="line"
+ x="391.29538"
+ y="303.30817">a<tspan
+ style="font-size:21.66666667"
+ id="tspan7506">1</tspan></tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-4-8-9-8-7"
+ y="303.74017"
+ x="409.47354"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="303.74017"
+ x="409.47354"
+ id="tspan2843-8-72-0-4-7"
+ sodipodi:role="line" /></text>
+ </g>
+ </g>
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2.00000001, 2.00000001;stroke-dashoffset:0"
+ d="m 573.40706,625.37304 c 0,216.77224 0,216.30303 0,216.30303"
+ id="path6949-5-1-9-0"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <path
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:2.00000001, 2.00000001;stroke-dashoffset:0"
+ d="m 440.17907,625.37304 c 0,216.77224 0,216.30303 0,216.30303"
+ id="path6949-9-7-5-8-2"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <rect
+ y="758.99347"
+ x="573.85706"
+ height="37.468384"
+ width="109.65764"
+ id="rect2923-2-5-8-4"
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <g
+ transform="matrix(0.6,0,0,0.6,364.64162,599.39016)"
+ id="g2917-0-4-2-8"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="391.29538"
+ y="303.30817"
+ id="text2835-5-7-4-0-5"
+ sodipodi:linespacing="100%"><tspan
+ y="303.30817"
+ x="391.29538"
+ sodipodi:role="line"
+ id="tspan2915-3-5-5-72">a<tspan
+ id="tspan7508-1"
+ style="font-size:23.33333397px">2</tspan></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="409.47354"
+ y="303.74017"
+ id="text2841-4-8-9-8-4"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-8-72-0-4-1"
+ x="409.47354"
+ y="303.74017"
+ style="font-size:18px" /></text>
+ </g>
+ <path
+ sodipodi:nodetypes="cc"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:4, 2;stroke-dashoffset:0;marker-end:url(#marker8943)"
+ d="m 432.11883,643.2811 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ id="path6941-1-8-3-7"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <text
+ xml:space="preserve"
+ style="font-size:8.39999962px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="423.89059"
+ y="640.05188"
+ id="text6943-33-9-9-6"
+ sodipodi:linespacing="100%"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ style="font-size:9.60000038px"
+ sodipodi:role="line"
+ id="tspan6945-9-8-0-8"
+ x="423.89059"
+ y="640.05188">Event line</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text3211-3-0-3-2"
+ y="741.08624"
+ x="405.69138"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="741.08624"
+ x="405.69138"
+ id="tspan3213-2-4-5-6"
+ sodipodi:role="line">start</tspan><tspan
+ id="tspan7516-3"
+ y="755.08624"
+ x="405.69138"
+ sodipodi:role="line"> of a1</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text3215-4-8-5-0"
+ y="726.04669"
+ x="620.22107"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:100%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="726.04669"
+ x="620.22107"
+ id="tspan3217-8-7-5-4"
+ sodipodi:role="line">start of of a2</tspan></text>
+ <path
+ transform="matrix(1,0,0,0.68177752,394.10581,747.41703)"
+ d="m 143.99446,116.88141 -34.79061,20.08637 0,-40.172738 34.79061,20.086368 z"
+ inkscape:randomized="0"
+ inkscape:rounded="0"
+ inkscape:flatsided="true"
+ sodipodi:arg2="1.0471976"
+ sodipodi:arg1="0"
+ sodipodi:r2="11.596869"
+ sodipodi:r1="23.193739"
+ sodipodi:cy="116.88141"
+ sodipodi:cx="120.80072"
+ sodipodi:sides="3"
+ id="path3209-5-81-0-4"
+ style="fill:url(#linearGradient7925);fill-opacity:1;stroke:#b75912;stroke-width:1.21109629;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ sodipodi:type="star"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <path
+ sodipodi:nodetypes="cc"
+ style="fill:none;stroke:#000000;stroke-width:0.5;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:1, 3;stroke-dashoffset:0;marker-end:none"
+ d="m 432.11883,827.10165 c 220.83619,0 221.17226,0.005 221.17226,0.005"
+ id="path6941-7-3-5-0-3"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <g
+ transform="matrix(0.85747563,0,0,0.85747563,125.96692,495.93017)"
+ id="g4705-1-4-6"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <path
+ transform="matrix(0.45261198,0,0,0.45261198,411.38959,140.44702)"
+ d="m 125.59055,294.48819 c 0,17.53975 -14.21878,31.75853 -31.758534,31.75853 -17.539752,0 -31.75853,-14.21878 -31.75853,-31.75853 0,-17.53975 14.218778,-31.75853 31.75853,-31.75853 17.539754,0 31.758534,14.21878 31.758534,31.75853 z"
+ sodipodi:ry="31.75853"
+ sodipodi:rx="31.75853"
+ sodipodi:cy="294.48819"
+ sodipodi:cx="93.832016"
+ id="path2816-5-4-9-3-2"
+ style="fill:#ffccaa;fill-opacity:1;stroke:#f40000;stroke-width:4.89559841;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ sodipodi:type="arc" />
+ <g
+ id="g2845-6-0-9-0-6"
+ transform="matrix(0.45261198,0,0,0.45261198,408.11357,146.768)">
+ <text
+ sodipodi:linespacing="100%"
+ id="text2835-6-4-2-4-7"
+ y="289.34262"
+ x="91.530045"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ y="289.34262"
+ x="91.530045"
+ id="tspan2837-3-0-7-3-8"
+ sodipodi:role="line">e<tspan
+ id="tspan2839-3-5-0-8-9"
+ style="font-size:20px" /></tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text2841-1-3-6-9-7"
+ y="289.77463"
+ x="107.70822"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"><tspan
+ style="font-size:18px"
+ y="289.77463"
+ x="107.70822"
+ id="tspan2843-2-5-1-8-0"
+ sodipodi:role="line" /></text>
+ </g>
+ </g>
+ <path
+ inkscape:connector-type="polyline"
+ id="path5224-3-9"
+ d="M 572.93753,759.442 528.45446,734.28786"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:url(#marker8943-92)"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <rect
+ y="661.10962"
+ x="440.62909"
+ height="37.468384"
+ width="109.65764"
+ id="rect2923-2-5-8-1-0"
+ style="fill:#afc6e9;fill-opacity:1;stroke:#001ff4;stroke-width:1.89999998;stroke-linecap:round;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;stroke-dashoffset:0"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <path
+ inkscape:connector-type="polyline"
+ id="path5224-3-4-3"
+ d="M 503.75946,721.736 467.37461,700.05253"
+ style="fill:none;stroke:#000000;stroke-width:1;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-end:url(#marker8943-92)"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438" />
+ <g
+ transform="matrix(0.6,0,0,0.6,247.73237,504.78134)"
+ id="g2917-0-4-2-5-3"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438">
+ <text
+ xml:space="preserve"
+ style="font-size:36px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="391.29538"
+ y="303.30817"
+ id="text2835-5-7-4-0-0-4"
+ sodipodi:linespacing="100%"><tspan
+ y="303.30817"
+ x="391.29538"
+ sodipodi:role="line"
+ id="tspan2915-3-5-5-7-1">a<tspan
+ id="tspan7506-8"
+ style="font-size:21.66666603px">1</tspan></tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ x="409.47354"
+ y="303.74017"
+ id="text2841-4-8-9-8-7-2"
+ sodipodi:linespacing="100%"><tspan
+ sodipodi:role="line"
+ id="tspan2843-8-72-0-4-7-5"
+ x="409.47354"
+ y="303.74017"
+ style="font-size:18px" /></text>
+ </g>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7927"
+ y="170.40047"
+ x="80.611183"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="170.40047"
+ x="80.611183"
+ id="tspan7929"
+ sodipodi:role="line">(a) start-precedes-end</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7931"
+ y="376.30768"
+ x="50.433823"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ id="tspan7985"
+ y="376.30768"
+ x="50.433823"
+ sodipodi:role="line">(c) generation-activity-ordering</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7931-0"
+ y="594.55798"
+ x="58.549366"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="594.55798"
+ x="58.549366"
+ id="tspan7933-2"
+ sodipodi:role="line">(e) usage-activity-ordering</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7927-2"
+ y="170.40047"
+ x="456.43887"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="170.40047"
+ x="456.43887"
+ id="tspan7929-4"
+ sodipodi:role="line">(b) generation-precedes-usage</tspan></text>
+ <text
+ inkscape:transform-center-y="6.888"
+ inkscape:transform-center-x="27.765345"
+ sodipodi:linespacing="100%"
+ id="text7931-9"
+ y="376.30768"
+ x="420.07336"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ id="tspan7985-7"
+ y="376.30768"
+ x="420.07336"
+ sodipodi:role="line">(d) derivation-usage-generation-ordering</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7931-0-6"
+ y="594.55798"
+ x="401.02457"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="594.55798"
+ x="401.02457"
+ id="tspan7933-2-0"
+ sodipodi:role="line">(f) derivation-generation-generation-ordering</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7931-0-7"
+ y="859.19098"
+ x="46.271523"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="859.19098"
+ x="46.271523"
+ id="tspan7933-2-1"
+ sodipodi:role="line">(g) wasInformedBy-ordering</tspan></text>
+ <text
+ sodipodi:linespacing="100%"
+ id="text7931-0-7-1"
+ y="859.19098"
+ x="468.52567"
+ style="font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;line-height:100%;writing-mode:lr-tb;text-anchor:start;fill:#000000;fill-opacity:1;stroke:none;font-family:Utopia;-inkscape-font-specification:Utopia"
+ xml:space="preserve"
+ inkscape:export-filename="/home/lavm/papers/papers/prov-wg/hg/model/path6912.png"
+ inkscape:export-xdpi="79.550438"
+ inkscape:export-ydpi="79.550438"><tspan
+ y="859.19098"
+ x="468.52567"
+ id="tspan7933-2-1-5"
+ sodipodi:role="line">(h) wasStartedBy-ordering</tspan></text>
+ </g>
+ </g>
+</svg>
--- a/model/releases/WD-prov-dm-20111215/Overview.html Wed Dec 14 00:09:57 2011 +0000
+++ b/model/releases/WD-prov-dm-20111215/Overview.html Wed Dec 14 00:11:16 2011 +0000
@@ -14,7 +14,7 @@
</style>
- <script src="http://www.w3.org/2007/OWL/toggles.js" type="text/javascript"></script>
+ <script src="toggles.js" type="text/javascript"></script>
<style type="text/css">
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/model/releases/WD-prov-dm-20111215/toggles.js Wed Dec 14 00:11:16 2011 +0000
@@ -0,0 +1,52 @@
+/*
+ Written by Jonathan Snook, http://www.snook.ca/jonathan
+ Add-ons by Robert Nyman, http://www.robertnyman.com
+ Author says "The credit comment is all it takes, no license. Go crazy with it!:-)"
+ From http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/
+*/
+
+function getElementsByClassName(oElm, strTagName, oClassNames){
+ var arrElements = (! (! (strTagName == "*") || ! (oElm.all)))? oElm.all : oElm.getElementsByTagName(strTagName);
+ var arrReturnElements = new Array();
+ var arrRegExpClassNames = new Array();
+ if(typeof oClassNames == "object"){
+ for(var i=0; !(i>=oClassNames.length); i++){ /*>*/
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames[i].replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ }
+ else{
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames.replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ var oElement;
+ var bMatchesAll;
+ for(var j=0; !(j>=arrElements.length); j++){ /*>*/
+ oElement = arrElements[j];
+ bMatchesAll = true;
+ for(var k=0; !(k>=arrRegExpClassNames.length); k++){ /*>*/
+ if(!arrRegExpClassNames[k].test(oElement.className)){
+ bMatchesAll = false;
+ break;
+ }
+ }
+ if(bMatchesAll){
+ arrReturnElements.push(oElement);
+ }
+ }
+ return (arrReturnElements)
+}
+
+function set_display_by_class(el, cls, newValue) {
+ var e = getElementsByClassName(document, el, cls);
+ if (e != null) {
+ for (var i=0; !(i>=e.length); i++) {
+ e[i].style.display = newValue;
+ }
+ }
+}
+
+function set_display_by_id(id, newValue) {
+ var e = document.getElementById(id);
+ if (e != null) {
+ e.style.display = newValue;
+ }
+}
\ No newline at end of file
--- a/ontology/Overview.html Wed Dec 14 00:09:57 2011 +0000
+++ b/ontology/Overview.html Wed Dec 14 00:11:16 2011 +0000
@@ -631,7 +631,7 @@
padding: 3px 1em;
}
</style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head>
- <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1 class="title" id="title">The PROV Ontology: Model and Formal Semantics</h1><h2 id="w3c-working-draft-24-november-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 24 November 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111124/">http://www.w3.org/TR/2011/WD-prov-o-20111124/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
+ <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1 class="title" id="title">The PROV Ontology: Model and Formal Semantics</h1><h2 id="w3c-working-draft-13-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 13 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111213/">http://www.w3.org/TR/2011/WD-prov-o-20111213/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
<dd><a href="http://tw.rpi.edu/instances/Deborah_L_McGuinness">Deborah McGuinness</a>, Rensselaer Polytechnic Institute, USA</dd>
<dt>Authors:</dt><dd><span>(In alphabetical order)</span></dd>
<dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester, UK</dd>
@@ -639,7 +639,7 @@
<dd><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a>, Universidad Politécnica de Madrid, Spain</dd>
<dd><a href="http://tw.rpi.edu/instances/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute, USA</dd>
<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester, UK</dd>
-<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednick</a>, Rensselaer Polytechnic Institute, USA</dd>
+<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednik</a>, Rensselaer Polytechnic Institute, USA</dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
<div class="introductory section" id="abstract"><h2>Abstract</h2>
--- a/ontology/ProvenanceFormalModel.html Wed Dec 14 00:09:57 2011 +0000
+++ b/ontology/ProvenanceFormalModel.html Wed Dec 14 00:11:16 2011 +0000
@@ -60,7 +60,7 @@
//subtitle : "",
// if you wish the publication date to be other than today, set this
- publishDate: "2011-11-24",
+ publishDate: "2011-12-13",
// if the specification's copyright date is a range of years, specify
// the start date here:
@@ -112,7 +112,7 @@
{ name: "Stian Soiland-Reyes",
url:"http://soiland-reyes.com/stian/",
company: "University of Manchester, UK" },
- { name: "Stephan Zednick",
+ { name: "Stephan Zednik",
url:"http://tw.rpi.edu/web/person/StephanZednik",
company: "Rensselaer Polytechnic Institute, USA" },
],
--- a/ontology/fpwd/Overview.html Wed Dec 14 00:09:57 2011 +0000
+++ b/ontology/fpwd/Overview.html Wed Dec 14 00:11:16 2011 +0000
@@ -2,6 +2,7 @@
<html lang="en" dir="ltr">
<head>
<title>The PROV Ontology: Model and Formal Semantics</title>
+ <script src="toggles.js"></script>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<!--
=== NOTA BENE ===
@@ -631,7 +632,7 @@
padding: 3px 1em;
}
</style><link charset="utf-8" type="text/css" rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD"></head>
- <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1 class="title" id="title">The PROV Ontology: Model and Formal Semantics</h1><h2 id="w3c-working-draft-24-november-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 24 November 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111124/">http://www.w3.org/TR/2011/WD-prov-o-20111124/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
+ <body style="display: inherit;"><div class="head"><p><a href="http://www.w3.org/"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72"></a></p><h1 class="title" id="title">The PROV Ontology: Model and Formal Semantics</h1><h2 id="w3c-working-draft-13-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 13 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-o-20111213/">http://www.w3.org/TR/2011/WD-prov-o-20111213/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a></dd><dt>Editors:</dt><dd><a href="http://cci.case.edu/cci/index.php/Satya_Sahoo">Satya Sahoo</a>, Case Western Reserve University, USA</dd>
<dd><a href="http://tw.rpi.edu/instances/Deborah_L_McGuinness">Deborah McGuinness</a>, Rensselaer Polytechnic Institute, USA</dd>
<dt>Authors:</dt><dd><span>(In alphabetical order)</span></dd>
<dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester, UK</dd>
@@ -639,7 +640,7 @@
<dd><a href="http://www.oeg-upm.net/index.php/en/phdstudents/28-dgarijo">Daniel Garijo</a>, Universidad Politécnica de Madrid, Spain</dd>
<dd><a href="http://tw.rpi.edu/instances/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute, USA</dd>
<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester, UK</dd>
-<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednick</a>, Rensselaer Polytechnic Institute, USA</dd>
+<dd><a href="http://tw.rpi.edu/web/person/StephanZednik">Stephan Zednik</a>, Rensselaer Polytechnic Institute, USA</dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
<div class="introductory section" id="abstract"><h2>Abstract</h2>
@@ -1583,11 +1584,6 @@
<h3><span class="secno">3.5 </span>Overview of the ontology</h3>
<p>The following diagram illustrates the complete PROV ontology except for <code>QualifiedInvolvement</code> which is detailed in the <a href="#overview-of-qualified-involvement">subsection on Qualified Involvement</a> below. </p>
<img src="diagrams/ProvenanceOntology.png" style="min-width: 45em; width: 55em; max-width: 95%" alt="Classes and properties of the PROV ontology">
-<!--
- <p>The following diagram illustrates the complete PROV ontology schema along with the cardinality restrictions imposed on the properties. </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/9/9a/Object_Properties_overall_diagram.png" alt="Object properties among all classes in the PROV ontology"/>
- <a href="https://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.pdf"><img src="https://dvcs.w3.org/hg/prov/raw-file/34a479f3f5d0/ontology/diagram-history/2011-10-03-tlebo/ProvenanceOntology.owl.png" alt="Object properties among all classes in the PROV ontology"/></a>
--->
</div>
<div class="section" id="overview-of-qualified-involvement">
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/fpwd/toggles.js Wed Dec 14 00:11:16 2011 +0000
@@ -0,0 +1,52 @@
+/*
+ Written by Jonathan Snook, http://www.snook.ca/jonathan
+ Add-ons by Robert Nyman, http://www.robertnyman.com
+ Author says "The credit comment is all it takes, no license. Go crazy with it!:-)"
+ From http://www.robertnyman.com/2005/11/07/the-ultimate-getelementsbyclassname/
+*/
+
+function getElementsByClassName(oElm, strTagName, oClassNames){
+ var arrElements = (! (! (strTagName == "*") || ! (oElm.all)))? oElm.all : oElm.getElementsByTagName(strTagName);
+ var arrReturnElements = new Array();
+ var arrRegExpClassNames = new Array();
+ if(typeof oClassNames == "object"){
+ for(var i=0; !(i>=oClassNames.length); i++){ /*>*/
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames[i].replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ }
+ else{
+ arrRegExpClassNames.push(new RegExp("(^|\s)" + oClassNames.replace(/\-/g, "\-") + "(\s|$)"));
+ }
+ var oElement;
+ var bMatchesAll;
+ for(var j=0; !(j>=arrElements.length); j++){ /*>*/
+ oElement = arrElements[j];
+ bMatchesAll = true;
+ for(var k=0; !(k>=arrRegExpClassNames.length); k++){ /*>*/
+ if(!arrRegExpClassNames[k].test(oElement.className)){
+ bMatchesAll = false;
+ break;
+ }
+ }
+ if(bMatchesAll){
+ arrReturnElements.push(oElement);
+ }
+ }
+ return (arrReturnElements)
+}
+
+function set_display_by_class(el, cls, newValue) {
+ var e = getElementsByClassName(document, el, cls);
+ if (e != null) {
+ for (var i=0; !(i>=e.length); i++) {
+ e[i].style.display = newValue;
+ }
+ }
+}
+
+function set_display_by_id(id, newValue) {
+ var e = document.getElementById(id);
+ if (e != null) {
+ e.style.display = newValue;
+ }
+}
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ontology/fpwd/toggles.js.prov.ttl Wed Dec 14 00:11:16 2011 +0000
@@ -0,0 +1,85 @@
+@prefix dc: <http://purl.org/dc/terms/> .
+@prefix frbr: <http://purl.org/vocab/frbr/core#> .
+@prefix http: <http://www.w3.org/2011/http#> .
+@prefix nfo: <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#> .
+@prefix prov: <http://dvcs.w3.org/hg/prov/raw-file/tip/ontology/ProvenanceOntology.owl#> .
+
+<filed://7b766131c1f04bf3b59758a4e58feedc2377f8897e7c57ee2a3db95c0408a37b/SHA256-6c5854e6e626314e2780f57fd2d7df97865087a8ed712e6b667f55524037fb32/toggles.js> a <http://purl.org/vocab/frbr/core#Item>;
+ prov:wasGeneratedBy <http://code.google.com/p/surfrdf/6c97fc1c-93ed-4f6b-9076-15bfd3c66a51>;
+ dc:date "2011-12-12T23:07:46.034679"^^<http://www.w3.org/2001/XMLSchema#dateTime>;
+ dc:modified "2011-12-12T18:07:46"^^<http://www.w3.org/2001/XMLSchema#dateTime>;
+ frbr:exemplarOf <hash:Manifestation/SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382>;
+ frbr:reproductionOf <hash:Item/SHA256-da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31-http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash>;
+ nfo:fileUrl <file:////Users/lebot/afrl/phd/prov-wg/hg/prov/ontology/fpwd/toggles.js>,
+ <toggles.js>;
+ nfo:hasHash <hash:SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382> .
+
+<hash:Expression/SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382> a <http://purl.org/vocab/frbr/core#Expression>;
+ frbr:realizationOf <http://dvcs.w3.org/hg/prov/raw-file/dbc7398ffeec/model/releases/WD-prov-dm-20111215/toggles.js>;
+ nfo:hasHash <hash:SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382> .
+
+<hash:SHA256-da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31> a <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash>;
+ nfo:hashAlgorithm "SHA256";
+ nfo:hashValue "da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31" .
+
+<http://code.google.com/p/surfrdf/236f1e62-3e1f-4c54-9093-9023cd39c927> a <http://www.w3.org/2011/http#ResponseHeader>;
+ http:fieldName "date";
+ http:fieldValue "Mon, 12 Dec 2011 23:07:43 GMT";
+ http:hdrName <http://www.w3.org/2011/http-headers#date> .
+
+<http://code.google.com/p/surfrdf/3858dbc3-7154-47dd-a556-0b7e3cd68c24> a <http://www.w3.org/2011/http#ResponseHeader>;
+ http:fieldName "content-length";
+ http:fieldValue "1599";
+ http:hdrName <http://www.w3.org/2011/http-headers#content-length> .
+
+<http://code.google.com/p/surfrdf/6c97fc1c-93ed-4f6b-9076-15bfd3c66a51> a <http://www.w3.org/2011/http#Request>;
+ prov:hadRecipe <http://www.w3.org/2011/http-methods#GET>;
+ prov:used <hash:Item/SHA256-da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31-http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash>;
+ prov:wasControlledBy <http://purl.org/twc/id/machine/lebot/MacBookPro6_2#lebot>;
+ dc:date "2011-12-12T23:07:46.034679"^^<http://www.w3.org/2001/XMLSchema#dateTime>;
+ http:methd <http://www.w3.org/2011/http-methods#GET>;
+ http:requestURI "http://dvcs.w3.org/hg/prov/raw-file/dbc7398ffeec/model/releases/WD-prov-dm-20111215/toggles.js";
+ http:resp <hash:Item/SHA256-da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31-http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash> .
+
+<http://code.google.com/p/surfrdf/a819e0d4-a989-442c-a1e1-e2ac1b1d65c1> a <http://www.w3.org/2011/http#ResponseHeader>;
+ http:fieldName "vary";
+ http:fieldValue "Accept-Encoding";
+ http:hdrName <http://www.w3.org/2011/http-headers#vary> .
+
+<http://code.google.com/p/surfrdf/c07977c2-618c-416d-abae-ed3cb8b79983> a <http://www.w3.org/2011/http#ResponseHeader>;
+ http:fieldName "content-type";
+ http:fieldValue "application/javascript";
+ http:hdrName <http://www.w3.org/2011/http-headers#content-type> .
+
+<http://code.google.com/p/surfrdf/e5939bac-a9ae-46ad-8cfc-d80b4afc5369> a <http://www.w3.org/2011/http#ResponseHeader>;
+ http:fieldName "server";
+ http:fieldValue "Apache/2.2.16 (Debian)";
+ http:hdrName <http://www.w3.org/2011/http-headers#server> .
+
+<http://code.google.com/p/surfrdf/f6fabf53-2677-4c19-b700-c320054bd475> a <http://www.w3.org/2011/http#ResponseHeader>;
+ http:fieldName "content-disposition";
+ http:fieldValue "inline; filename=\"toggles.js\"";
+ http:hdrName <http://www.w3.org/2011/http-headers#content-disposition> .
+
+<http://dvcs.w3.org/hg/prov/raw-file/dbc7398ffeec/model/releases/WD-prov-dm-20111215/toggles.js> a <http://purl.org/vocab/frbr/core#Work> .
+
+<hash:Manifestation/SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382> a <http://purl.org/vocab/frbr/core#Manifestation>;
+ frbr:embodimentOf <hash:Expression/SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382>;
+ nfo:hasHash <hash:SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382> .
+
+<hash:Item/SHA256-da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31-http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash> a <http://www.w3.org/2011/http#Response>;
+ dc:date "2011-12-12T23:07:43+00:00"^^<http://www.w3.org/2001/XMLSchema#dateTime>;
+ frbr:exemplarOf <hash:Manifestation/SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382>;
+ nfo:hasHash <hash:SHA256-da09eebed83731f98aa833238f71c4876a87bd62deb9ef2cc63d9aec916d0e31>;
+ http:headers <http://code.google.com/p/surfrdf/236f1e62-3e1f-4c54-9093-9023cd39c927>,
+ <http://code.google.com/p/surfrdf/3858dbc3-7154-47dd-a556-0b7e3cd68c24>,
+ <http://code.google.com/p/surfrdf/a819e0d4-a989-442c-a1e1-e2ac1b1d65c1>,
+ <http://code.google.com/p/surfrdf/c07977c2-618c-416d-abae-ed3cb8b79983>,
+ <http://code.google.com/p/surfrdf/e5939bac-a9ae-46ad-8cfc-d80b4afc5369>,
+ <http://code.google.com/p/surfrdf/f6fabf53-2677-4c19-b700-c320054bd475>;
+ http:httpVersion "1.1" .
+
+<hash:SHA256-63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382> a <http://www.semanticdesktop.org/ontologies/2007/03/22/nfo#FileHash>;
+ nfo:hashAlgorithm "SHA256";
+ nfo:hashValue "63823aa544613fb0ea916ac9a4bcd8e50cb3b1418669d66237df0a3f6346e382" .
+
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/paq/WD-PROV-AQ-20111212.html Wed Dec 14 00:11:16 2011 +0000
@@ -0,0 +1,1286 @@
+<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
+<html lang="en" dir="ltr">
+<head>
+ <title>PROV-AQ: Provenance Access and Query</title>
+ <link rel="stylesheet" type="text/css" href="css/prov-aq.css">
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+<!-- Use common W3C-hosted version of ReSpec.js:
+-->
+
+<!-- Use local version of ReSpec.js for debugging:
+ <script src="js/respec.js" class="remove"></script>
+-->
+
+ <style type="text/css">
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
+h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
+ border: none;
+}
+
+dfn {
+ font-weight: bold;
+}
+
+a.internalDFN {
+ color: inherit;
+ border-bottom: 1px solid #99c;
+ text-decoration: none;
+}
+
+a.externalDFN {
+ color: inherit;
+ border-bottom: 1px dotted #ccc;
+ text-decoration: none;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+code {
+ color: #ff4500;
+}
+
+
+/* --- WEB IDL --- */
+pre.idl {
+ border-top: 1px solid #90b8de;
+ border-bottom: 1px solid #90b8de;
+ padding: 1em;
+ line-height: 120%;
+}
+
+pre.idl::before {
+ content: "WebIDL";
+ display: block;
+ width: 150px;
+ background: #90b8de;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+.idlType {
+ color: #ff4500;
+ font-weight: bold;
+ text-decoration: none;
+}
+
+/*.idlModule*/
+/*.idlModuleID*/
+/*.idlInterface*/
+.idlInterfaceID, .idlDictionaryID {
+ font-weight: bold;
+ color: #005a9c;
+}
+
+.idlSuperclass {
+ font-style: italic;
+ color: #005a9c;
+}
+
+/*.idlAttribute*/
+.idlAttrType, .idlFieldType, .idlMemberType {
+ color: #005a9c;
+}
+.idlAttrName, .idlFieldName, .idlMemberName {
+ color: #ff4500;
+}
+.idlAttrName a, .idlFieldName a, .idlMemberName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlMethod*/
+.idlMethType {
+ color: #005a9c;
+}
+.idlMethName {
+ color: #ff4500;
+}
+.idlMethName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlParam*/
+.idlParamType {
+ color: #005a9c;
+}
+.idlParamName {
+ font-style: italic;
+}
+
+.extAttr {
+ color: #666;
+}
+
+/*.idlConst*/
+.idlConstType {
+ color: #005a9c;
+}
+.idlConstName {
+ color: #ff4500;
+}
+.idlConstName a {
+ color: #ff4500;
+ border-bottom: 1px dotted #ff4500;
+ text-decoration: none;
+}
+
+/*.idlException*/
+.idlExceptionID {
+ font-weight: bold;
+ color: #c00;
+}
+
+.idlTypedefID, .idlTypedefType {
+ color: #005a9c;
+}
+
+.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
+ color: #c00;
+ font-weight: normal;
+}
+
+.excName a {
+ font-family: monospace;
+}
+
+.idlRaises a.idlType, .excName a.idlType {
+ border-bottom: 1px dotted #c00;
+}
+
+.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
+ width: 45px;
+ text-align: center;
+}
+.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
+.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
+
+.idlImplements a {
+ font-weight: bold;
+}
+
+dl.attributes, dl.methods, dl.constants, dl.fields, dl.dictionary-members {
+ margin-left: 2em;
+}
+
+.attributes dt, .methods dt, .constants dt, .fields dt, .dictionary-members dt {
+ font-weight: normal;
+}
+
+.attributes dt code, .methods dt code, .constants dt code, .fields dt code, .dictionary-members dt code {
+ font-weight: bold;
+ color: #000;
+ font-family: monospace;
+}
+
+.attributes dt code, .fields dt code, .dictionary-members dt code {
+ background: #ffffd2;
+}
+
+.attributes dt .idlAttrType code, .fields dt .idlFieldType code, .dictionary-members dt .idlMemberType code {
+ color: #005a9c;
+ background: transparent;
+ font-family: inherit;
+ font-weight: normal;
+ font-style: italic;
+}
+
+.methods dt code {
+ background: #d9e6f8;
+}
+
+.constants dt code {
+ background: #ddffd2;
+}
+
+.attributes dd, .methods dd, .constants dd, .fields dd, .dictionary-members dd {
+ margin-bottom: 1em;
+}
+
+table.parameters, table.exceptions {
+ border-spacing: 0;
+ border-collapse: collapse;
+ margin: 0.5em 0;
+ width: 100%;
+}
+table.parameters { border-bottom: 1px solid #90b8de; }
+table.exceptions { border-bottom: 1px solid #deb890; }
+
+.parameters th, .exceptions th {
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+ font-family: initial;
+ font-weight: normal;
+ text-shadow: #666 1px 1px 0;
+}
+.parameters th { background: #90b8de; }
+.exceptions th { background: #deb890; }
+
+.parameters td, .exceptions td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+ vertical-align: top;
+}
+
+.parameters tr:first-child td, .exceptions tr:first-child td {
+ border-top: none;
+}
+
+.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
+ width: 100px;
+}
+
+.parameters td.prmType {
+ width: 120px;
+}
+
+table.exceptions table {
+ border-spacing: 0;
+ border-collapse: collapse;
+ width: 100%;
+}
+
+/* --- TOC --- */
+.toc a {
+ text-decoration: none;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- TABLE --- */
+table.simple {
+ border-spacing: 0;
+ border-collapse: collapse;
+ border-bottom: 3px solid #005a9c;
+}
+
+.simple th {
+ background: #005a9c;
+ color: #fff;
+ padding: 3px 5px;
+ text-align: left;
+}
+
+.simple th[scope="row"] {
+ background: inherit;
+ color: inherit;
+ border-top: 1px solid #ddd;
+}
+
+.simple td {
+ padding: 3px 10px;
+ border-top: 1px solid #ddd;
+}
+
+.simple tr:nth-child(even) {
+ background: #f0f6ff;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+
+/* --- EXAMPLES --- */
+pre.example {
+ border-top: 1px solid #ff4500;
+ border-bottom: 1px solid #ff4500;
+ padding: 1em;
+ margin-top: 1em;
+}
+
+pre.example::before {
+ content: "Example";
+ display: block;
+ width: 150px;
+ background: #ff4500;
+ color: #fff;
+ font-family: initial;
+ padding: 3px;
+ font-weight: bold;
+ margin: -1em 0 1em -1em;
+}
+
+/* --- EDITORIAL NOTES --- */
+.issue {
+ padding: 1em;
+ margin: 1em 0em 0em;
+ border: 1px solid #f00;
+ background: #ffc;
+}
+
+.issue::before {
+ content: "Issue";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #f00;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+.note {
+ margin: 1em 0em 0em;
+ padding: 1em;
+ border: 2px solid #cff6d9;
+ background: #e2fff0;
+}
+
+.note::before {
+ content: "Note";
+ display: block;
+ width: 150px;
+ margin: -1.5em 0 0.5em 0;
+ font-weight: bold;
+ border: 1px solid #cff6d9;
+ background: #fff;
+ padding: 3px 1em;
+}
+
+/* --- Best Practices --- */
+div.practice {
+ border: solid #bebebe 1px;
+ margin: 2em 1em 1em 2em;
+}
+
+span.practicelab {
+ margin: 1.5em 0.5em 1em 1em;
+ font-weight: bold;
+ font-style: italic;
+}
+
+span.practicelab { background: #dfffff; }
+
+span.practicelab {
+ position: relative;
+ padding: 0 0.5em;
+ top: -1.5em;
+}
+
+p.practicedesc {
+ margin: 1.5em 0.5em 1em 1em;
+}
+
+@media screen {
+ p.practicedesc {
+ position: relative;
+ top: -2em;
+ padding: 0;
+ margin: 1.5em 0.5em -1em 1em;
+ }
+}
+
+/* --- SYNTAX HIGHLIGHTING --- */
+pre.sh_sourceCode {
+ background-color: white;
+ color: black;
+ font-style: normal;
+ font-weight: normal;
+}
+
+pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
+pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
+pre.sh_sourceCode .sh_usertype { color: teal; } /* user defined types */
+pre.sh_sourceCode .sh_string { color: red; font-family: monospace; } /* strings and chars */
+pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; } /* regular expressions */
+pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
+pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; } /* comments */
+pre.sh_sourceCode .sh_number { color: purple; } /* literal numbers */
+pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; } /* e.g., #include, import */
+pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
+pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
+pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
+pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
+
+/* Predefined variables and functions (for instance glsl) */
+pre.sh_sourceCode .sh_predef_var { color: #00008B; }
+pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
+
+/* for OOP */
+pre.sh_sourceCode .sh_classname { color: teal; }
+
+/* line numbers (not yet implemented) */
+pre.sh_sourceCode .sh_linenum { display: none; }
+
+/* Internet related */
+pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
+
+/* for ChangeLog and Log files */
+pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
+pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
+pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
+
+/* for Prolog, Perl... */
+pre.sh_sourceCode .sh_variable { color: #006400; }
+
+/* for LaTeX */
+pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
+pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
+pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
+pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
+pre.sh_sourceCode .sh_argument { color: #006400; }
+pre.sh_sourceCode .sh_optionalargument { color: purple; }
+pre.sh_sourceCode .sh_math { color: orange; }
+pre.sh_sourceCode .sh_bibtex { color: blue; }
+
+/* for diffs */
+pre.sh_sourceCode .sh_oldfile { color: orange; }
+pre.sh_sourceCode .sh_newfile { color: #006400; }
+pre.sh_sourceCode .sh_difflines { color: blue; }
+
+/* for css */
+pre.sh_sourceCode .sh_selector { color: purple; }
+pre.sh_sourceCode .sh_property { color: blue; }
+pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
+
+/* other */
+pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
+pre.sh_sourceCode .sh_paren { color: red; }
+pre.sh_sourceCode .sh_attribute { color: #006400; }
+
+</style><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head>
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-AQ: Provenance Access and Query</h1><h2 id="w3c-working-draft-12-december-2011"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 12 December 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-prov-aq-20111212/">http://www.w3.org/TR/2011/WD-prov-aq-20111212/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-aq/">http://www.w3.org/TR/prov-aq/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html">http://dvcs.w3.org/hg/prov/raw-file/tip/paq/prov-aq.html</a></dd><dt>Editors:</dt><dd><span>Graham Klyne</span>, <a href="http://www.ox.ac.uk/">University of Oxford</a></dd>
+<dd><span>Paul Groth</span>, <a href="http://www.vu.nl/">VU University Amsterdam</a></dd>
+<dt>Authors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+<dd><span>Olaf Hartig</span>, Invited Expert</dd>
+<dd><span>Yogesh Simmhan</span>, Invited Expert</dd>
+<dd><a href="http://www.rpi.edu/research/ccni/">James Myers</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://tw.rpi.edu/web/person/TimLebo">Timothy Lebo</a>, Rensselaer Polytechnic Institute</dd>
+<dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
+<dd><a href="http://www.inf.kcl.ac.uk/staff/simonm/">Simon Miles</a>, Invited Expert</dd>
+</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2011-2011 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
+
+
+ <div id="abstract" class="introductory section"><h2>Abstract</h2>
+This document specifies how to use standard Web protocols,
+including HTTP, to obtain information about the provenance of Web
+resources. We describe both simple access mechanisms for
+locating provenance information associated with web pages or resources, and
+provenance query services for more complex deployments. This is
+part of the larger <acronym title="World Wide Web Consortium">W3C</acronym> Prov provenance framework.
+ </div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
+ This document is part of a set of specifications produced by the <acronym title="World Wide Web Consortium">W3C</acronym> provenance working group aiming to define interoperable interchange of provenance information in heterogeneous environments such as the Web. It describes the use of existing web mechanisms for discovery and retrieval of provenance information.
+ <p>This document was published by the <a href="http://www.w3.org/2011/prov">Provenance Working Group</a> as a First Public Working Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. The group does not expect this document to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#concepts" class="tocxref"><span class="secno">1.1 </span>Concepts</a></li><li class="tocline"><a href="#provenance--entities-and-resources" class="tocxref"><span class="secno">1.2 </span>Provenance, entities and resources</a></li><li class="tocline"><a href="#interpreting-provenance-information" class="tocxref"><span class="secno">1.3 </span>Interpreting provenance information</a></li></ul></li><li class="tocline"><a href="#accessing-provenance-information" class="tocxref"><span class="secno">2. </span>Accessing provenance information</a></li><li class="tocline"><a href="#locating-provenance-information" class="tocxref"><span class="secno">3. </span>Locating provenance information</a><ul class="toc"><li class="tocline"><a href="#resource-accessed-by-http" class="tocxref"><span class="secno">3.1 </span>Resource accessed by HTTP</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-services" class="tocxref"><span class="secno">3.1.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-html" class="tocxref"><span class="secno">3.2 </span>Resource represented as HTML</a><ul class="toc"><li class="tocline"><a href="#specifying-provenance-services-1" class="tocxref"><span class="secno">3.2.1 </span>Specifying Provenance Services</a></li></ul></li><li class="tocline"><a href="#resource-represented-as-rdf" class="tocxref"><span class="secno">3.3 </span>Resource represented as RDF</a></li><li class="tocline"><a href="#arbitrary-data" class="tocxref"><span class="secno">3.4 </span>Arbitrary data</a></li></ul></li><li class="tocline"><a href="#provenance-services" class="tocxref"><span class="secno">4. </span>Provenance services</a><ul class="toc"><li class="tocline"><a href="#using-the-provenance-service-api" class="tocxref"><span class="secno">4.1 </span>Using the provenance service API</a><ul class="toc"><li class="tocline"><a href="#retrieve-provenance-uris-for-a-resource" class="tocxref"><span class="secno">4.1.1 </span>Retrieve Provenance-URIs for a resource</a></li><li class="tocline"><a href="#retrieve-provenance-information-for-a-resource" class="tocxref"><span class="secno">4.1.2 </span>Retrieve Provenance information for a resource</a></li></ul></li><li class="tocline"><a href="#resources-presented-and-representations-used" class="tocxref"><span class="secno">4.2 </span>Resources presented and representations used</a><ul class="toc"><li class="tocline"><a href="#service-description" class="tocxref"><span class="secno">4.2.1 </span>Service description</a></li><li class="tocline"><a href="#provenance-locations" class="tocxref"><span class="secno">4.2.2 </span>Provenance locations</a></li><li class="tocline"><a href="#provenance-information" class="tocxref"><span class="secno">4.2.3 </span>Provenance information</a></li></ul></li><li class="tocline"><a href="#provenance-service-discovery" class="tocxref"><span class="secno">4.3 </span>Provenance service discovery</a></li></ul></li><li class="tocline"><a href="#querying-provenance-information" class="tocxref"><span class="secno">5. </span>Querying provenance information</a><ul class="toc"><li class="tocline"><a href="#find-provenance-uri-given-entity-uri-of-resource" class="tocxref"><span class="secno">5.1 </span>Find provenance-URI given entity-URI of resource</a></li><li class="tocline"><a href="#find-provenance-uri-given-identifying-information-about-a-resource" class="tocxref"><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</a></li><li class="tocline"><a href="#obtain-provenance-information-directly-given-an-entity-uri-of-a-resource" class="tocxref"><span class="secno">5.3 </span>Obtain provenance information directly given an entity-URI of a resource</a></li></ul></li><li class="tocline"><a href="#incremental-provenance-retrieval" class="tocxref"><span class="secno">6. </span>Incremental Provenance Retrieval</a><ul class="toc"><li class="tocline"><a href="#via-web-retrieval" class="tocxref"><span class="secno">6.1 </span>Via Web Retrieval</a></li><li class="tocline"><a href="#via-queries" class="tocxref"><span class="secno">6.2 </span>Via Queries</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">7. </span>IANA considerations</a><ul class="toc"><li class="tocline"><a href="#registration-template-for-link-relation---provenance" class="tocxref"><span class="secno">7.1 </span>Registration template for link relation: "provenance"</a></li><li class="tocline"><a href="#registration-template-for-link-relation---anchor" class="tocxref"><span class="secno">7.2 </span>Registration template for link relation: "anchor"</a></li><li class="tocline"><a href="#registration-template-for-link-relation---provenance-service" class="tocxref"><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</a></li></ul></li><li class="tocline"><a href="#security-considerations" class="tocxref"><span class="secno">8. </span>Security considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#provenance-service-format-examples" class="tocxref"><span class="secno">B. </span>Provenance service format examples</a><ul class="toc"><li class="tocline"><a href="#rdf-turtle-example-of-service-description" class="tocxref"><span class="secno">B.1 </span>RDF Turtle example of service description</a></li><li class="tocline"><a href="#rdf-xml-example-of-service-description" class="tocxref"><span class="secno">B.2 </span>RDF/XML example of service description</a></li><li class="tocline"><a href="#plain-xml-example-of-service-description" class="tocxref"><span class="secno">B.3 </span>Plain XML example of service description</a></li><li class="tocline"><a href="#rdf-turtle-example-of-provenance-locations" class="tocxref"><span class="secno">B.4 </span>RDF Turtle example of provenance locations</a></li><li class="tocline"><a href="#rdf-xml-example-of-provenance-locations" class="tocxref"><span class="secno">B.5 </span>RDF/XML example of provenance locations</a></li><li class="tocline"><a href="#plain-xml-example-of-provenance-locations" class="tocxref"><span class="secno">B.6 </span>Plain XML example of provenance locations</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">C.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.2 </span>Informative references</a></li></ul></li></ul></div>
+
+
+
+<!-- == Sect 1 =================================================================================== -->
+
+ <div id="introduction" class="section">
+ <!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
+ <p>
+ The Provenance Data Model [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] and Provenance Ontology [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-O">PROV-O</a></cite>] specifications define how to represent provenance information in the World Wide Web.
+ </p>
+ <p>
+ This note describes how existing web mechanisms may be used to locate, retrieve and query provenance information.
+ </p>
+
+ <div id="concepts" class="section">
+ <h3><span class="secno">1.1 </span>Concepts</h3>
+ <p>
+ In defining the specification below, we make use of the following concepts.
+ </p><dl>
+ <dt><dfn id="dfn-provenance-information">Provenance information</dfn></dt>
+ <dd>refers to provenance represented in some fashion.</dd>
+ <dt><dfn id="dfn-provenance-uri">Provenance-URI</dfn></dt>
+ <dd>a URI denoting some <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>.</dd>
+ <dt><dfn id="dfn-entity">Entity</dfn></dt>
+ <dd>an aspect of a <a class="internalDFN" href="#dfn-resource">resource</a>, about which one wishes to present some <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>. For example, a weather report for a given date may be an aspect of a resource that is maintained as the current weather report. An entity is itself a <a class="internalDFN" href="#dfn-resource">resource</a>. See also [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>], and [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>] <a href="http://www.w3.org/TR/webarch/#representation-reuse">section 2.3.2</a>.</dd>
+ <dt><dfn id="dfn-entity-uri">Entity-URI</dfn></dt>
+ <dd>a URI denoting an <a class="internalDFN" href="#dfn-entity">entity</a>, which allows that entity to be identified for the purpose of finding and expressing <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> (see <a href="#provenance-entities-resources" class="sectionRef">section 1.2 </a> for discussion)</dd>
+ <dt><dfn id="dfn-provenance-service">Provenance service</dfn></dt>
+ <dd>a service that provides a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> given a <a class="internalDFN" href="#dfn-resource">resource</a> URI or an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>.</dd>
+ <dt><dfn id="dfn-service-uri">Service-URI</dfn></dt>
+ <dd>the URI of a <a class="internalDFN" href="#dfn-provenance-service">provenance service</a>.</dd>
+ <dt><dfn id="dfn-resource">Resource</dfn></dt>
+ <dd>also referred to as <dfn id="dfn-web-resource">web resource</dfn>: a resource as described by the Architecture of the World Wide Web [<cite><a class="bibref" rel="biblioentry" href="#bib-WEBARCH">WEBARCH</a></cite>], <a href="http://www.w3.org/TR/webarch/#id-resources">section 2.2</a>. A resource may be associated with multiple <a title="Entity" class="internalDFN" href="#dfn-entity">entities</a> (see <a href="#provenance-entities-resources" class="sectionRef">section 1.2 </a> for discussion)</dd>
+ </dl>
+ <p></p>
+
+ </div>
+
+ <div id="provenance--entities-and-resources" class="section">
+ <h3 id="provenance-entities-resources"><span class="secno">1.2 </span>Provenance, entities and resources</h3>
+ <p>
+ Fundamentally, <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> is <em>about</em> <a class="internalDFN">resources</a>. In general, resources may vary over time and context. E.g., a resource describing the weather in London changes from day-to-day, or one listing restaurants near you will vary depending on your location. Provenance information, to be useful, must be persistent and not itself dependent on context. Yet we may still want to make provenance assertions about dynamic or context-dependent web resources (e.g. the weather forecast for London on a particular day may have been derived from a particular set of Meteorological Office data).
+ </p>
+ <p>
+ Provenance descriptions of dynamic and context-dependent resources are possible through the notion of entities. An <a class="internalDFN" href="#dfn-entity">entity</a> is simply a web resource that is a contextualized view or instance of an original web resource. For example, a <acronym title="World Wide Web Consortium">W3C</acronym> specification typically undergoes several public revisions before it is finalized. A URI that refers to the "current" revision might be thought of as denoting the specification through its lifetime. Separate URIs for each individual revision would then be <a class="internalDFN">entity-URIs</a>, denoting the specification at a particular stage in its development. Using these, we can make provenance assertions that a particular revision was published on a particular date, and was last modified by a particular editor. Entity-URIs may use any URI scheme, and are not required to be dereferencable.
+ </p>
+ <p>
+ Requests for provenance about a resource may return provenance information that uses one or more entity-URIs to refer to versions of that resource. Some given provenance information may use multiple entity-URIs if there are assertions referring to the same underlying resource in different contexts. For example, provenance information describing a <acronym title="World Wide Web Consortium">W3C</acronym> document might include information about all revisions of the document using statements that use the different entity-URIs of the various revisions.
+ </p>
+ <p>
+ In summary, a key notion within the concepts outlined above is that <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> may be not universally applicable to a <a class="internalDFN" href="#dfn-resource">resource</a>, but may be expressed with respect to that resource in a restricted context (e.g. at a particular time). This restricted view is called an <a class="internalDFN" href="#dfn-entity">entity</a>, and an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a> is used to refer to it within provenance information.
+ </p>
+ </div>
+
+ <div id="interpreting-provenance-information" class="section">
+ <h3><span class="secno">1.3 </span>Interpreting provenance information</h3>
+ <p><a class="internalDFN" href="#dfn-provenance-information">Provenance information</a> describes relationships between entities, activities and agents. As such, any given provenance information may contain information about several <a title="Entity" class="internalDFN" href="#dfn-entity">entities</a>. Within some provenance information, the entities thus described are identified by their <a class="internalDFN" href="#dfn-entity-uri">Entity-URI</a>s.
+ </p>
+ <p>When interpreting provenance information, it is important to be aware that statements about several entities may be present, and to be accordingly selective when using the information provided. (In some exceptional cases, it may be that the provenance information returned does not contain any information relating to a specific associated entity.)
+ </p>
+ </div>
+
+ </div>
+
+<!-- == Sect 2 =================================================================================== -->
+
+ <div id="accessing-provenance-information" class="section">
+ <!--OddPage--><h2><span class="secno">2. </span>Accessing provenance information</h2>
+ <p>Web applications may access <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> in the same way as any web resource, by dereferencing its URI. Typically, this will be by performing an HTTP GET operation. Thus, any provenance information may be associated with a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>, and may be accessed by dereferencing that URI using normal web mechanisms.
+ </p>
+ <p>
+ Provenance assertions are about pre-determined activities involving entities; as such, they are not dynamic. Thus, provenance information returned at a given provenance-URI may commonly be static. But the availability of provenance information about a resource may vary (e.g. if there is insufficient storage to keep it indefinitely, or new information becomes available at a later date), so the provenance information returned at a given URI may change, provided that such change does not contradict any previously retrieved information.
+ </p>
+ <p>
+ How much or how little provenance information is returned in response to to a retrieval request is a matter for the provenance provider application. At a minimum, for as long as provenance information about an entity remains available, sufficient should be returned to enable a client application to walk the provenance graph per <a class="sectionRef" href="#incremental-provenance-retrieval">section 6. Incremental Provenance Retrieval</a>.
+ </p>
+ <p>
+ When publishing provenance as a web resource, the <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> should be discoverable using one or more of the mechanisms described in <a href="#locating-provenance-information" class="sectionRef">section 3. Locating provenance information</a>.
+ </p>
+ <p>
+ If there is no URI for some particular provenance information, then alternative mechanisms may be needed. Possible mechanisms are suggested in <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> and <a href="#querying-provenance-information" class="sectionRef">section 5. Querying provenance information</a>.
+ </p>
+ </div>
+
+<!-- == Sect 3 =================================================================================== -->
+
+ <div id="locating-provenance-information" class="section">
+ <!--OddPage--><h2><span class="secno">3. </span>Locating provenance information</h2>
+ <p>
+ When <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> is a resource that can be accessed using normal web retrieval, one needs to know a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> to dereference. If this is known in advance, there is nothing more to specify. If a provenance-URI is not known then a mechanism to discover one must be based on information that is available to the would-be accessor.
+ </p>
+ <p>Provenance information may be provided by several parties other than the provider of the original resource, each using different provenance-URIs, and each with different concerns. (It is possible that these different parties may provide contradictory provenance information.)
+ </p>
+ <p>
+ Once provenance information information is retrieved, one also needs to know how to locate the view of that resource within that provenance information. This view is an <a class="internalDFN" href="#dfn-entity">entity</a> and is identified by an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>.
+ </p>
+ <p>
+ We start by considering mechanisms for the resource provider to indicate a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> along with a <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>. (Mechanisms that can be independent of the resource provision are discussed in <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>). Three mechanisms are described here:
+ </p><ul>
+ <li>The requester knows the resource URI <em>and</em> the resource is accessible using HTTP</li>
+ <li>The requester has a copy of a resource represented as HTML or XHTML</li>
+ <li>The requester has a copy of a resource represented as RDF (including the range of possible RDF syntaxes, such as HTML with embedded RDFa)</li>
+ </ul>
+ These particular cases are selected as corresponding to primary current web protocol and data formats. Finally, in <a href="#arbitrary-data" class="sectionRef">section 3.4 Arbitrary data</a>, we discuss the case of a resource in an unspecified format which has been provided by some means other than HTTP.
+ <p></p>
+ <p>
+ The mechanisms specified for use with HTTP and HTML are similar to those proposed by POWDER [<cite><a class="bibref" rel="biblioentry" href="#bib-POWDER-DR">POWDER-DR</a></cite>] (sections <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#assoc-markup">4.1.1</a> and <a href="http://www.w3.org/TR/2009/REC-powder-dr-20090901/#httplink">4.1.3</a>).
+ </p>
+
+ <div id="resource-accessed-by-http" class="section">
+ <h3><span class="secno">3.1 </span>Resource accessed by HTTP</h3>
+ <p>
+ For a document accessible using HTTP, provenance information may be indicated using an HTTP <code>Link</code> header field, as defined by <a href="http://tools.ietf.org/html/rfc5988">Web Linking (RFC 5988)</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-LINK-REL">LINK-REL</a></cite>]. The <code>Link</code> header field is included in the HTTP response to a GET or HEAD operation (other HTTP operations are not excluded, but are not considered here).
+ </p>
+ <p>
+ A <code>provenance</code> link relation type for referencing provenance information is registered according to the template in <a href="#iana-considerations" class="sectionRef">section 7. IANA considerations</a>, and may be used as shown::
+ </p><pre class="pattern">Link: <cite>provenance-URI</cite>; rel="provenance"; anchor="<cite>entity-URI</cite>"</pre>
+ When used in conjunction with an HTTP success response code (<code>2xx</code>), this HTTP header field indicates that <code><cite>provenance-URI</cite></code> is the URI of some provenance information associated with the requested resource and that the associated entity is identified as <code><cite>entity-URI</cite></code>. (See also <a href="#interpreting-provenance-information" class="sectionRef">section 1.3 Interpreting provenance information</a>.)
+ <p></p>
+ <p>
+ If no <code>anchor</code> link is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the resource.
+ </p>
+ <p>
+ At this time, the meaning of these links returned with other HTTP response codes is not defined: future revisions of this specification may define interpretations for these.
+ </p>
+ <p>
+ An HTTP response <em class="rfc2119" title="may">may</em> include multiple <code>provenance</code> link header fields, indicating a number of different provenance resources that are known to the responding server, each providing provenance information about the accessed resource.
+ </p>
+ <p>
+ The presence of a <code>provenance</code> link in an HTTP response does not preclude the possibility that other publishers may offer provenance information about the same resource. In such cases, discovery of the additional provenance information must use other means (e.g. see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>).
+ </p>
+ <p>
+ Provenance resources indicated in this way are not guaranteed to be authoritative. Trust in the linked provenance data must be determined separately from trust in the original resource, just as in the web at large, it is a users' responsibility to determine an appropriate level of trust in any other linked resource; e.g. based on the domain that serves it, or an associated digital signature. (Ssee also <a href="#security-considerations" class="sectionRef">section 8. Security considerations</a>.)
+ </p>
+
+ <div id="specifying-provenance-services" class="section">
+ <h4><span class="secno">3.1.1 </span>Specifying Provenance Services</h4>
+ <p class="pending">
+ This is a new proposal. It needs to be checked as to whether it is useful. GK/PG to review nature of provenance-service-URI.
+ </p>
+ <p>
+ The document provider may indicate that provenance information about the document is provided by a <a class="internalDFN" href="#dfn-provenance-service">provenance service</a>. This is done through the use of a <code>provenance-service</code> link relation type following the same pattern as above:
+ </p>
+ <pre class="pattern">Link: <cite>provenance-service-URI</cite>; anchor="<cite>entity-URI</cite>"; rel="provenance-service"</pre>
+ <p>
+ The <code>provenance-service</code> link identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to determine a <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> or retrieve <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> for an <a class="internalDFN" href="#dfn-entity">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
+ </p>
+ <p>
+ There may be multiple <code>provenance-service</code> link header fields, and these may appear in the same document as <code>provenance</code> links (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations will not be used together).
+ </p>
+ </div>
+
+ </div>
+
+ <div id="resource-represented-as-html" class="section">
+ <h3><span class="secno">3.2 </span>Resource represented as HTML</h3>
+ <p>
+ For a document presented as HTML or XHTML, without regard for how it has been obtained, provenance information may be associated with a resource by adding a <code><Link></code> element to the HTML <code><head></code> section.
+ Two new link relation types for referencing provenance information are registered according to the template in <a href="#iana-considerations" class="sectionRef">section 7. IANA considerations</a>, and may be used as shown:
+ </p><pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <link rel="provenance" href="<cite>provenance-URI</cite>">
+ <link rel="anchor" href="<cite>entity-URI</cite>">
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ ...
+ </body>
+ </html></pre>
+ <p></p>
+ <p>
+ The <code><cite>provenance-URI</cite></code> given by the <code>provenance</code> link element identifies the provenance-URI for the document.
+ </p>
+ <p>
+ The <code><cite>entity-URI</cite></code> given by the <code>anchor</code> link element specifies an identifier for the presented document view, and which may be used within the provenance information when referring to this document.
+ </p>
+ <p>
+ An HTML document header <em class="rfc2119" title="may">may</em> include multiple "provenance" link elements, indicating a number of different provenance resources that are known to the creator of the document, each of which may provide provenance information about the document.
+ </p>
+ <p>
+ Likewise, the header <em class="rfc2119" title="may">may</em> include multiple "anchor" link elements indicating that, e.g., different revisions of the document can be identified in the provenance information using the different <code><cite>entity-URIs</cite></code>.
+ </p>
+ <p>
+ If no "anchor" link element is provided then the <code><cite>entity-URI</cite></code> is assumed to be the URI of the document. It is <em class="rfc2119" title="recommended">recommended</em> that this convention be used only when the document is static.
+ </p>
+
+ <div id="specifying-provenance-services-1" class="section">
+ <h4><span class="secno">3.2.1 </span>Specifying Provenance Services</h4>
+ <p>
+ The document creator may specify that the provenance information about the document is provided by a <a class="internalDFN" href="#dfn-provenance-service">provenance service</a>. This is done through the use of a third link relation type following the same pattern as above:
+ </p>
+ <pre class="pattern"> <html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <link rel="provenance-service" href="<cite>service-URI</cite>">
+ <link rel="anchor" href="<cite>entity-URI</cite>">
+ <title>Welcome to example.com</title>
+ </head>
+ <body>
+ ...
+ </body>
+ </html></pre>
+ <p>
+ The <code>provenance-service</code> link element identifies the <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Dereferencing this URI yields a service description that provides further information to enable a client to access <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> for an <a class="internalDFN" href="#dfn-entity">entity</a>; see <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> for more details.
+ </p>
+ <p>
+ There may be multiple <code>provenance-service</code> link elements, and these <em class="rfc2119" title="may">may</em> appear in the same document as <code>anchor</code> and <code>provenance</code> link elements (though, in simple cases, we anticipate that <code>provenance</code> and <code>provenance-service</code> link relations would not be used together).
+ </p>
+ </div>
+ </div>
+
+ <div id="resource-represented-as-rdf" class="section">
+ <h3><span class="secno">3.3 </span>Resource represented as RDF</h3>
+ <p>
+ If a resource is represented as RDF (in any of its recognized syntaxes, including RDFa), it may contain references to its own provenance using additional RDF statements.
+ </p>
+ <p>
+ For this purpose a new RDF property, <code>prov:hasProvenance</code>, is defined as a relation between two resources, where the object of the property is a resource that provides provenance information about the subject resource. Multiple <code>prov:hasProvenance</code> assertions may be made about a subject resource.
+ </p>
+ <p>
+ Another new RDF property, <code>prov:hasAnchor</code>, is defined to allow the RDF content to specify one or more <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>s of the RDF document for the purpose of provenance information (similar to the use of the "anchor" link relation in HTML).
+ </p>
+ <p class="TODO">
+ @@TODO: document namespace. Check naming style. Use provenance model namespace? Define as part of model?<br>
+ @@TODO: example, when vocabulary issues are settled.
+ </p>
+ </div>
+
+ <div id="arbitrary-data" class="section">
+ <h3><span class="secno">3.4 </span>Arbitrary data</h3>
+ <p class="pending">
+ We have so far decided not to try and define a common mechanism for arbitrary data, because it's not clear to us what the correct choice would be. Is this a reasonable position, or is there a real need for a generic solution for provenance discovery for arbitrary, non-web-accessible data objects?
+ </p>
+ <p>
+ If a resource is represented using a data format other than HTML or RDF, and no URI for the resource is known, provenance discovery becomes trickier to achieve. This specification does not define a specific mechanism for such arbitrary resources, but this section discusses some of the options that might be considered.
+ </p>
+ <p>
+ For formats which have provision for including metadata within the file (e.g. JPEG images, PDF documents, etc.), use the format-specific metadata to include a <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>, <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a> and/or <a class="internalDFN" href="#dfn-service-uri">service-URI</a>. Format-specific metadata provision might also be used to include <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> directly in the resource.
+ </p>
+ <p>
+ Use a generic packaging format that can combine an arbitrary data file with a separate metadata file in a known format, such as RDF. At this time, it is not clear what format that should be, but some possible candidates are:
+ </p><ul>
+ <li>MIME multipart/related [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2387">RFC2387</a></cite>]: both email and HTTP are based on MIME or MIME-derivatives, so this has the advantage of working well with the network transfer mechanisms discussed in the motivating scenarios considered.
+ </li>
+ <li>
+ Composite object-packaging work from the digital library community, of which there are several (ORE, MPEG-21, BagIt @@refs) to name a handful. Practical implementations of these seem to commonly be based on the ZIP file format.
+ </li>
+ <li>
+ Packaging formats along the lines of those used for shipping Java web applications or (basically, a ZIP file with a manifest and some imposed structure)
+ </li>
+ <li>
+ Ongoing work in the research community (e.g. <a href="http://eprints.ecs.soton.ac.uk/21587/">Why Linked Data is Not Enough for Scientists</a>, ePub, etc.) to encapsulate data, code, annotations and metadata into a common exchangeable format.
+ </li>
+ </ul>
+ <p></p>
+ <p class="TODO">
+ Fix references in above text.
+ </p>
+ </div>
+
+ </div>
+
+<!-- == Sect 4 =================================================================================== -->
+
+ <div id="provenance-services" class="section">
+ <!--OddPage--><h2><span class="secno">4. </span>Provenance services</h2>
+ <p>
+ This section describes a REST API [<cite><a class="bibref" rel="biblioentry" href="#bib-REST-APIs">REST-APIs</a></cite>] for a provenance service with facilities for discovery and/or retrieval of provenance information, which can be implemented independently of the original resource delivery channels (e.g. by a third party service).
+ </p>
+ <p>
+ All service implementations must respond with a service description (<a href="#service-description" class="sectionRef">section 4.2.1 Service description</a>) when the service URI is dereferenced.
+ Service implementations may provide either discovery, retrieval or both of these services, indicated by presence of the corresponding service URI templates in the service description. Which of these services to provide is a choice for individual service implementations.
+ </p>
+ <p>
+ On the Web, the normal mechanism for retrieving information is to associate it with a URI, and dereference the URI using normal retrieval mechanisms. This approach is enabled using the provenance discovery service mechanism: given the URI of some resource for which provenance information is required, the service returns one or more URIs from which provenance information may be obtained. This approach may be preferred when the provenance service cannot specify the form of URIs used for identifying provenance information, or when there may be more than one source of provenance information known to the provenance service.
+ </p>
+ <p>
+ The provenance retrieval service returns provenance information directly. This mechanism may be preferred when the provenance information is not already presented directly to the web, or is stored in a database with a complex query protocol, or when the provenance service can control the URI from which provenance information is served and avoid the intermediate step of URI discovery.
+ </p>
+
+ <div id="using-the-provenance-service-api" class="section">
+ <h3><span class="secno">4.1 </span>Using the provenance service API</h3>
+ <p>
+ This section describes general procedures for using the provenance service API. Later sections describe the resources presented by the API, and their representation using JSON. <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>gives examples of alternative representations. Normal HTTP content negotiation mechanisms may be used to retrieve representations using formats convenient for the client application.
+ </p>
+
+ <div id="retrieve-provenance-uris-for-a-resource" class="section">
+ <h4><span class="secno">4.1.1 </span>Retrieve Provenance-URIs for a resource</h4>
+ <p>
+ To use the provenance service to retrieve a list of provenance-URIs for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or entity (<code>entity-URI</code>):
+ </p><ol>
+ <li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN" href="#dfn-service-description">service description</a>.</li>
+ <li>Extract the provenance locations template from the service description.</li>
+ <li>Use the provenance locations template with <code>entity-URI</code> for template variable <code>uri</code> to form <code>provenance-locations-URI</code>.</li>
+ <li>Dereference <code>provenance-locations-URI</code> to obtain a <a class="internalDFN" href="#dfn-provenance-locations-resource">provenance locations resource</a> in one of the formats described below.</li>
+ </ol>
+ <p></p>
+ <p>
+ Any or all of URIs in the returned provenance locations may be used to retrieve provenance information, per <a href="#accessing-provenance-information" class="sectionRef">section 2. Accessing provenance information</a>.
+ </p>
+ </div>
+
+ <div id="retrieve-provenance-information-for-a-resource" class="section">
+ <h4><span class="secno">4.1.2 </span>Retrieve Provenance information for a resource</h4>
+ <p>
+ To use the provenance service to directly retrieve provenance information for a resource, starting with the service URI (<code>service-URI</code>) and the URI of the resource or context (<code>entity-URI</code>):
+ </p><ol>
+ <li>Dereference <code>service-URI</code> to obtain a representation of the <a class="internalDFN" href="#dfn-service-description">service description</a>.</li>
+ <li>Extract the provenance information template from the service description.</li>
+ <li>Use the provenance information template with <code>entity-URI</code> for template variable <code>uri</code> to form <code>provenance-URI</code>.</li>
+ <li>Dereference <code>provenance-URI</code> to obtain <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>.</li>
+ </ol>
+ <p></p>
+ </div>
+
+ </div>
+
+ <div id="resources-presented-and-representations-used" class="section">
+ <h3><span class="secno">4.2 </span>Resources presented and representations used</h3>
+
+ <div id="service-description" class="section">
+ <h4><span class="secno">4.2.1 </span>Service description</h4>
+ <p>
+ A provenance <dfn id="dfn-service-description">service description</dfn> describes the provenance discovery and retrieval service and, in particular, provides URI templates [<cite><a class="bibref" rel="biblioentry" href="#bib-URI-template">URI-template</a></cite>] for URIs to access <a title="provenance locations resource" class="internalDFN" href="#dfn-provenance-locations-resource">provenance locations resources</a> and/or <a class="internalDFN" href="#dfn-provenance-information">provenance information</a>. Dereferencing the service URI returns a representation of this service description. The service description <em class="rfc2119" title="may">may</em> contain additional metadata about the service beyond that described here: API clients are expected to ignore any metadata elements they do not understand.
+ </p>
+ <p>
+ This example shows a provenance service description using JSON format [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>], which is presented as MIME content-type <code>application/json</code>.
+ Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>.
+ </p>
+ <pre class="example code">{
+ "provenance_service_uri": "http://example.org/provenance_service/",
+ "provenance_locations_template": "http://example.org/provenance_service/locations/?uri={uri}",
+ "provenance_content_template": "http://example.org/provenance_service/provenance/?uri={uri}"
+}</pre>
+ <p class="issue">
+ Is there any point in including the provenance service URI here? It has been included for consistency with RDF representations, but is functionally redundant.
+ </p>
+ </div>
+
+ <div id="provenance-locations" class="section">
+ <h4><span class="secno">4.2.2 </span>Provenance locations</h4>
+ <p>
+ A <dfn id="dfn-provenance-locations-resource">provenance locations resource</dfn> enumerates one or more <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>s identifying <a class="internalDFN" href="#dfn-provenance-information">provenance information</a> associated with a given resource.
+ </p>
+ <p>
+ The examples below and in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a> are for a given resource URI <code>http://example.org/qdata/</code>, and using the service description example above, its URI would be <code>http://example.org/provenance_service/location/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
+ </p>
+ <p>
+ This example uses JSON format [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC4627">RFC4627</a></cite>], presented as MIME content type <code>application/json</code>.
+ Other examples may be seen in <a href="#provenance-service-format-examples" class="sectionRef">section B. Provenance service format examples</a>.
+ </p>
+ <pre class="example code">{
+ "uri": "http://example.org/qdata/",
+ "provenance": [
+ "http://source1.example.org/provenance/qdata/",
+ "http://source2.example.org/prov/qdata/",
+ "http://source3.example.com/prov?id=qdata"
+ ]
+}</pre>
+ <p class="note">
+ The template might use <code>?uri={+uri}</code> rather than just <code>?uri={uri}</code>, and thereby avoid %-escaping the <code>:</code> and <code>/</code> characters in the given URI, but this could cause difficulties for URIs containing query parameters and/or fragment identifiers. In this case, the client application would need to ensure that any such characters were %-escaped <em>before</em> being passed into a URI-template expansion processor.
+ </p>
+ </div>
+
+ <div id="provenance-information" class="section">
+ <h4><span class="secno">4.2.3 </span>Provenance information</h4>
+ <p>
+ Provenance information about a resource or resources may be returned in any format. It is recommended that the format be one defined by the Provenance Model specification [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>].
+ </p>
+ <p>
+ Assuming a given resource URI <code>http://example.org/qdata/</code>, and
+ using the service description example above, the provenance URI would be <code>http://example.org/provenance_service/provenance/?uri=http%3A%2F%2Fexample.org%2Fqdata%2F</code>.
+ </p>
+ </div>
+
+ </div>
+
+ <!-- <section class="informative"> -->
+ <div id="provenance-service-discovery" class="section">
+ <h3><span class="secno">4.3 </span>Provenance service discovery</h3>
+ <p>
+ This specification does not define any specific mechanism for discovering provenance services. Applications may use any appropriate mechanism, including but not limited to: prior configuration, search engines, service registries, etc.
+ </p>
+ </div>
+
+ </div>
+
+<!-- ===================================================================================== -->
+
+ <div id="querying-provenance-information" class="section">
+ <!--OddPage--><h2><span class="secno">5. </span>Querying provenance information</h2>
+ <p>
+ Simply identifying and retrieving provenance information as a web resource may not always meet the requirements of a particular application or service, e.g.:
+ </p><ul>
+ <li>the entity for which provenance information is required is not identified by a known URI</li>
+ <li>the provenance information for an entity is not directly identified by a known URI</li>
+ <li>a requirement to access provenance information for a number of distinct but related entities in a single atomic operation</li>
+ <li><i>etc.</i></li>
+ </ul>
+ <p></p>
+ <p>
+ A provenance query service provides an alternative way to access provenance information and/or Provenance-URIs. An application will need a provenance query service URI, and some relevant information about the entity whose provenance is to be accessed.
+ </p>
+ <p>
+ The details of a provenance query service is an implementation choice, but for interoperability between different providers and users we recommend use of SPARQL [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-PROTOCOL">RDF-SPARQL-PROTOCOL</a></cite>] [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]. The query service URI would then be the URI of a SPARQL endpoint (or, to use the SPARQL specification language, a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>). The following subsections provide examples for what are considered to be some plausible common scenarios for using SPARQL, and are not intended to cover all possibilities.
+ </p>
+
+ <div id="find-provenance-uri-given-entity-uri-of-resource" class="section">
+ <h3><span class="secno">5.1 </span>Find provenance-URI given entity-URI of resource</h3>
+ <p>
+ If the requester has an <a class="internalDFN" href="#dfn-entity-uri">entity-URI</a>, a simple SPARQL query may be used to return the corresponding <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>. E.g., if the original resource has a entity-URI <code>http://example.org/resource</code>,
+ <code>
+ </code></p><pre class="example code"><code> @prefix prov: <@@TBD>
+ SELECT ?provenance_uri WHERE
+ {
+ <http://example.org/resource> prov:hasProvenance ?provenance_uri
+ }
+ </code></pre><code>
+ </code>
+ <p></p>
+ <p class="TODO">
+ @@TODO: specific provenance namespace and property to be determined by the model or ontology specification?
+ </p>
+ </div>
+
+ <div id="find-provenance-uri-given-identifying-information-about-a-resource" class="section">
+ <h3><span class="secno">5.2 </span>Find Provenance-URI given identifying information about a resource</h3>
+ <p>
+ If the requester has identifying information that is not the URI of the original resource, then they will need to construct a more elaborate query to locate an entity description and obtain its provenance-URI(s). The nature of identifying information that can be used in this way will depend upon the third party service used, further definition of which is out of scope for this specification. For example, a query for a document identified by a DOI, say <code>1234.5678</code>, using the PRISM vocabulary [<cite><a class="bibref" rel="biblioentry" href="#bib-PRISM">PRISM</a></cite>] recommended by FaBio [<cite><a class="bibref" rel="biblioentry" href="#bib-FABIO">FABIO</a></cite>], might look like this:
+ </p><pre class="example code">@prefix prov: <@@TBD>
+@prefix prism: <http://prismstandard.org/namespaces/basic/2.0/>
+SELECT ?provenance_uri WHERE
+{
+ [ prism:doi "1234.5678" ] prov:hasProvenance ?provenance_uri
+}</pre>
+ <p></p>
+ <p class="TODO">
+ @@TODO: specific provenance namespace and property to be determined by the model specification?
+ </p>
+ </div>
+
+ <div id="obtain-provenance-information-directly-given-an-entity-uri-of-a-resource" class="section">
+ <h3><span class="secno">5.3 </span>Obtain provenance information directly given an entity-URI of a resource</h3>
+ <p>
+ This scenario retrieves provenance information directly given the URI of a resource or entity, and may be useful where the provenance information has not been assigned a specific URI, or when the calling application is interested only in specific elements of provenance information.
+ </p>
+ <p>
+ If the original resource has an entity-URI <code>http://example.org/resource</code>, a SPARQL query for provenance information might look like this:
+ </p><pre class="example code">@prefix prov: <@@TBD>
+CONSTRUCT
+{
+ <http://example.org/resource> ?p ?v
+}
+WHERE
+{
+ <http://example.org/resource> ?p ?v
+}</pre>
+ This query essentially extracts all available properties and values available from the query service used that are directly about the specified entity, and returns them as an RDF graph. This may be fine if the service contains <em>only</em> provenance information about the indicated resource, or if the non-provenance information is also of interest. A more complex query using specific provenance vocabulary terms may be needed to selectively retrieve just provenance information when other kinds of information are also available.
+ <p></p>
+ <p class="TODO">
+ @@TODO: specific provenance namespace and property to be determined by the model specification? The above query pattern assumes provenance information is included in direct properties about the entity. When an RDF provenance vocabulary is fully formulated, this may well turn out to not be the case. A better example would be one that retrieves specific provenance information when the vocabulary terms have been defined.
+ </p>
+ </div>
+
+ </div>
+
+<!-- ===================================================================================== -->
+
+ <div id="incremental-provenance-retrieval" class="section">
+ <!--OddPage--><h2><span class="secno">6. </span>Incremental Provenance Retrieval</h2>
+ <p><a class="internalDFN" href="#dfn-provenance-information">Provenance information</a> may be large. While this specification does not define how to implement scalable provenance systems, it does allow for publishers to make available provenance in an incremental fashion. We now discuss two possibilities for incremental provenance retrieval.
+ </p>
+
+ <div id="via-web-retrieval" class="section">
+ <h3><span class="secno">6.1 </span>Via Web Retrieval</h3>
+ <p>Publishers are not required to publish all the provenance information associated with a given entity at a particular <a class="internalDFN" href="#dfn-provenance-uri">provenance-URI</a>. The amount of provenance information exposed is application dependent. However, it is possible to incrementally retrieve (i.e. walk the provenance graph) by progressively looking up provenance information using HTTP. The pattern is as follows:
+ </p><ol>
+ <li>For a given entity (<code>entity-uri-1</code>) retrieve it's associated <code>provenance-uri-1</code> using the HTTP <code>Link</code> header (<a href="#resource-accessed-by-http" class="sectionRef">section 3.1 Resource accessed by HTTP</a>)</li>
+ <li>Dereference <code>provenance-uri-1</code></li>
+ <li>Navigate the provenance information</li>
+ <li>When reaching a dead-end during navigation, that is on encountering a reference to an entity (<code>entity-uri-2</code>) with no provided provenance information, find its provenance-URI and continue from Step 1. (Note: an HTTP HEAD operation may be used to obtain the Link headers without retrieving the entity content.)</li>
+ </ol>
+ <p></p>
+ <p>To reduce the overhead of multiple HTTP requests, a provenance information publisher may link entities to their associated provenance information using the <code>prov:hasProvenance</code> predicate. Thus, the same pattern above applies, except instead of having to retrieve a new <code>Link</code> header field, one can immediately dereference the entity's associated provenance.
+ </p>
+ <p>The same approach can be adopted when using the <a class="internalDFN" href="#dfn-provenance-service">provenance service</a> API (<a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>). However, instead of performing an HTTP HEAD or GET against a resource one queries the provenance service using the given <a class="internalDFN" href="#dfn-entity-uri">entity-uri</a>.
+ </p>
+ </div>
+
+ <div id="via-queries" class="section">
+ <h3><span class="secno">6.2 </span>Via Queries</h3>
+ <p>Provenance information may be made available using a SPARQL endpoint (<a href="#querying-provenance-information" class="sectionRef">section 5. Querying provenance information</a>) [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-PROTOCOL">RDF-SPARQL-PROTOCOL</a></cite>] [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY">RDF-SPARQL-QUERY</a></cite>]. Using SPARQL queries, provenance can be selectively retrieved using combinations of filters and or path queries.
+ </p>
+ </div>
+
+ </div>
+
+<!-- ===================================================================================== -->
+
+ <div id="iana-considerations" class="section">
+ <!--OddPage--><h2><span class="secno">7. </span>IANA considerations</h2>
+ <p>This document requests registration of new link relations, per <a href="http://tools.ietf.org/html/rfc5988#section-6.2.1">section-6.2.1 of RFC 5988</a>.
+ </p>
+ <p class="TODO">
+ @@TODO The following templates should be completed and submitted to link-relations@ietf.org:
+ </p>
+ <div id="registration-template-for-link-relation---provenance" class="section">
+ <h3><span class="secno">7.1 </span>Registration template for link relation: "provenance"</h3>
+ <p>
+ </p><dl>
+ <dt>Relation Name:</dt>
+ <dd>
+ <code>provenance</code>
+ </dd>
+ <dt>Description:</dt>
+ <dd>
+ the resource identified by target IRI of the link provides provenance information about the entity identified by the context link
+ </dd>
+ <dt>Reference:</dt>
+ <dd>
+ @@this spec, @@provenance-model-spec
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ ...
+ </dd>
+ <dt>Application Data:</dt>
+ <dd>
+ ...
+ </dd>
+ </dl>
+ <p></p>
+ </div>
+ <div id="registration-template-for-link-relation---anchor" class="section">
+ <h3><span class="secno">7.2 </span>Registration template for link relation: "anchor"</h3>
+ <p class="pending">
+ The name "anchor" has been used for the link relation name, despite the corresponding URI being described as an entity-URI. This terminology has been chosen to align with usage in the description of the HTTP <code>Link</code> header field, per <a href="http://tools.ietf.org/html/rfc5988#section-5.2">RFC 5988</a>.
+ </p>
+ <p>
+ </p><dl>
+ <dt>Relation Name:</dt>
+ <dd>
+ <code>anchor</code>
+ </dd>
+ <dt>Description:</dt>
+ <dd>
+ when used in conjunction with a "provenance" link, the resource identified by target IRI of the link is an entity for which provenance information may be provided. This may be used, for example, to isolate relevant information from a referenced document that contains provenance information for several entities.
+ </dd>
+ <dt>Reference:</dt>
+ <dd>
+ @@this spec, @@provenance-model-spec
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ ...
+ </dd>
+ <dt>Application Data:</dt>
+ <dd>
+ ...
+ </dd>
+ </dl>
+ <p></p>
+ </div>
+ <div id="registration-template-for-link-relation---provenance-service" class="section">
+ <h3><span class="secno">7.3 </span>Registration template for link relation: "provenance-service"</h3>
+ <p>
+ </p><dl>
+ <dt>Relation Name:</dt>
+ <dd>
+ <code>provenance-service</code>
+ </dd>
+ <dt>Description:</dt>
+ <dd>
+ the resource identified by target URI of the link is an provenance service per <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a> of this specification.
+ </dd>
+ <dt>Reference:</dt>
+ <dd>
+ @@this spec, @@provenance-model-spec
+ </dd>
+ <dt>Notes:</dt>
+ <dd>
+ ...
+ </dd>
+ <dt>Application Data:</dt>
+ <dd>
+ ...
+ </dd>
+ </dl>
+ <p></p>
+ </div>
+ </div>
+
+<!-- ===================================================================================== -->
+
+ <div id="security-considerations" class="section">
+ <!--OddPage--><h2><span class="secno">8. </span>Security considerations</h2>
+ <p>
+ Provenance is central to establishing trust in data. If provenance information is corrupted, it may lead agents (human or software) to draw inappropriate and possibly harmful conclusions. Therefore, care is needed to ensure that the integrity of provenance data is maintained.
+ </p>
+ <p>
+ When using HTTP to access provenance information, or to determine a provenance URI, secure HTTP (https) <em class="rfc2119" title="should">should</em> be used.
+ </p>
+ <p>
+ When retrieving a provenance URI from a document, steps <em class="rfc2119" title="should">should</em> be taken to ensure the document itself is an accurate copy of the original whose author is being trusted (e.g. signature checking, or verifying its checksum against an author-provided secure web service).
+ </p>
+ <p class="TODO">
+ @@TODO ... privacy, access control to provenance (note to self: discussed in Edinburgh linked data provenance workshop). In particular, note that the fact that a resource is openly accessible does not mean that its provenance information should also be.
+ </p>
+ </div>
+
+<!-- ===================================================================================== -->
+
+ <div class="appendix section" id="acknowledgements">
+ <!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
+ <p>
+ The editors acknowledge the contribution and review from members of the provenance working group.
+ </p>
+ <p>
+ Many thanks to Robin Berjon for making our lives so much easier with his cool <a href="http://dev.w3.org/2009/dap/ReSpec.js/documentation.html">ReSpec</a> tool.
+ </p>
+ </div>
+
+<!-- ===================================================================================== -->
+
+ <div class="appendix section" id="provenance-service-format-examples">
+ <!--OddPage--><h2><span class="secno">B. </span>Provenance service format examples</h2>
+ <p>
+ In <a href="#provenance-services" class="sectionRef">section 4. Provenance services</a>, the provenance service description was represented as a JSON-formatted document. As noted, HTTP content negotiation <em class="rfc2119" title="may">may</em> be enabled to retrieve the document in alternative formats. This appendix provides examples of service description document represented using RDF Turtle and XML syntaxes, and XML.
+ </p>
+
+ <div id="rdf-turtle-example-of-service-description" class="section">
+ <h3><span class="secno">B.1 </span>RDF Turtle example of service description</h3>
+ <p>
+ This example uses the RDF Turtle format [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE">TURTLE</a></cite>], presented as MIME content-type <code>text/turtle</code>.
+ </p>
+ <pre class="example code">@prefix provds: <@@TBD@@#> .
+<http://example.org/provenance_service/> a provds:Service_description ;
+ provds:provenance_locations_template "http://example.org/provenance_service/locations/?uri={uri}" ;
+ provds:provenance_content_template "http://example.org/provenance_service/provenance/?uri={uri}"
+ .</pre>
+ <p class="note">
+ The provenance URI templates are encoded in RDF as plain string literals, <em>not</em> as resource URIs.
+ </p>
+ <p class="TODO">
+ Finalize URIs in the above example.
+ </p>
+ </div>
+
+ <div id="rdf-xml-example-of-service-description" class="section">
+ <h3><span class="secno">B.2 </span>RDF/XML example of service description</h3>
+ <p>This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>], and presented as MIME content-type <code>application/xml+rdf</code>.</p>
+ <pre class="example code"><rdf:RDF
+ xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:provds = "@@TBD@@#"
+>
+ <provds:Service_description rdf:about="http://example.org/provenance_service/">
+ example.org <provds:provenance_locations_template>http://example.org/provenance_service/locations/?uri={uri}</provds:location_template> ;
+ <provds:provenance_content_template>http://example.org/provenance_service/provenance/?uri={uri}</provds:provenance_template> ;
+ </provds:Service_description>
+</rdf:RDF></pre>
+ <p class="TODO">
+ Finalize URIs in the above example.
+ </p>
+ </div>
+
+ <div id="plain-xml-example-of-service-description" class="section">
+ <h3><span class="secno">B.3 </span>Plain XML example of service description</h3>
+ <p class="TODO">
+ @@TODO: provide example and schema
+ </p>
+ </div>
+
+ <div id="rdf-turtle-example-of-provenance-locations" class="section">
+ <h3><span class="secno">B.4 </span>RDF Turtle example of provenance locations</h3>
+ <p>
+ This example uses the RDF Turtle format [<cite><a class="bibref" rel="biblioentry" href="#bib-TURTLE">TURTLE</a></cite>], presented as MIME content type <code>text/turtle</code>.
+ </p>
+ <pre class="example code">@prefix prov: <@@TBD@@#> .
+<http://example.org/qdata/> a prov:Entity ;
+ prov:hasProvenance <http://source1.example.org/provenance/qdata/> ;
+ prov:hasProvenance <http://source2.example.org/prov/qdata/> ;
+ prov:hasProvenance <http://source3.example.com/prov?id=qdata>
+ .</pre>
+ <p class="issue">
+ NOTE: The namespace URI used here for the provenance properties is different from that used in the service description. I am anticipating that it will be defined as part of the provenance model. If it is not defined as part of the provenance model, then a property name should be allocated in the provenance discovery service namespace.
+ </p>
+ <p class="TODO">@@TODO: revise to conform with Provenance Model vocabulary; review URIs</p>
+ </div>
+
+ <div id="rdf-xml-example-of-provenance-locations" class="section">
+ <h3><span class="secno">B.5 </span>RDF/XML example of provenance locations</h3>
+ <p>
+ This is essentially the same as the Turtle example above, but encoded in RDF/XML [<cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SYNTAX-GRAMMAR">RDF-SYNTAX-GRAMMAR</a></cite>], and presented with MIME content type <code>application/rdf+xml</code>.
+ </p>
+ <pre class="example code"><rdf:RDF
+ xmlns:rdf = "http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:rdfs = "http://www.w3.org/2000/01/rdf-schema#"
+ xmlns:prov = "@@TBD@@#"
+>
+ <prov:Entity rdf:about="http://example.org/qdata/">
+ <prov:hasProvenance rdf:resource="http://source1.example.org/provenance/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source2.example.org/prov/qdata/" /> ;
+ <prov:hasProvenance rdf:resource="http://source3.example.com/prov?id=qdata" /> ;
+ </prov:Entity>
+</rdf:RDF></pre>
+ <p class="issue">@@TODO: revise to conform with Provenance Model vocabulary</p>
+ </div>
+
+ <div id="plain-xml-example-of-provenance-locations" class="section">
+ <h3><span class="secno">B.6 </span>Plain XML example of provenance locations</h3>
+ <p class="TODO">
+ @@TODO: provide example and schema
+ </p>
+ </div>
+
+ </div>
+
+<!-- ===================================================================================== -->
+
+<!--
+ <section class="appendix">
+ <h2>Motivating scenario</h2>
+ <p class="pending">
+ I propose to replace this appendix with text based on Yogesh's walk-through of the scenario, renaming to be something like "Motivating scenario and examples"
+ </p>
+ <p><a href="http://www.w3.org/2011/prov/wiki/ProvenanceAccessScenario">This scenario</a> was selected by the provenance working group as a touchstone for evaluating any provenance access proposal. This appendix evaluates the foregoing proposals against the requirements implied by that scenario.</p>
+ <p>
+ <ul>
+ <li>Obtaining the document D: for the purpose of this analysis, it is assumed that the access to the document is either from a known Web URI, or the document is available as HTML or RDF (the primary web standards for documents and data). The mechanisms here are in principle applicable to other document forms of a per-format basis.
+ <ul>
+ <li>D1, D2: use the HTTP <code>Link:</code> header. Any server providing the document may provide this information. Different servers might offer links to different provenance sources.</li>
+ <li>D3: information provided as an image with a known URI, but from a non-provenance-aware source. The image URI can be used as a key to access a third party provenance discovery service.
+ <li>D4, D6, D7, D8: information provided as an image, without a known web location. At the very least, some mechanism, not specified here, is needed to identify the image provided. In the case of an email attachment, it is possible (but not guaranteed) that the email message MIME wrapper specifies a URI for the image, which can be used as a key. Some image formats support embedded metadata which might be used for this purpose. <em>(Arbitrary data files could be wrapped in a package, say MIME multipart/related [[RFC2387]], that could include additional metadata. Image files could be wrapped in a minimal HTML document. It is not clear to me at this stage that a single mechanism is appropriate for all situations)</em>.</li>
+ <li>D5: HTML email. Depending on how the HTML is constructed, the HTML header could include <code><link></code> elements.</li>
+ </ul>
+ </li>
+ <li>Lacking identification or in-band metadata, some independent identification of the thing represented by an available mechanism is required. <em>I think this is unavoidable</em></li>
+ <li>Enacting the "Oh yeah?" feature
+ <ul>
+ <li>W: once a URI for provenance information has been determined, accessing it using a web browser or other web client software should be straightforward. If the provenance is accessible via a third party query service, that may be less straightforward.</li>
+ <li>E: this scenario seems to envisage a wholesale overhaul of email client software, which seems unlikely. If a URI for provenance can be provided, the natural way to access it would be via a web client of some kind, which might be a browser or other software.</li>
+ <li>S: this scenario effectively calls for this: given an arbitrary data resource, implement a general purpose application to discover, retrieve and analyze provenance about that resource. At the present time, this is a matter for experimental development, which could be based substantially on the mechanisms described for provenance discovery and access via third party services.</li>
+ </ul>
+ </li>
+ <li>I: Accessing the provenance
+ <ul>
+ <li>W: a web client needs one or more URIs for provenance information, and/or URI(s) for a provenance query service and sufficient additional information about the resource to formulate an effective query. They may also need access information that can be used to assess (or help a user assess) the trustworthiness of provenance of information obtained, (which could be more provenance information)</li>
+ <li>E: an email client is a passive receiver of information, so asking one to retrieve provenance information is a perverse expectation. There have been some attempts to standardize email protocols that interact with the email sender but such mechanisms have not been significantly deployed in practice. This case can be viewed as a variation on the shell-client case (S) below. If all provenance information is sent <em>with</em> the original content using standard email mechanisms (MIME multipart, etc.) then the email client may use that (or hand it off to a helper application) as the basis for provenance-based analysis or presentation.</li>
+ <li>S: command shell or other local application. This is the general case for provenance access. Given some arbitrary information, what does a provenance-aware application need to access the required provenance information? It may employ any of the mechanisms described above.</li>
+ </ul>
+ </li>
+ </ul>
+ </p>
+ <section>
+ <h2>Gap analysis</h2>
+ <p>
+ There are clearly a number of capabilities needed for a provenance-aware application that are not covered by the mechanisms described above. But most of these amount to implementation details and decisions for a particular application, and as such are beyond the scope of this document to specify.
+ </p>
+ <p>
+ One feature not covered above that might be a candidate for specification is a common format for a data package that combines original content along with provenance-related metadata or data. At this stage, it is not clear what format that might take, but some possible candidates are discussed in <a href="#arbitrary-data" class="sectionRef"></a>.
+ In any case, it seems to me that a specification that is specific for provenance to the exclusion of other metadata is unlikely to obtain traction, as provenance is just part of a wider landscape of information quality, trust, preservation and more.
+ </p>
+ </section>
+ </section>
+
+-->
+
+
+
+<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">C. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><p>No normative references.</p></div><div id="informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-FABIO">[FABIO]</dt><dd>D. Shotton; S. Peroni. <a href="http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations"><cite>FaBiO, the FRBR-aligned Bibliographic Ontology.</cite></a> June 2011. URL: <a href="http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations">http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations</a>
+</dd><dt id="bib-LINK-REL">[LINK-REL]</dt><dd>M. Nottingham, <a href="http://www.ietf.org/rfc/rfc5988.txt"><cite>Web Linking</cite></a>, October 2010, Internet RFC 5988. URL: <a href="http://www.ietf.org/rfc/rfc5988.txt">http://www.ietf.org/rfc/rfc5988.txt</a>
+</dd><dt id="bib-POWDER-DR">[POWDER-DR]</dt><dd>Kevin Smith; Phil Archer; Andrea Perego. <a href="http://www.w3.org/TR/2008/WD-powder-dr-20081114"><cite>Protocol for Web Description Resources (POWDER): Description Resources.</cite></a> 14 November 2008. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2008/WD-powder-dr-20081114">http://www.w3.org/TR/2008/WD-powder-dr-20081114</a>
+</dd><dt id="bib-PRISM">[PRISM]</dt><dd>International Digital Enterprise Alliance, Inc. <a href="http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf"><cite>PRISM: Publishing Requirements for Industry Standard Metadata</cite></a>. February 2008. URL: <a href="http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf">http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf</a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>L. Moreau; P. Missier. <a href="http://www.w3.org/TR/prov-dm/"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>S. Sahoo; D. McGuinness. <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html"><cite>PROV Ontology Model</cite></a>. 2011, Work in progress. URL: <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html/">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a>
+</dd><dt id="bib-RDF-SPARQL-PROTOCOL">[RDF-SPARQL-PROTOCOL]</dt><dd>Lee Feigenbaum; Kendall Grant Clark; Elias Torres. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115"><cite>SPARQL Protocol for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-protocol-20080115</a>
+</dd><dt id="bib-RDF-SPARQL-QUERY">[RDF-SPARQL-QUERY]</dt><dd>Andy Seaborne; Eric Prud'hommeaux. <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115"><cite>SPARQL Query Language for RDF.</cite></a> 15 January 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115">http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115</a>
+</dd><dt id="bib-RDF-SYNTAX-GRAMMAR">[RDF-SYNTAX-GRAMMAR]</dt><dd>Dave Beckett. <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210"><cite>RDF/XML Syntax Specification (Revised).</cite></a> 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210">http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210</a>
+</dd><dt id="bib-REST-APIs">[REST-APIs]</dt><dd>R. Fielding. <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">REST APIs must be hypertext driven</a>. October 2008 (blog post), URL: <a href="http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven">http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</a>
+</dd><dt id="bib-RFC2387">[RFC2387]</dt><dd>E. Levinson. <a href="http://www.ietf.org/rfc/rfc2387.txt"><cite>The MIME Multipart/Related Content-type.</cite></a> August 1998. Internet RFC 2387. URL: <a href="http://www.ietf.org/rfc/rfc2387.txt">http://www.ietf.org/rfc/rfc2387.txt</a>
+</dd><dt id="bib-RFC4627">[RFC4627]</dt><dd>D. Crockford. <a href="http://www.ietf.org/rfc/rfc4627.txt"><cite>The application/json Media Type for JavaScript Object Notation (JSON)</cite></a> July 2006. Internet RFC 4627. URL: <a href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a>
+</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd>David Beckett, Tim Berners-Lee. <a href="http://www.w3.org/TeamSubmission/turtle/"><cite>Turtle: Terse RDF Triple Language.</cite></a> January 2008. W3C Team Submission. URL: <a href="http://www.w3.org/TeamSubmission/turtle/">http://www.w3.org/TeamSubmission/turtle/</a>
+</dd><dt id="bib-URI-template">[URI-template]</dt><dd>J. Gregorio; R. Fielding, ed.; M. Hadley; M. Nottingham. <a href="http://tools.ietf.org/html/draft-gregorio-uritemplate-06"><cite>URI Template</cite></a>. July 2011, Work in progress. URL: <a href="http://tools.ietf.org/html/draft-gregorio-uritemplate-06"><cite>http://tools.ietf.org/html/draft-gregorio-uritemplate-06</cite></a>
+</dd><dt id="bib-WEBARCH">[WEBARCH]</dt><dd>Norman Walsh; Ian Jacobs. <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/"><cite>Architecture of the World Wide Web, Volume One.</cite></a> 15 December 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">http://www.w3.org/TR/2004/REC-webarch-20041215/</a>
+</dd></dl></div></div></body></html>
\ No newline at end of file
--- a/paq/prov-aq.html Wed Dec 14 00:09:57 2011 +0000
+++ b/paq/prov-aq.html Wed Dec 14 00:11:16 2011 +0000
@@ -44,10 +44,10 @@
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "FPWD",
+ specStatus: "FPWD-NOTE",
// the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "PROV-AQ",
+ shortName: "prov-aq",
// if your specification has a subtitle that goes below the main
// formal title, define it here
@@ -141,11 +141,15 @@
<section id='abstract'>
- This document describes the use of existing mechanisms for accessing and querying provenance data about resources on the web.
+This document specifies how to use standard Web protocols,
+including HTTP, to obtain information about the provenance of Web
+resources. We describe both simple access mechanisms for
+locating provenance information associated with web pages or resources, and
+provenance query services for more complex deployments. This is
+part of the larger W3C Prov provenance framework.
</section>
<section id="sotd">
- Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document is part of a set of specifications produced by the W3C provenance working group aiming to define interoperable interchange of provenance information in heterogeneous environments such as the Web. It describes the use of existing web mechanisms for discovery and retrieval of provenance information.
</section>
--- a/primer/Primer.html Wed Dec 14 00:09:57 2011 +0000
+++ b/primer/Primer.html Wed Dec 14 00:11:16 2011 +0000
@@ -1,964 +1,1010 @@
-<!DOCTYPE html>
-<html><head>
- <title>Prov Model Primer</title>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
- <!--
- === NOTA BENE ===
- For the three scripts below, if your spec resides on dev.w3 you can check them
- out in the same tree and use relative links so that they'll work offline,
- -->
- <!-- PM -->
- <style type="text/css">
- .note { font-size:small; margin-left:50px }
- </style>
-
- <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
-
- <script class="remove">
- var respecConfig = {
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
-
- // the specification's short name, as in http://www.w3.org/TR/short-name/
- shortName: "Prov-Primer",
-
- // if your specification has a subtitle that goes below the main
- // formal title, define it here
- subtitle : "Initial draft for internal discussion",
-
- // if you wish the publication date to be other than today, set this
- // publishDate: "2009-08-06",
-
- // if the specification's copyright date is a range of years, specify
- // the start date here:
- // copyrightStart: "2005"
-
- // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
- // and its maturity status
- // previousPublishDate: "1977-03-15",
- // previousMaturity: "WD",
-
- // if there a publicly available Editor's Draft, this is the link
- edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html",
-
- // if this is a LCWD, uncomment and set the end of its review period
- // lcEnd: "2009-08-05",
-
- // if you want to have extra CSS, append them to this list
- // it is recommended that the respec.css stylesheet be kept
- extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css", "./extra.css"],
-
- // editors, add as many as you like
- // only "name" is required
- editors: [
- { name: "Yolanda Gil", url: "http://www.isi.edu/~gil/",
- company: "Information Sciences Institute, University of Southern California, US" },
- { name: "Simon Miles", url: "http://www.inf.kcl.ac.uk/~simonm",
- company: "King's College London, UK" },
- ],
-
- // authors, add as many as you like.
- // This is optional, uncomment if you have authors as well as editors.
- // only "name" is required. Same format as editors.
-
- authors: [
- { name: "TBD"},
- ],
-
- // name of the WG
- wg: "Provenance Working Group",
-
- // URI of the public WG page
- wgURI: "http://www.w3.org/2011/prov/wiki/Main_Page",
-
- // name (with the @w3c.org) of the public mailing to which comments are due
- wgPublicList: "public-prov-wg",
-
- // URI of the patent status for this WG, for Rec-track documents
- // !!!! IMPORTANT !!!!
- // This is important for Rec-track documents, do not copy a patent URI from a random
- // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
- // Team Contact.
- wgPatentURI: "",
- };
- </script>
- </head>
- <body>
- <section id="abstract">
- <p>This document aims to provide an intuitive guide to the PROV Data Model,
- with worked examples.</p>
-
- <p>
- This is a document for internal discussion, which will ultimately
- evolve in the first Public Working Draft of the Primer.</p>
- </section>
-
- <section>
- <h2>Introduction</h2>
- <p>
- This primer document provides an accessible introduction to the PROV Data Model
- (PROV-DM) standard for representing provenance on the Web, and its representation
- in the PROV Ontology (PROV-O). Provenance describes
- the origins of things, so PROV-DM data consists of assertions about the past.
- </p>
-
- <p>
- This primer document aims to ease the adoption of the standard by providing:
- </p>
- <ul>
- <li>An intuitive explanation of how PROV-DM models provenance.</li>
- <li>Worked examples that can be followed to produce your own PROV-DM data.</li>
- <li>Answers to frequently asked questions regarding how the model should be applied.</li>
- </ul>
-
- <p>
- The provenance of digital objects represents their origins. The PROV-DM is a
- proposed standard to represent provenance records, which reflect the entities
- and activities involved in producing and delivering or otherwise influencing a
- given object. By knowing the provenance of an object, we can make determinations
- about how to use it. Provenance records can be used for many purposes, such as
- understanding how data was collected so it can be meaningfully used, determining
- ownership and rights over an object, making judgments about information to
- determine whether to trust it, verifying that the activity used to obtain a
- result complies with given requirements, and reproducing how something it was generated.
- </p>
-
- <p>
- As a standard for provenance, PROV-DM accommodates all those different uses
- of provenance. However, different people may have different perspectives on provenance,
- and as a result different types of information might be captured in a provenance record.
- One perspective might focus on <i>agent-centered provenance</i>, that is, what entities
- were involved in generating or manipulating the information in question. For example,
- in the provenance of a picture in a news article we might capture the photographer who
- took it, the person that edited it, and the newspaper that published it. A second perspective
- might focus on <i>object-centered provenance</i>, by tracing the origins of portions of a
- document to other documents. An example is having a web page that was assembled from content
- from a news article, quotes of interviews with experts, and a graph that plots data from a
- government agency. A third perspective one might take is on <i>process-centered provenance</i>,
- capturing the actions and steps taken to generate the information in question. For example, a
- graph may have been generated by invoking a service to retrieve data from a database, and then
- extracting certain statistics from the data using some statistics package.
- </p>
-
- <p>
- Provenance records are metadata. There are other kinds of metadata that is
- not provenance. For example, the size of an image is a metadata property of
- that image but it is not provenance.
- </p>
-
- <p>
- A comprehensive overview of requirements, use cases, prior research, and proposed
- vocabularies for provenance are available from the
- <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov/">Final Report of the W3C Provenance Incubator Group</a>.
- The document contains three general scenarios
- that may help identify the provenance aspects of your planned applications and
- help plan the design of your provenance system.
- </p>
- <p>
- For a detailed description of PROV-DM, please refer to the
- <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">PROV Data Model and Abstract Syntax Notation Document</a>.
- </p>
- </section>
-
- <section>
- <h2>Intuitive overview of PROV-DM</h2>
-
- <p><i>This section provides an intuitive explanation of the concepts in PROV-DM.
- As with the rest of this document, it should be treated as a starting point for
- understanding the model, and not normative in itself. The model specification
- provides the precise definitions and constraints to be followed in using PROV-DM.</i></p>
-
- <section>
- <h3>Entities</h3>
-
- <p>
- In PROV-DM, the things that you may ask the provenance of are called <i>entities</i>.
- An entity’s provenance may refer to many other entities. For example, a document D is
- an entity whose provenance refers to other entities such as a graph inserted into D,
- the dataset that was used to create that graph, or the author of the document.
- </p>
- <p>
- Entities are described and identified by their attributes, may be more
- or less specific, and may be described from different perspectives. For example,
- document D, the second version of document D, and document D as stored on my file system,
- are three distinct entities for which we may describe the provenance. They
- may all be perspectives on the same thing in the world (document D may exist only
- in its second version and on my file system), but are <i>characterized</i> in
- different ways by being described using different <i>attributes</i> (version, location, and
- so on).
- </p>
- <p>
- The characterization of an entity means that the provenance assertions
- about the entity are only about the thing when it has those attributes.
- For example, the second version of document D is characterized by being the
- second version, and so assertions about who reviewed that entity apply only
- to the document as it is in its second version. When the document becomes
- the third version, a new entity exists (the third version of D) and the
- provenance assertions about who reviewed the second version do not apply.
- </p>
- </section>
-
- <section>
- <h3>Activities</h3>
-
- <p>
- While entities are static aspects in the world (things), <i>activities</i> are
- dynamic aspects (actions, processes, etc.)
- An activity is something that has either occurred or is still
- taking place. Most importantly, activities are how entities come into
- existence, often making use of previously existing entities to achieve this.
- For example, if the second version of document D was generated
- by a translation from the first version of the document in another language,
- then this translation is an activity.
- </p>
- </section>
-
- <section>
- <h3>Use and Generation</h3>
-
- <p>
- Every entity is created by an activity, which is called the <i>generation</i> of the entity.
- For example, writing a document brings the document into existence, while
- revising the document brings a new version into existence.
- Activities also make <i>use</i> of entities. For example, revising a document
- to fix spelling mistakes uses the original version of the document as well
- as a list of corrections. In PROV-DM, assertions can be made to state that
- particular activities used or generated particular entities.
- </p>
- </section>
-
- <section>
- <h3>Agents</h3>
-
- <p>
- An agent is a type of entity that takes an active role in an activity such
- that it can be assigned some degree of responsibility for the activity taking
- place. An agent can be a person, a piece of software, or an inanimate object.
- In PROV-DM, agents are a kind of entity, and it is therefore possible to
- associate provenance with agents. Consider a graph displaying some statistics
- regarding crime rates over time in a linear regression. To represent the
- provenance of a that graph, we could state that the person who created the
- graph was an agent involved in its creation, and that the software used to
- create the graph was also an agent involved in that activity. We
- can also represent the provenance of that software and the agents involved in
- that, such as the vendor of that software.
- </p>
- </section>
-
- <!--section>
- <h3>Accounts</h3>
-
- <p>An intuitive overview of how to think about accounts in PROV-DM.</p>
- </section -->
-
- <section>
- <h3>Roles</h3>
-
- <p>
- A role is a description of the function or part an entity
- played in an activity. In PROV-DM data, roles are qualifying, application-specific,
- information about the relationship between an entity and an activity, whether
- that is how an activity used an entity, generated an entity, or was controlled by an agent.
- For example, an agent may play the role of "editor" in an activity that uses
- one entity in the role of "document to be edited" and another in the role of "edits
- to be made", to generate a further entity in the role of "edited document".
- </p>
- <!--p>Roles are intended as an extension point in the model; it is expected users will define and use custom role taxonomies. Role interpretation is application specific.</p -->
- </section>
-
- <section>
- <h3>Revisions</h3>
-
- <p>
- A single resource, such as a document, may go through multiple revisions
- (also called versions and other comparable terms) over time. Between revisions,
- several changes may have taken place to the resource, each possibly controlled
- by different agents. The result of each revision is, in PROV-DM terms, an entity,
- and PROV-DM allows one to relate those entities by making an assertion that
- one is a revision of another.
- </p>
- </section>
-
- <section>
- <h3>Complementarity</h3>
- <p>
- As described above, entities can be described from different perspectives,
- by being characterized by different attributes. For example, "document D",
- "the second version of document D" and "document D as stored on my filesystem"
- are different entities
- because they are characterized in different ways. However, for some period of time
- they may all refer to the same thing in the world, e.g. for a while the copy of
- D on my filesystem <i>was</i> the second version.
- </p>
- <p>
- In PROV-DM, we say there is <i>complementarity</i> between one entity and another
- if, in some period of time, they have the same or compatible characterization.
- So, both "the second version of document D" and "document D as stored on my filesystem"
- are complements of "document D", because they are both characterized by being
- document D, but with specific additional attributes.
- If, at some point in time, a version of D stored on my filesystem is the second one, then
- "document D as stored on my filesystem" and "the second version of document D" are
- complements of each other.
- </p>
-
- <!-- p>
- Several asserted entities could be characterizing the same thing, in
- particular when entities are asserted by different <em>accounts</em> or over
- different time periods. If two such entities have <em>overlapping
- lifespans</em>, and the first entity have some <em>attributes</em> that
- have not been asserted (and not necessarily always true) for the second entity,
- then the first entity is said to be <em>complementing</em> the second
- entity, that is the first entity helps form a more detailed
- description of the second entity, at least for the duration of the
- overlapping lifespan.
- </p>
- <p>
- In addition, if <code>:A prov:wasComplementOf :B</code>, then of all the
- attributes of the entity <code>:A</code> which can be <em>mapped</em> to
- <em>compatible</em> attributes of <code>:B</code> MUST be <em>matching</em>
- for the continuous duration of the overlap of <code>:A</code> and
- <code>:B</code>'s lifespans.
- It is out of scope for PROV to specify or assert the nature of
- the <em>compatibility mapping</em> and <em>matching</em>, the exact
- interpretation of these is left to the asserter of
- <code>wasComplementOf</code>
- </p>
- <p>
- If <code>:B</code> also have some attributes which
- are not asserted (or not always true) about <code>:A</code>,
- then this MAY be asserted using the
- inverse relation <code>:B prov:wasComplementOf :A</code>. If two entities
- both complement each other in this manner, both MUST have some
- attributes the other does not have, although those attributes MAY
- not have been asserted in the provenance. Note that the
- <em>lack</em> of such an inverse assertion does not neccessarily
- mean that <code>:B</code> did not have any additional attributes
- for <code>:A</code> in the timespan, only that this has not
- been asserted.
- </p>
- <p>
- In the simplest case, both entites are described using the same
- attributes, in which case <em>matching</em> means the values SHOULD
- literally be the same (matching by identity). On the other hand an
- attribute like <code>ex1:speed_in_mph</code> can be <em>mapped</em> to
- a compatible <code>ex2:speed_in_kmh</code> attribute. Not all
- attributes might be mappable in both directions, for instance
- <code>ex1:city</code> to <code>ex2:country</code>, but not vice
- versa.
- </p>
- <p>
- Note that it is out of scope for PROV to assert or explain any
- mapping of compatible attributes. This is merely a conclusion
- that can be drawn from the assertion that the two entities both
- described the same thing in the overlapping time spans. Also note
- that asserting a complementary relationship does not detail how the
- two entity timespans overlap, this could be anything from
- complete one-to-one match (where all attributes are always true for
- both entities) to merely touching overlaps.
- </p -->
- </section>
-
- <section>
- <h3>Derivation</h3>
-
- <p>
- When one entity's existence, content, characteristics and so on are
- at least partly due to another entity, then we say that the former is
- derived from the latter. For example, one document may contain
- material copied from another, a child is derived from his/her
- ancestors, and a page displayed in a browser is derived from the same
- page on the web server from which it was downloaded, as well as from
- the designer's original sketches of what the page would look like.
- </p>
- <p>
- There are different kinds of derivation expressible in PROV-DM.
- Consider the case of the page in the browser above. It is derived from
- the designer's sketch in the strictest sense, i.e. if the sketch had
- been different so would the page. On the other hand, there are
- entities that are part of the page's history but which did not inform
- the content of that page, i.e. the page would have been the same even
- if the earlier entity changed. For example, on creating the original
- draft of the page, the designer may have included a banner image
- saying "DRAFT - FOR REVIEW ONLY". This banner was not part of the
- sketch, nor part of the published page downloaded to the browser, but
- was part of the page's history, and while not affecting the browsed
- page's content may have been a factor in its existence. Finally, in
- some cases, we may be able to say not only that one entity was derived
- from another, but also how it was derived, i.e. by what activity.
- For example, the page in the browser is derived from the
- page on the web server because a download activity sent the bytes of
- the latter across an HTTP connection to the browser client.
- </p>
- <p>
- In PROV-DM terms, we say that the page in the browser <i>was eventually
- derived from</i> the sketch, <i>depended on</i> the banner image, and <i>was derived
- from</i> the page on the web server due to the download activity.
- </p>
- </section>
- </section>
-
- <section>
- <h2>Worked Examples</h2>
-
- <p>In the following sections, we show how PROV-DM can be used to model
- provenance in specific examples.</p>
-
- <p>We include examples of how the formal ontology
- can be used to represent the PROV-DM assertions as RDF triples.
- These are shown using the Turtle notation. In
- the latter depictions, the namespace prefix <b>prov</b> denotes
- terms from the Prov ontology, while <b>ex1</b>, <b>ex2</b>, etc.
- denote terms specific to the example.</p>
-
- <p>We also provide a representation of the examples in the Abstract
- Syntax Model used in the conceptual model document. The full ASM data is
- included in the appendix.</p>
-
- <section>
- <h3>Entities</h3>
-
- <p>
- An online newspaper publishes an article making using of data (GovData) provided through a government portal, in England.
- The article includes a chart based on GovData, with data values aggregated by
- regions of the country.
- </p>
- <p>
- A blogger, Betty, looking at the chart, spots what she thinks to be an error.
- Betty retrieves the provenance of the chart, to determine from where the facts presented derive.
- </p>
- <p>The Prov data includes the assertions:</p>
- <pre class="turtle example">
- ex1:dataSet1 a prov:Entity .
- ex1:regionList1 a prov:Entity .
- ex1:aggregate1 a prov:Entity .
- ex1:chart1 a prov:Entity .
- </pre>
- <p>
- These statements, in order, assert that the original data set is an entity (<code>ex1:dataSet1</code>),
- the list of regions
- (<code>ex1:regionList1</code>) is an entity, the data aggregated by region is an entity (<code>ex1:aggregate1</code>),
- and the chart (<code>ex1:chart1</code>) is an entity.
- </p>
-
- </section>
-
- <section>
- <h3>Activities</h3>
-
- <p>
- Further, the Prov data asserts that there was
- an activity (<code>ex1:compiled</code>) denoting the compilation of the
- chart from the data set.
- </p>
- <pre class="turtle example">
- ex1:compiled a prov:Activity .
- </pre>
- <p>
- The provenance also includes reference to the steps involved in compilation,
- aggregating the data by region and generating the chart graphic.
- </p>
- <pre class="turtle example">
- ex1:aggregated a prov:Activity .
- ex1:illustrated a prov:Activity .
- </pre>
- </section>
-
- <section>
- <h3>Use and Generation</h3>
-
- <p>
- Finally, the Prov data asserts the key events that connected the above
- entities and activities, i.e. the use of an entity by an activity,
- or the generation of an entity by an activity.
- </p>
- <p>
- For example, the data below states that the aggregation activity
- (<code>ex1:aggregated</code>) used the data set, that it used the list of
- regions, and that the aggregated data was generated by this activity.
- </p>
- <pre class="turtle example">
- ex1:aggregated prov:used ex1:dataSet1 ;
- prov:used ex1:regionList1 .
- ex1:aggregate1 prov:wasGeneratedBy ex1:aggregated .
- </pre>
- <p>
- Similarly, the chart graphic creation activity (<code>ex1:illustrated</code>)
- used the aggregated data, and the chart was generated by this activity.
- </p>
- <pre class="turtle example">
- ex1:illustrated prov:used ex1:aggregate1 .
- ex1:chart1 prov:wasGeneratedBy ex1:illustrated .
- </pre>
-
- <!-- p>
- For example, the provenance declares the event (of type <code>prov:Usage</code>)
- where the aggregation activity used the GovData data set, and the event
- (of type <code>prov:Generation</code>) where the same activity generated
- the data aggregated by region.
- </p>
- <pre class="turtle example">
- ex1:dataSet1Usage a prov:Usage .
- ex1:aggregate1Generation a prov:Generation .
- </pre>
- <p>
- To describe these events, the provenance says within which activity
- they occur and what entity is used or generated.
- </p>
- <pre class="turtle example">
- ex1:aggregated prov:qualifiedUsage ex1:dataSet1Usage .
- ex1:aggregated prov:qualifiedGeneration ex1:aggregate1Generation .
- ex1:dataSet1Usage prov:entity ex1:dataSet1 .
- ex1:aggregate1Generation prov:entity ex1:aggregate1 .
- </pre>
- <p>
- Comparable events are described for the activity of generating the chart image
- from the aggregated data.
- </p>
- <pre class="turtle example">
- ex1:aggregate1Usage a prov:Usage .
- ex1:chart1Generation a prov:Generation .
- ex1:illustrated prov:qualifiedUsage ex1:aggregate1Usage .
- ex1:illustrated prov:qualifiedGeneration ex1:chart1Generation .
- ex1:aggregate1Usage prov:entity ex1:aggregate1 .
- ex1:chart1Generation prov:entity ex1:chart1 .
- </pre -->
- <p>
- From this information Betty can see that
- the mistake could have been in the original data set or else was introduced
- in the compilation activity, and sets out to discover which.
- </p>
-
- </section>
-
- <section>
- <h3>Agents</h3>
-
- <p>
- Digging deeper, Betty wants to know who compiled the chart. Betty sees
- that both the aggregation and chart creation activities were controlled
- by the Derek.
- </p>
- <pre class="turtle example">
- ex1:aggregated prov:wasControlledBy ex1:derek .
- ex1:illustrated prov:wasControlledBy ex1:derek .
- </pre>
- <p>
- The record for Derek provides the
- following information, of which the first line is a PROV-O statement that
- Derek is a (PROV-DM) agent.
- </p>
- <pre class="turtle example">
- ex1:derek a prov:Agent ;
- a foaf:Person ;
- foaf:givenName "Derek"^^xsd:string ;
- foaf:mbox <mailto:dererk@example.org> .
- </pre>
- </section>
-
- <!-- section>
- <h3>Accounts</h3>
-
- <p><i>Suggested example:</i> The analyst provides his own record of how he compiled GovData to create
- the chart, which provides more detail than in the newspaper's provenance data.
- Specifically, the analysts account separates compilation into two stages: aggregating
- data by region and then producing the graphic. Therefore, there are two separate
- accounts of the same events.</p>
- </section -->
-
- <section>
- <h3>Roles</h3>
-
- <p>
- For Betty to understand where the error lies, she needs to have more detailed
- information on how entities have been used in, participated in, and generated
- by activities. Betty has determined that <code>ex1:aggregated</code> used
- entities <code>ex1:regionList1</code> and <code>ex1:dataSet1</code>, but she does not
- know what function these entities played in the processing. Betty
- also knows that <code>ex1:derek</code> controlled the activities, but she does
- not know if Derek was the analyst responsible for determining how the data
- should be aggregated.
- </p>
- <p>
- The above information is described as roles in the provenance data. The aggregation
- activity involved entities in four roles: the data to be aggregated (<code>ex1:dataToAggregate</code>),
- the regions to aggregate by (<code>ex1:regionsToAggregateBy</code>), the
- resulting aggregated data (<code>ex1:aggregatedData</code>), and the
- analyst doing the aggregation (<code>ex1:analyst</code>).
- </p>
- <pre class="turtle example">
- ex1:dataToAggregate a prov:Role .
- ex1:regionsToAggregateBy a prov:Role .
- ex1:aggregatedData a prov:Role .
- ex1:analyst a prov:Role .
- </pre>
- <p>
- In addition to the simple facts that the aggregation activity used, generated or
- was controlled by entities/agents as described in the sections above, the
- provenance data contains more details of <i>how</i> these entities and agents
- were involved, i.e. the roles they played. For example, the data below states
- that the aggregation activity (<code>ex1:aggregated</code>) included the usage
- of the GovData data set (<code>ex1:dataSet1</code>) in the role of the data
- to be aggregated (<code>ex1:dataToAggregate</code>).
- </p>
- <pre class="turtle example">
- ex1:aggregated prov:hadQualifiedUsage [ a prov:Usage ;
- prov:hadQualifiedEntity ex1:dataSet1 ;
- prov:hadRole ex1:dataToAggregate ] .
- </pre>
- <p>
- This can then be distinguished from the same activity's usage of the list of
- regions because the roles played are different.
- </p>
- <pre class="turtle example">
- ex1:aggregated prov:hadQualifiedUsage [ a prov:Usage ;
- prov:hadQualifiedEntity ex1:regionList1 ;
- prov:hadRole ex1:regionsToAggregateBy ] .
- </pre>
- <p>
- Similarly, the provenance includes assertions that the same activity was
- controlled in a particular way (<code>ex1:analyst</code>) by Derek, and that
- the entity <code>ex1:aggregate1</code> took the role of the aggregated
- data in what the activity generated.
- </p>
- <pre class="turtle example">
- ex1:aggregated
- prov:hadQualifiedControl [ a prov:Control ;
- prov:hadQualifiedEntity ex1:derek ;
- prov:hadRole ex1:analyst
- ] ;
- prov:hadQualifiedGeneration [ a prov:Generation ;
- prov:hadQualifiedEntity ex1:aggregate1 ;
- prov:hadRole ex1:aggregatedData
- ] .
- </pre>
- </section>
-
- <section>
- <h3>Revision</h3>
-
- <p>
- After looking at the detail of the compilation activity, there appears
- to be nothing wrong, so Betty concludes the error is in GovData. She contacts
- the government, and a new version of GovData is created, declared to be the
- next revision of the data by Edith. The provenance data now includes a statement
- that the new data set, <code>ex1:dataSet2</code> is a new revision of the
- old data set, <code>ex1:dataSet1</code>.
- </p>
- <pre class="turtle example">
- ex1:dataSet2 prov:wasRevisionOf ex1:dataSet1 .
- </pre>
- </section>
-
- <section>
- <h3>Complementarity</h3>
-
- <p>Betty lets Derek know that a new revision of the data set exists,
- and he looks at the provenance of the new data to understand what he needs to
- re-analyze. </p>
- <p>In addition to specifying that
- <code>ex1:dataSet2</code> is a new revision of
- <code>ex1:dataSet1</code>, the provenance from DataGov also
- asserts that both of these entities were a <em>complement of</em>
- another entity <code>ex1:dataSet</code>.
- </p>
- <pre class="turtle example">
- ex1:dataSet1 prov:wasComplementOf ex1:dataSet .
- ex1:dataSet2 prov:wasComplementOf ex1:dataSet .
- </pre>
- <!--
- <pre class="asn example">
- wasComplementOf(ex1:dataSet1, ex1:dataSet)
- wasComplementOf(ex1:dataSet2, ex1:dataSet)
- </pre>
- -->
- <p>
- This assertion means that <code>ex1:dataSet1</code> at some point shared
- its characterizing attributes with <code>ex1:dataSet</code>, and the same for
- <code>ex2:dataSet2</code>. Thus the <em>entity</em>
- <code>ex1:dataSet1</code> did at some point represent the same
- thing as characterized by the entity <code>ex1:dataSet</code>. The same is
- true for <code>ex1:dataSet2</code>, though not necessarily at the
- same point in time.
- </p>
- <!-- p>
- The term <em>was complement of</em> here means that the
- <code>ex1:dataSet1</code>
- provide additional details that adds to the details of
- <code>ex1:dataSet</code> (complementing it), and that both of these
- entities represented the same thing.
- Characterizing attributes of <code>ex1:dataSet</code> are from this
- asserted to have been <em>compatible</em> with the properties of
- <code>ex1:dataSet1</code> and <code>ex1:dataSet2</code>.
- <em>Compatible</em> here means that some kind of mapping can be
- established between the attributes, they don't neccessarily have to
- match directly.
- </p -->
- <p>
- Derek then looks at the characterization of the generalized data set
- (<code>ex1:dataSet</code>) to find the attributes shared with the first
- and second versions of the data set. The assertions below give the generalized
- data set's attributes: it is of type <code>ex1:DataSet</code>, it covers
- three named regions, it was created by <code>ex1:DataGov</code>, and
- has a given title.
- </p>
- <pre class="example turtle">
- ex1:dataSet a ex1:DataSet ;
- ex1:regions ( ex1:North, ex1:NorthWest, ex1:East ) ;
- dc:creator ex1:DataGov ;
- dc:title "Regional incidence dataset 2011" .
- </pre>
- <p>
- As <code>ex1:dataSet1</code> and <code>ex1:dataSet2</code> complement
- <code>ex1:dataSet</code>,
- Derek can deduce from the above attributes that both the former had
- these same attributes at some point, i.e.
- the creator <code>ex1:DataGov</code> and so on. Derek compares the above
- assertions to the
- attributes of <code>ex1:dataSet1</code>.
- </p>
- <pre class="example turtle">
- ex1:dataSet1 a ex1:DataSet ;
- ex1:postCodes ( "N1", "N2", "NW1", "E1", "E2" ) ;
- ex1:totalIncidents 141 ;
- dc:creator ex1:DataGov ;
- dc:title "Regional incidence dataset 2011" .
- </pre>
- <p>
- Shared characterizing attributes are not necessarily represented in
- the serialized assertions of different entities. For example, the creator
- and title are exactly the same for <code>ex1:dataSet</code> and <code>ex1:dataSet1</code>,
- but the regions covered by the data set are described in a different way:
- "regions" for <code>ex1:dataSet</code> and "postCodes" for <code>ex1:dataSet1</code>.
- Whether these are equivalent is a domain-specific judgment.
- We can also see that, while <code>ex1:dataSet1</code> complements <code>ex1:dataSet</code>,
- the inverse is not true. <code>ex1:dataSet1</code> is more specific, because
- it has a "totalIncidents" attribute specific to that version of the data set.
- </p>
- <!-- p>
- Derek sees that the creator and title are directly mappable and
- equal between these entities. He also knows (from his region
- aggregation method) that the <code>ex1:postCodes</code> <code>N1</code> and
- <code>N2</code> are in the
- region <code>ex1:North</code>, and so on, and can confirm that although
- this regional characterisation of the data is not expressed
- using the same attributes in the two entities, they are <em>compatible</em>.
- </p>
- <p>Derek notes that <code>ex1:totalIncidents</code> is not stated
- for <code>ex1:dataSet</code>, and not mappable to any of the
- other existing attributes. Thus this could be one of the
- complementing attributes that makes <code>ex1:dataSet1</code>
- more specific than <code>ex1:dataSet</code>.
-
- Derek can from the assertion <code>ex1:dataSet1
- prov:wasComplementOf ex1:dataSet</code>
- see that <code>ex1:dataSet</code>
- did have 141 incidents when its characterization interval
- overlapped that of <code>ex1:dataSet1</code>, but not neccessarily
- throughout its lifetime. Note that in this example the provenance
- assertions are not providing any direct description of the
- characterization interval of the entities.
- </p>
- <p>
- Due to the open world assumption (more
- information might be added later) he can not conclude
- from this alone that <code>ex1:dataSet</code> at any point did
- <strong>not</strong> have 141 incidents. He therefore does not know
- for sure that <code>ex1:totalIncidents</code> is a complementing
- attribute which <code>ex1:dataSet</code> does not have in its
- characterisation.
- </p>
- <p>
- Derek finally compares the newer revision
- <code>ex1:dataSet2</code> with
- <code>ex1:dataSet</code>:
- </p>
- <pre class="example turtle">
- ex1:dataSet2 a ex1:DataSet ;
- ex1:postCodes ( "N1", "N2", "NW1", "NW2", "E1", "E2" ) ;
- ex1:totalIncidents 158 ;
- dc:creator ex1:DataGov ;
- dc:title "Regional incidence dataset 2011" .
- </pre>
- <p>
- In this revision, the new postcode <kbd>NW2</kbd> appears, this is still
- <em>compatible</em> with the region <code>ex1:NorthWest</code>
- of <code>ex1:dataSet</code>
- On the other hand, the attribute <code>prov:totalIncidents</code> have gone up to 158.
- </p>
- <p>
- From the <code>prov:wasComplementOf</code> assertion Derek knows that
- <code>ex1:dataSet2</code> also provides additional attributes for
- <code>ex1:dataSet</code>, but because the total incidents can't
- both be 141 and 158, the attribute <code>ex1:totalIncidents</code>
- is a complementing attribute, and changes over the
- characterisation interval (lifespan) of <code>ex1:dataSet</code>,
- and is thus not one of its characterising attributes. He also now
- knows that <code>ex1:dataSet</code> is a common characterisation
- of the dataset that spans (parts of) both revisions. It has
- however not been asserted explicitly that the
- <code>ex1:dataSet</code> is a somewhat more general
- characterisation, just that it allows mutability on the
- <code>prov:totalIncidents</code> attribute and overlapped (parts
- of) the timespans of the two revisions.
- </p>
- <p>
- From this Derek concludes that he can still use the regions North,
- North West and East in the diagram layout, but as the
- <code>ex1:totalIncidents</code> differ, something in the
- raw data has changed. He can't from this provenance assertion
- alone tell if that is merely from the addition of the post code
- NW2, or if data for the other post codes have changed as well.
- Derek decides to redo the aggregation by region using
- <code>ex1:dataSet2</code> and regenerate the
- graphics using the same layout.
- </p -->
- </section>
-
- <section>
- <h3>Derivation</h3>
-
- <p>
- Derek creates a new chart based on the revised data,
- using the same compilation activity as before. Betty checks the article again at a
- later point, and wants to know if it is based on the old or new GovData.
- She sees three new assertions about derivation in the provenance data, plus
- an assertion about how the new chart was generated.
- </p>
- <pre class="example turtle">
- ex1:chart2 prov:dependedOn ex1:dataSet2 .
- ex1:chart2 prov:wasEventuallyDerivedFrom ex1:dataSet2 .
- ex1:chart2 prov:wasDerivedFrom ex1:dataSet2 .
- ex1:chart2 prov:wasGeneratedBy ex1:compiled2 .
- </pre>
- <p>
- She interprets these assertions as follows. The first says that the new chart included,
- somewhere in the history of its creation, the revised data set.
- The second says further that the new chart is as it because of the revised
- data set, i.e. there is an explicit influence of the data on the chart.
- Finally, the third and fourth assertions together say further that it was
- the activity <code>ex1:compiled2</code> that derived the new chart
- from the revised data set.
- </p>
- </section>
- </section>
-
- <section>
- <h2>Frequently asked questions</h2>
- </section>
-
- <section class="appendix">
- <h2>Abstract Syntax Notation for Examples</h2>
- <p>
- Below we give translations of the working example snippets into the PROV-DM
- abstract syntax notation (ASN).
- </p>
- <section>
- <h3>Entities</h3>
- <pre class="example asn">
- entity(ex1:dataSet1).
- entity(ex1:regionList1).
- entity(ex1:aggregate1).
- entity(ex1:chart1).
- </pre>
- </section>
-
- <section>
- <h3>Activities</h3>
- <pre class="example asn">
- activity(ex1:compiled,compilation_step).
- activity(ex1:aggregated).
- activity(ex1:illustrated).
- </pre>
- <p>
- In the first assertion above, 'compilation_step' is an optional reference to the 'recipe' that describes
- what the 'compiled' activity did. The interpretation of its name,
- 'compilation_step', is left to applications (it is not further resolved within PROV-DM).
- </p>
- <p>
- In the second assertion, optional 'recipe' has been omitted.
- </p>
- <!--PM comment: here readers will be confused by the processExecutiion / activity disconnect!
- also this does not show start/end times, optional attributes. At least one example would be useful-->
- </section>
-
- <section>
- <h3>Use and Generation</h3>
- <pre class="example asn">
- used(ex1:aggregated, ex1:dataSet1).
- used(ex1:aggregated, ex1:regionList1).
- wasGeneratedBy(ex1:aggregate1, ex1:aggregated).
-
- used(ex1:illustrated, ex1:aggregate1).
- wasGeneratedBy(ex1:chart1, ex1:illustrated).
- </pre>
- </section>
-
- <section>
- <h3>Agents</h3>
- <pre class="example asn">
- entity(ex1:derek, [ type="foaf:Person", foaf:givenName = "Derek",
- foaf:mbox= "<mailto:derek@example.org>"]).
- agent(ex1:derek).
-
- wasControlledBy(ex1:aggregated, ex1:derek).
- wasControlledBy(ex1:illustrated, ex1:derek).
- </pre>
- </section>
-
- <section>
- <h3>Roles</h3>
- <p>
- Roles are not declared directly in PROV-DM, rather they are attributes of
- relations. Thus, the entire Turtle example in sec. 3.5 is rendered as follows:
- </p>
- <pre class="example asn">
- used(ex1:aggregated, ex1:dataSet1, [ prov:role = "dataToAggregate"]).
- used(ex1:aggregated, ex1:regionList1, [ prov:role = "regionsToAggregteBy"]).
- </pre>
- <p>
- In the first assertion above, note that this adds a "role" attribute to the first 'used' assertion of Ex. 3.
- Similarly in the second assertion, we have added a "role" attribute to the second 'used' assertion of Ex. 3.
- </p>
- </section>
-
- <section>
- <h3>Revision</h3>
- <pre class="example asn">
- wasRevisionOf(ex1:dataSet2, ex1:dataSet1).
- </pre>
- </section>
-
- <section>
- <h3>Complementarity</h3>
- <pre class="example asn">
- entity(ex1:dataSet, [ type="ex1:DataSet", ex1:regions ="(ex1:North, ex1:NorthWest, ex1:East)",
- dc:creator="ex1:DataGov", dc:title="Regional incidence dataset 2011" ]).
-
- wasComplementOf(dataSet1, dataSet).
- wasComplementOf(dataSet2, dataSet).
-
- entity(ex1:dataSet1, [ type="ex1:DataSet", ex1:postCodes="( 'N1', 'N2', 'NW1', 'E1', 'E2' ) ",
- ex1:totalIncidents = "141", dc:creator = " ex1:DataGov",
- dc:title = "Regional incidence dataset 2011" ]).
- </pre>
- </section>
-
- <section>
- <h3>Derivation</h3>
- <pre class="example asn">
- dependedOn(ex1:chart2, ex1:dataSet2).
- wasEventuallyDerivedFrom(ex1:chart2, ex1:dataSet2).
- wasDerivedFrom(ex1:chart2, ex1:dataSet2).
- wasGeneratedBy(ex1:chart2, ex1:compiled2).
- </pre>
- </section>
- </section>
-
- <section class="appendix">
- <h2>Acknowledgements</h2>
- <p>
- WG membership to be listed here.
- </p>
- </section>
-
- </body></html>
+<!DOCTYPE html>
+<html><head>
+ <title>Prov Model Primer</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+ <!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+ <!-- PM -->
+ <style type="text/css">
+ .note { font-size:small; margin-left:50px }
+ </style>
+
+ <script src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
+
+ <script class="remove">
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "Prov-Primer",
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ subtitle : "Initial draft for internal discussion",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ // copyrightStart: "2005"
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ // previousPublishDate: "1977-03-15",
+ // previousMaturity: "WD",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://dvcs.w3.org/hg/prov/raw-file/default/primer/Primer.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ extraCSS: ["http://dev.w3.org/2009/dap/ReSpec.js/css/respec.css", "./extra.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Yolanda Gil", url: "http://www.isi.edu/~gil/",
+ company: "Information Sciences Institute, University of Southern California, US" },
+ { name: "Simon Miles", url: "http://www.inf.kcl.ac.uk/~simonm",
+ company: "King's College London, UK" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ authors: [
+ { name: "TBD"},
+ ],
+
+ // name of the WG
+ wg: "Provenance Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2011/prov/wiki/Main_Page",
+
+ // name (with the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "public-prov-wg",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "",
+ };
+ </script>
+ </head>
+ <body>
+ <section id="abstract">
+ <p>This document aims to provide an intuitive guide to the PROV Data Model,
+ with worked examples.</p>
+
+ <p>
+ This is a document for internal discussion, which will ultimately
+ evolve in the first Public Working Draft of the Primer.</p>
+ </section>
+
+ <section>
+ <h2>Introduction</h2>
+ <p>
+ This primer document provides an accessible introduction to the PROV Data Model
+ (PROV-DM) standard for representing provenance on the Web, and its representation
+ in the PROV Ontology (PROV-O). Provenance describes
+ the origins of things, so PROV-DM data consists of assertions about the past.
+ </p>
+
+ <p>
+ This primer document aims to ease the adoption of the standard by providing:
+ </p>
+ <ul>
+ <li>An intuitive explanation of how PROV-DM models provenance.</li>
+ <li>Worked examples that can be followed to produce your own PROV-DM data.</li>
+ <li>Answers to frequently asked questions regarding how the model should be applied.</li>
+ </ul>
+
+ <p>
+ The <i>provenance</i> of digital objects represents their origins. The PROV-DM is a
+ proposed standard to represent provenance records, which contain <i>assertions</i> about the entities
+ and activities involved in producing and delivering or otherwise influencing a
+ given object. By knowing the provenance of an object, we can make determinations
+ about how to use it. Provenance records can be used for many purposes, such as
+ understanding how data was collected so it can be meaningfully used, determining
+ ownership and rights over an object, making judgments about information to
+ determine whether to trust it, verifying that the process and steps used to obtain a
+ result complies with given requirements, and reproducing how something it was generated.
+ </p>
+
+ <p>
+ As a standard for provenance, PROV-DM accommodates all those different uses
+ of provenance. Different people may have different perspectives on provenance,
+ and as a result different types of information might be captured in provenance records.
+ One perspective might focus on <i>agent-centered provenance</i>, that is, what entities
+ were involved in generating or manipulating the information in question. For example,
+ in the provenance of a picture in a news article we might capture the photographer who
+ took it, the person that edited it, and the newspaper that published it. A second perspective
+ might focus on <i>object-centered provenance</i>, by tracing the origins of portions of a
+ document to other documents. An example is having a web page that was assembled from content
+ from a news article, quotes of interviews with experts, and a chart that plots data from a
+ government agency. A third perspective one might take is on <i>process-centered provenance</i>,
+ capturing the actions and steps taken to generate the information in question. For example, a
+ chart may have been generated by invoking a service to retrieve data from a database, then
+ extracting certain statistics from the data using some statistics package, and finally
+ processing these results with a graphing tool.
+ </p>
+
+ <p>
+ Provenance records are metadata. There are other kinds of metadata that is
+ not provenance. For example, the size of an image is a metadata property of
+ that image but it is not provenance.
+ </p>
+
+ <p>
+ For general background on provenance, a
+ comprehensive overview of requirements, use cases, prior research, and proposed
+ vocabularies for provenance are available from the
+ <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov/">Final Report of the W3C Provenance Incubator Group</a>.
+ That document contains three general scenarios
+ that may help identify the provenance aspects of your planned applications and
+ help plan the design of your provenance system.
+ </p>
+ <p>
+ The next section gives an introductory overview of PROV-DM using simple examples.
+ The following section shows how the formal ontology PROV-O can be used to represent the PROV-DM assertions
+ as RDF triples. The document also contains frequently asked questions, and an appendix giving example
+ snippets of the PROV-DM Abstract Syntax Notation (ASN).
+ For a detailed description of PROV-DM, please refer to the
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">PROV Data Model and Abstract Syntax Notation document</a>.
+ For a detailed description of PROV-O, refer to the
+ <a href="http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html">PROV Ontology Model and Formal Semantics document</a>.
+ </p>
+ </section>
+
+ <section>
+ <h2>Intuitive overview of PROV-DM</h2>
+
+ <p><i>This section provides an intuitive explanation of the concepts in PROV-DM.
+ As with the rest of this document, it should be treated as a starting point for
+ understanding the model, and not normative in itself. The PROV-DM model specification
+ provides precise definitions and constraints to be used.</i></p>
+
+<p>
+The following ER diagram provides a high level overview of the <strong>structure of PROV-DM records</strong>.
+The diagram is the same that appears in the
+<a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html">PROV Data Model and Abstract Syntax Notation document</a>,
+but note that this primer document only describes some of the terms shown in the diagram.
+</p>
+
+<div style="text-align: center;">
+ <img src="overview.png" alt="PROV-DM overview"/>
+</div>
+
+ <section>
+ <h3>Entities</h3>
+
+ <p>
+ In PROV-DM, the things that one may ask the provenance of are called <i>entities</i>.
+ Examples of such entities are a web page, a chart, and a spellchecker.
+ </p>
+ <p>
+ An entity’s provenance may refer to many other entities. For example, a document D is
+ an entity whose provenance refers to other entities such as a chart inserted into D,
+ the dataset that was used to create that chart, or the author of the document.
+ </p>
+ <p>
+ Entities may be described from different perspectives that may be more or less specific. For example,
+ document D as stored in my file system, the second version of document D after someone edited it,
+ and D as an evolving document,
+ are three distinct entities for which we may describe the provenance. They
+ may all be perspectives on the same thing in the world (document D may exist only
+ in its second version and on my file system), but are <i>characterized</i> in
+ different ways by being described using different <i>attributes</i> (version, location, and
+ so on).
+ </p>
+ <p>
+ The characterization of an entity means that the provenance assertions
+ about the entity are only about the thing when it has those attributes.
+ For example, the second version of document D is characterized by being the
+ second version, and so assertions about who reviewed that entity apply only
+ to the document as it is in its second version. When the document becomes
+ the third version, a new entity exists (the third version of D) and the
+ provenance assertions about who reviewed the second version do not apply.
+ </p>
+ </section>
+
+ <section>
+ <h3>Activities</h3>
+
+ <p>
+ Activities are how entities come into
+ existence and how their attributes change to become new entities,
+ often making use of previously existing entities to achieve this.
+ For example, if the second version of document D was generated
+ by a translation from the first version of the document in another language,
+ then this translation is an activity.
+ An activity may have either already occurred or be still
+ taking place when a new entity is generated.
+ While entities are static aspects in the world (things), <i>activities</i> are
+ dynamic aspects (actions, processes, etc.)
+ </p>
+ </section>
+
+ <section>
+ <h3>Use and Generation</h3>
+
+ <p>
+ Activities <i>generate</i> new entities.
+ For example, writing a document brings the document into existence, while
+ revising the document brings a new version into existence.
+ </p>
+ <p>
+ Activities also make <i>use</i> of entities. For example, revising a document
+ to fix spelling mistakes uses the original version of the document as well
+ as a list of corrections.
+ </p>
+ <p>
+ Assertions can be made in a provenance record to state that
+ particular activities used or generated particular entities.
+ </p>
+ </section>
+
+ <section>
+ <h3>Agents</h3>
+
+ <p>
+ An agent is a type of entity that takes an active role in an activity such
+ that it can be assigned some degree of responsibility for the activity taking
+ place. An agent can be a person, a piece of software, or an inanimate object.
+ Several agents can be associated with an activity.
+ Consider a chart displaying some statistics
+ regarding crime rates over time in a linear regression. To represent the
+ provenance of a that chart, we could state that the person who created the
+ chart was an agent involved in its creation, and that the software used to
+ create the chart was also an agent involved in that activity.
+ </p>
+ <p>
+ Since agents are a kind of entity, it is therefore possible to
+ associate provenance records with the agents themselves.
+ In the running example, we
+ can also represent the provenance of the software used to create the chart, and specify the agents involved in
+ producing that software, such as the vendor.
+ </p>
+ </section>
+
+ <!--section>
+ <h3>Accounts</h3>
+
+ <p>An intuitive overview of how to think about accounts in PROV-DM.</p>
+ </section -->
+
+ <section>
+ <h3>Roles</h3>
+
+ <p>
+ A <i>role</i> is a description of the function or the part that an entity
+ played in an activity. Roles specify
+ the relationship between an entity and an activity, whether
+ how an activity used an entity or generated an entity. Roles also specify how agents are
+ involved in an activity, qualifying their participation in the activity or
+ specifying what agents controlled it.
+ For example, an agent may play the role of "editor" in an activity that uses
+ one entity in the role of "document to be edited" and another in the role of "document
+ editor", to generate a further entity in the role of "edited document".
+ Roles are application specific.
+ </p>
+ <!--p>Roles are intended as an extension point in the model; it is expected users will define and use custom role taxonomies. Role interpretation is application specific.</p -->
+ </section>
+
+ <section>
+ <h3>Revisions and Derivation</h3>
+
+ <p>
+ A given entity, such as a document, may go through multiple <i>revisions</i>
+ (also called versions and other comparable terms) over time. Between revisions,
+ one or more attributes of the entity may change.
+ The result of each revision is a new entity,
+ and PROV-DM allows one to relate those entities by making an assertion that
+ one is a revision of another.
+ </p>
+ <p>
+ When one entity's existence, content, characteristics and so on are
+ at least partly due to another entity, then we say that the former is
+ <i>derived</i> from the latter. For example, one document may contain
+ material copied from another,
+ and a chart is derived from the data that is used to create it.
+ </p>
+ <!-- p>
+ <p>
+ There are different kinds of derivation expressible in PROV-DM.
+ Consider the case of the page in the browser above. It is derived from
+ the designer's sketch in the strictest sense, i.e. if the sketch had
+ been different so would the page. On the other hand, there are
+ entities that are part of the page's history but which did not inform
+ the content of that page, i.e. the page would have been the same even
+ if the earlier entity changed. For example, on creating the original
+ draft of the page, the designer may have included a banner image
+ saying "DRAFT - FOR REVIEW ONLY". This banner was not part of the
+ sketch, nor part of the published page downloaded to the browser, but
+ was part of the page's history, and while not affecting the browsed
+ page's content may have been a factor in its existence. Finally, in
+ some cases, we may be able to say not only that one entity was derived
+ from another, but also how it was derived, i.e. by what activity.
+ For example, the page in the browser is derived from the
+ page on the web server because a download activity sent the bytes of
+ the latter across an HTTP connection to the browser client.
+ </p>
+ </p -->
+ <p>
+ There are different kinds of derivation expressible in PROV-DM. For
+ example, the data may be normalized before creating the chart.
+ In PROV-DM terms, we say that the chart <i>was eventually
+ derived from</i> the original data, <i>depended on</i> the settings
+ of the graphing software, and <i>was derived
+ from</i> the normalized data.
+ </p>
+ </section>
+
+ <!-- p>
+ <section>
+ <h3>Complementarity</h3>
+ <p>
+ As described above, entities can be described from different perspectives,
+ by being characterized by different attributes. For example, "document D",
+ "the second version of document D" and "document D as stored on my filesystem"
+ are different entities
+ because they are characterized in different ways. However, for some period of time
+ they may all refer to the same thing in the world, e.g. for a while the copy of
+ D on my filesystem <i>was</i> the second version.
+ </p>
+ <p>
+ In PROV-DM, we say there is <i>complementarity</i> between one entity and another
+ if, in some period of time, they have the same or compatible characterization.
+ So, both "the second version of document D" and "document D as stored on my filesystem"
+ are complements of "document D", because they are both characterized by being
+ document D, but with specific additional attributes.
+ If, at some point in time, a version of D stored on my filesystem is the second one, then
+ "document D as stored on my filesystem" and "the second version of document D" are
+ complements of each other.
+ </p>
+ Several asserted entities could be characterizing the same thing, in
+ particular when entities are asserted by different <em>accounts</em> or over
+ different time periods. If two such entities have <em>overlapping
+ lifespans</em>, and the first entity have some <em>attributes</em> that
+ have not been asserted (and not necessarily always true) for the second entity,
+ then the first entity is said to be <em>complementing</em> the second
+ entity, that is the first entity helps form a more detailed
+ description of the second entity, at least for the duration of the
+ overlapping lifespan.
+ </p>
+ <p>
+ In addition, if <code>:A prov:wasComplementOf :B</code>, then of all the
+ attributes of the entity <code>:A</code> which can be <em>mapped</em> to
+ <em>compatible</em> attributes of <code>:B</code> MUST be <em>matching</em>
+ for the continuous duration of the overlap of <code>:A</code> and
+ <code>:B</code>'s lifespans.
+ It is out of scope for PROV to specify or assert the nature of
+ the <em>compatibility mapping</em> and <em>matching</em>, the exact
+ interpretation of these is left to the asserter of
+ <code>wasComplementOf</code>
+ </p>
+ <p>
+ If <code>:B</code> also have some attributes which
+ are not asserted (or not always true) about <code>:A</code>,
+ then this MAY be asserted using the
+ inverse relation <code>:B prov:wasComplementOf :A</code>. If two entities
+ both complement each other in this manner, both MUST have some
+ attributes the other does not have, although those attributes MAY
+ not have been asserted in the provenance. Note that the
+ <em>lack</em> of such an inverse assertion does not neccessarily
+ mean that <code>:B</code> did not have any additional attributes
+ for <code>:A</code> in the timespan, only that this has not
+ been asserted.
+ </p>
+ <p>
+ In the simplest case, both entites are described using the same
+ attributes, in which case <em>matching</em> means the values SHOULD
+ literally be the same (matching by identity). On the other hand an
+ attribute like <code>ex1:speed_in_mph</code> can be <em>mapped</em> to
+ a compatible <code>ex2:speed_in_kmh</code> attribute. Not all
+ attributes might be mappable in both directions, for instance
+ <code>ex1:city</code> to <code>ex2:country</code>, but not vice
+ versa.
+ </p>
+ <p>
+ Note that it is out of scope for PROV to assert or explain any
+ mapping of compatible attributes. This is merely a conclusion
+ that can be drawn from the assertion that the two entities both
+ described the same thing in the overlapping time spans. Also note
+ that asserting a complementary relationship does not detail how the
+ two entity timespans overlap, this could be anything from
+ complete one-to-one match (where all attributes are always true for
+ both entities) to merely touching overlaps.
+ </section>
+ </p -->
+
+
+ </section>
+
+ <section>
+ <h2>Examples of Use of the PROV-O Ontology</h2>
+
+ <p>In the following sections, we show how PROV-DM can be used to model
+ provenance in specific examples.</p>
+
+ <p>We include examples of how the formal ontology PROV-O
+ can be used to represent the PROV-DM assertions as RDF triples.
+ These are shown using the Turtle notation. In
+ the latter depictions, the namespace prefix <b>prov</b> denotes
+ terms from the Prov ontology, while <b>ex1</b>, <b>ex2</b>, etc.
+ denote terms specific to the example.</p>
+
+ <p>We also provide a representation of the examples in the Abstract
+ Syntax Model ASM used in the conceptual model document. The full ASM data
+ for the examples in this section is
+ included in the appendix.</p>
+
+ <section>
+ <h3>Entities</h3>
+
+ <p>
+ An online newspaper publishes an article with a chart about crime statistics making using of data (GovData) provided through a government portal.
+ The article includes a chart based on the data, with data values aggregated by
+ geographical regions.
+ </p>
+ <p>
+ A blogger, Betty, looking at the article, spots what she thinks to be an error in the chart.
+ Betty retrieves the provenance record of the article, how it was created.
+ </p>
+ <p>Betty would find the following assertions about entities in the provenance record:</p>
+ <pre class="turtle example">
+ ex1:newspaper1 a prov:Entity .
+ ex1:article1 a prov:Entity .
+ ex1:regionList1 a prov:Entity .
+ ex1:aggregate1 a prov:Entity .
+ ex1:chart1 a prov:Entity .
+ </pre>
+ <p>
+ These statements, in order, assert that there is a newspaper (<code>ex1:newspaper1</code>) and an article (<code>ex1:article1</code>),
+ that the original data set is an entity (<code>ex1:dataSet1</code>),
+ there is a list of regions
+ (<code>ex1:regionList1</code>) that is an entity, that the data aggregated by region is an entity (<code>ex1:aggregate1</code>),
+ and that the chart (<code>ex1:chart1</code>) is an entity.
+ </p>
+
+ </section>
+
+ <section>
+ <h3>Activities</h3>
+
+ <p>
+ Further, the provenance record asserts that there was
+ an activity (<code>ex1:compiled</code>) denoting the compilation of the
+ chart from the data set.
+ </p>
+ <pre class="turtle example">
+ ex1:compiled a prov:Activity .
+ </pre>
+ <p>
+ The provenance record also includes reference to the more specific steps involved in this compilation,
+ which are first aggregating the data by region and then generating the chart graphic.
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated a prov:Activity .
+ ex1:plotted a prov:Activity .
+ </pre>
+ </section>
+
+ <section>
+ <h3>Use and Generation</h3>
+
+ <p>
+ Finally, the provenance record asserts the key relations among the above
+ entities and activities, i.e. the use of an entity by an activity,
+ or the generation of an entity by an activity.
+ </p>
+ <p>
+ For example, the assertions below state that the aggregation activity
+ (<code>ex1:aggregated</code>) used the original data set, that it used the list of
+ regions, and that the aggregated data was generated by this activity.
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated prov:used ex1:dataSet1 ;
+ prov:used ex1:regionList1 .
+ ex1:aggregate1 prov:wasGeneratedBy ex1:aggregated .
+ </pre>
+ <p>
+ Similarly, the chart graphic creation activity (<code>ex1:illustrated</code>)
+ used the aggregated data, and the chart was generated by this activity.
+ </p>
+ <pre class="turtle example">
+ ex1:illustrated prov:used ex1:aggregate1 .
+ ex1:chart1 prov:wasGeneratedBy ex1:illustrated .
+ </pre>
+
+ <!--p>
+ For example, the provenance declares the event (of type <code>prov:Usage</code>)
+ where the aggregation activity used the GovData data set, and the event
+ (of type <code>prov:Generation</code>) where the same activity generated
+ the data aggregated by region.
+ </p>
+ <pre class="turtle example">
+ ex1:dataSet1Usage a prov:Usage .
+ ex1:aggregate1Generation a prov:Generation .
+ </pre>
+ <p>
+ To describe these events, the provenance says within which activity
+ they occur and what entity is used or generated.
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated prov:qualifiedUsage ex1:dataSet1Usage .
+ ex1:aggregated prov:qualifiedGeneration ex1:aggregate1Generation .
+ ex1:dataSet1Usage prov:entity ex1:dataSet1 .
+ ex1:aggregate1Generation prov:entity ex1:aggregate1 .
+ </pre>
+ <p>
+ Comparable events are described for the activity of generating the chart image
+ from the aggregated data.
+ </p>
+ <pre class="turtle example">
+ ex1:aggregate1Usage a prov:Usage .
+ ex1:chart1Generation a prov:Generation .
+ ex1:illustrated prov:qualifiedUsage ex1:aggregate1Usage .
+ ex1:illustrated prov:qualifiedGeneration ex1:chart1Generation .
+ ex1:aggregate1Usage prov:entity ex1:aggregate1 .
+ ex1:chart1Generation prov:entity ex1:chart1 .
+ </pre>
+ <p>
+ From this information Betty can see that
+ the mistake could have been in the original data set or else was introduced
+ in the compilation activity, and sets out to discover which.
+ </p>
+ </p -->
+
+ </section>
+
+ <section>
+ <h3>Agents</h3>
+
+ <p>
+ Digging deeper, Betty wants to know who compiled the chart.
+ Betty sees that Derek was involved in both the aggregation and
+ chart creation activities:
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated prov:wasAssociatedWith ex1:derek .
+ ex1:illustrated prov:wasAssociatedWith ex1:derek .
+ </pre>
+ <p>
+ The record for Derek provides the
+ following information, of which the first line is a PROV-O statement that
+ Derek is an agent, followed by statements about general properties of Derek.
+ </p>
+ <pre class="turtle example">
+ ex1:derek a prov:Agent ;
+ a foaf:Person ;
+ foaf:givenName "Derek"^^xsd:string ;
+ foaf:mbox <mailto:dererk@example.org> .
+ </pre>
+ </section>
+
+ <!-- section>
+ <h3>Accounts</h3>
+
+ <p><i>Suggested example:</i> The analyst provides his own record of how he compiled GovData to create
+ the chart, which provides more detail than in the newspaper's provenance data.
+ Specifically, the analysts account separates compilation into two stages: aggregating
+ data by region and then producing the chart. Therefore, there are two separate
+ accounts of the same events.</p>
+ </section -->
+
+ <section>
+ <h3>Roles</h3>
+
+ <p>
+ For Betty to understand where the error lies, she needs to have more detailed
+ information on how entities have been used in, participated in, and generated
+ by activities. Betty has determined that <code>ex1:aggregated</code> used
+ entities <code>ex1:regionList1</code> and <code>ex1:dataSet1</code>, but she does not
+ know what function these entities played in the processing. Betty
+ also knows that <code>ex1:derek</code> controlled the activities, but she does
+ not know if Derek was the analyst responsible for determining how the data
+ should be aggregated.
+ </p>
+ <p>
+ The above information is described as roles in the provenance records. The aggregation
+ activity involved entities in four roles: the data to be aggregated (<code>ex1:dataToAggregate</code>),
+ the regions to aggregate by (<code>ex1:regionsToAggregateBy</code>), the
+ resulting aggregated data (<code>ex1:aggregatedData</code>), and the
+ analyst doing the aggregation (<code>ex1:analyst</code>).
+ </p>
+ <pre class="turtle example">
+ ex1:dataToAggregate a prov:Role .
+ ex1:regionsToAggregateBy a prov:Role .
+ ex1:aggregatedData a prov:Role .
+ ex1:analyst a prov:Role .
+ </pre>
+ <p>
+ In addition to the simple facts that the aggregation activity used, generated or
+ was controlled by entities/agents as described in the sections above, the
+ provenance record contains more details of <i>how</i> these entities and agents
+ were involved, i.e. the roles they played. For example, the assertions below state
+ that the aggregation activity (<code>ex1:aggregated</code>) included the usage
+ of the government data set (<code>ex1:dataSet1</code>) in the role of the data
+ to be aggregated (<code>ex1:dataToAggregate</code>).
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated prov:hadQualifiedUsage [ a prov:Usage ;
+ prov:hadQualifiedEntity ex1:dataSet1 ;
+ prov:hadRole ex1:dataToAggregate ] .
+ </pre>
+ <p>
+ This can then be distinguished from the same activity's usage of the list of
+ regions because the roles played are different.
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated prov:hadQualifiedUsage [ a prov:Usage ;
+ prov:hadQualifiedEntity ex1:regionList1 ;
+ prov:hadRole ex1:regionsToAggregateBy ] .
+ </pre>
+ <p>
+ Similarly, the provenance includes assertions that the same activity was
+ controlled in a particular way (<code>ex1:analyst</code>) by Derek, and that
+ the entity <code>ex1:aggregate1</code> took the role of the aggregated
+ data in what the activity generated.
+ </p>
+ <pre class="turtle example">
+ ex1:aggregated
+ prov:hadQualifiedControl [ a prov:Control ;
+ prov:hadQualifiedEntity ex1:derek ;
+ prov:hadRole ex1:analyst
+ ] ;
+ prov:hadQualifiedGeneration [ a prov:Generation ;
+ prov:hadQualifiedEntity ex1:aggregate1 ;
+ prov:hadRole ex1:aggregatedData
+ ] .
+ </pre>
+ </section>
+
+ <section>
+ <h3>Revision</h3>
+
+ <p>
+ After looking at the detail of the compilation activity, there appears
+ to be nothing wrong, so Betty concludes the error is in the government dataset.
+ She looks at the characterization of the dataset <code>ex1:dataSet1</code>,
+ and sees that it is missing data from one of the zipcodes in the area. She contacts
+ the government, and a new version of GovData is created, declared to be the
+ next revision of the data by Edith. The provenance record of this new dataset,
+ <code>ex1:dataSet2</code>, states that it is a revision of the
+ old data set, <code>ex1:dataSet1</code>.
+ </p>
+ <pre class="turtle example">
+ ex1:dataSet2 prov:wasRevisionOf ex1:dataSet1 .
+ </pre>
+ </section>
+
+ <!-- section>
+ <h3>Complementarity</h3>
+
+ <p>Betty lets Derek know that a new revision of the data set exists,
+ and he looks at the provenance of the new data to understand what he needs to
+ re-analyze. </p>
+ <p>In addition to specifying that
+ <code>ex1:dataSet2</code> is a new revision of
+ <code>ex1:dataSet1</code>, the provenance from DataGov also
+ asserts that both of these entities were a <em>complement of</em>
+ another entity <code>ex1:dataSet</code>.
+ </p>
+ <pre class="turtle example">
+ ex1:dataSet1 prov:wasComplementOf ex1:dataSet .
+ ex1:dataSet2 prov:wasComplementOf ex1:dataSet .
+ </pre>
+ <!--
+ <pre class="asn example">
+ wasComplementOf(ex1:dataSet1, ex1:dataSet)
+ wasComplementOf(ex1:dataSet2, ex1:dataSet)
+ </pre>
+ -->
+ <p>
+ This assertion means that <code>ex1:dataSet1</code> at some point shared
+ its characterizing attributes with <code>ex1:dataSet</code>, and the same for
+ <code>ex2:dataSet2</code>. Thus the <em>entity</em>
+ <code>ex1:dataSet1</code> did at some point represent the same
+ thing as characterized by the entity <code>ex1:dataSet</code>. The same is
+ true for <code>ex1:dataSet2</code>, though not necessarily at the
+ same point in time.
+ </p>
+ <!-- p>
+ The term <em>was complement of</em> here means that the
+ <code>ex1:dataSet1</code>
+ provide additional details that adds to the details of
+ <code>ex1:dataSet</code> (complementing it), and that both of these
+ entities represented the same thing.
+ Characterizing attributes of <code>ex1:dataSet</code> are from this
+ asserted to have been <em>compatible</em> with the properties of
+ <code>ex1:dataSet1</code> and <code>ex1:dataSet2</code>.
+ <em>Compatible</em> here means that some kind of mapping can be
+ established between the attributes, they don't neccessarily have to
+ match directly.
+ </p -->
+ <p>
+ Derek then looks at the characterization of the generalized data set
+ (<code>ex1:dataSet</code>) to find the attributes shared with the first
+ and second versions of the data set. The assertions below give the generalized
+ data set's attributes: it is of type <code>ex1:DataSet</code>, it covers
+ three named regions, it was created by <code>ex1:DataGov</code>, and
+ has a given title.
+ </p>
+ <pre class="example turtle">
+ ex1:dataSet a ex1:DataSet ;
+ ex1:regions ( ex1:North, ex1:NorthWest, ex1:East ) ;
+ dc:creator ex1:DataGov ;
+ dc:title "Regional incidence dataset 2011" .
+ </pre>
+ <p>
+ As <code>ex1:dataSet1</code> and <code>ex1:dataSet2</code> complement
+ <code>ex1:dataSet</code>,
+ Derek can deduce from the above attributes that both the former had
+ these same attributes at some point, i.e.
+ the creator <code>ex1:DataGov</code> and so on. Derek compares the above
+ assertions to the
+ attributes of <code>ex1:dataSet1</code>.
+ </p>
+ <pre class="example turtle">
+ ex1:dataSet1 a ex1:DataSet ;
+ ex1:postCodes ( "N1", "N2", "NW1", "E1", "E2" ) ;
+ ex1:totalIncidents 141 ;
+ dc:creator ex1:DataGov ;
+ dc:title "Regional incidence dataset 2011" .
+ </pre>
+ <p>
+ Shared characterizing attributes are not necessarily represented in
+ the serialized assertions of different entities. For example, the creator
+ and title are exactly the same for <code>ex1:dataSet</code> and <code>ex1:dataSet1</code>,
+ but the regions covered by the data set are described in a different way:
+ "regions" for <code>ex1:dataSet</code> and "postCodes" for <code>ex1:dataSet1</code>.
+ Whether these are equivalent is a domain-specific judgment.
+ We can also see that, while <code>ex1:dataSet1</code> complements <code>ex1:dataSet</code>,
+ the inverse is not true. <code>ex1:dataSet1</code> is more specific, because
+ it has a "totalIncidents" attribute specific to that version of the data set.
+ </p>
+ <!-- p>
+ Derek sees that the creator and title are directly mappable and
+ equal between these entities. He also knows (from his region
+ aggregation method) that the <code>ex1:postCodes</code> <code>N1</code> and
+ <code>N2</code> are in the
+ region <code>ex1:North</code>, and so on, and can confirm that although
+ this regional characterisation of the data is not expressed
+ using the same attributes in the two entities, they are <em>compatible</em>.
+ </p>
+ <p>Derek notes that <code>ex1:totalIncidents</code> is not stated
+ for <code>ex1:dataSet</code>, and not mappable to any of the
+ other existing attributes. Thus this could be one of the
+ complementing attributes that makes <code>ex1:dataSet1</code>
+ more specific than <code>ex1:dataSet</code>.
+
+ Derek can from the assertion <code>ex1:dataSet1
+ prov:wasComplementOf ex1:dataSet</code>
+ see that <code>ex1:dataSet</code>
+ did have 141 incidents when its characterization interval
+ overlapped that of <code>ex1:dataSet1</code>, but not neccessarily
+ throughout its lifetime. Note that in this example the provenance
+ assertions are not providing any direct description of the
+ characterization interval of the entities.
+ </p>
+ <p>
+ Due to the open world assumption (more
+ information might be added later) he can not conclude
+ from this alone that <code>ex1:dataSet</code> at any point did
+ <strong>not</strong> have 141 incidents. He therefore does not know
+ for sure that <code>ex1:totalIncidents</code> is a complementing
+ attribute which <code>ex1:dataSet</code> does not have in its
+ characterisation.
+ </p>
+ <p>
+ Derek finally compares the newer revision
+ <code>ex1:dataSet2</code> with
+ <code>ex1:dataSet</code>:
+ </p>
+ <pre class="example turtle">
+ ex1:dataSet2 a ex1:DataSet ;
+ ex1:postCodes ( "N1", "N2", "NW1", "NW2", "E1", "E2" ) ;
+ ex1:totalIncidents 158 ;
+ dc:creator ex1:DataGov ;
+ dc:title "Regional incidence dataset 2011" .
+ </pre>
+ <p>
+ In this revision, the new postcode <kbd>NW2</kbd> appears, this is still
+ <em>compatible</em> with the region <code>ex1:NorthWest</code>
+ of <code>ex1:dataSet</code>
+ On the other hand, the attribute <code>prov:totalIncidents</code> have gone up to 158.
+ </p>
+ <p>
+ From the <code>prov:wasComplementOf</code> assertion Derek knows that
+ <code>ex1:dataSet2</code> also provides additional attributes for
+ <code>ex1:dataSet</code>, but because the total incidents can't
+ both be 141 and 158, the attribute <code>ex1:totalIncidents</code>
+ is a complementing attribute, and changes over the
+ characterisation interval (lifespan) of <code>ex1:dataSet</code>,
+ and is thus not one of its characterising attributes. He also now
+ knows that <code>ex1:dataSet</code> is a common characterisation
+ of the dataset that spans (parts of) both revisions. It has
+ however not been asserted explicitly that the
+ <code>ex1:dataSet</code> is a somewhat more general
+ characterisation, just that it allows mutability on the
+ <code>prov:totalIncidents</code> attribute and overlapped (parts
+ of) the timespans of the two revisions.
+ </p>
+ <p>
+ From this Derek concludes that he can still use the regions North,
+ North West and East in the diagram layout, but as the
+ <code>ex1:totalIncidents</code> differ, something in the
+ raw data has changed. He can't from this provenance assertion
+ alone tell if that is merely from the addition of the post code
+ NW2, or if data for the other post codes have changed as well.
+ Derek decides to redo the aggregation by region using
+ <code>ex1:dataSet2</code> and regenerate the
+ chart using the same layout.
+ </p -->
+ </section -->
+
+ <section>
+ <h3>Derivation</h3>
+
+ <p>
+ Derek notices that there is a new dataset available and creates a new chart based on the revised data,
+ using the same compilation activity as before. Betty checks the article again at a
+ later point, and wants to know if it is based on the old or new GovData.
+ She sees three new assertions about derivation in the provenance data, plus
+ an assertion about how the new chart was generated.
+ </p>
+ <pre class="example turtle">
+ ex1:chart2 prov:dependedOn ex1:dataSet2 .
+ ex1:chart2 prov:wasEventuallyDerivedFrom ex1:dataSet2 .
+ ex1:chart2 prov:wasDerivedFrom ex1:dataSet2 .
+ ex1:chart2 prov:wasGeneratedBy ex1:compiled2 .
+ </pre>
+ <p>
+ She interprets these assertions as follows. The first says that the new chart included,
+ somewhere in the history of its creation, the revised data set.
+ The second says further that the new chart is as it because of the revised
+ data set, i.e. there is an explicit influence of the data on the chart.
+ Finally, the third and fourth assertions together say further that it was
+ the activity <code>ex1:compiled2</code> that derived the new chart
+ from the revised data set.
+ </p>
+ </section>
+ </section>
+
+ <section>
+ <h2>Frequently asked questions</h2>
+ </section>
+
+ <section class="appendix">
+ <h2>Abstract Syntax Notation for Examples</h2>
+ <p>
+ Below we give translations of the working example snippets into the PROV-DM
+ abstract syntax notation (ASN).
+ </p>
+ <section>
+ <h3>Entities</h3>
+ <pre class="example asn">
+ entity(ex1:dataSet1).
+ entity(ex1:regionList1).
+ entity(ex1:aggregate1).
+ entity(ex1:chart1).
+ </pre>
+ </section>
+
+ <section>
+ <h3>Activities</h3>
+ <pre class="example asn">
+ activity(ex1:compiled).
+ activity(ex1:aggregated).
+ activity(ex1:illustrated).
+ </pre>
+ <!--
+ <p>
+ In the first assertion above, 'compilation_step' is an optional reference to the 'recipe' that describes
+ what the 'compiled' activity did. The interpretation of its name,
+ 'compilation_step', is left to applications (it is not further resolved within PROV-DM).
+ </p>
+ <p>
+ In the second assertion, optional 'recipe' has been omitted.
+ </p>
+ -->
+ <!--PM comment: here readers will be confused by the processExecutiion / activity disconnect!
+ also this does not show start/end times, optional attributes. At least one example would be useful-->
+ </section>
+
+ <section>
+ <h3>Use and Generation</h3>
+ <pre class="example asn">
+ used(ex1:aggregated, ex1:dataSet1).
+ used(ex1:aggregated, ex1:regionList1).
+ wasGeneratedBy(ex1:aggregate1, ex1:aggregated).
+
+ used(ex1:illustrated, ex1:aggregate1).
+ wasGeneratedBy(ex1:chart1, ex1:illustrated).
+ </pre>
+ </section>
+
+ <section>
+ <h3>Agents</h3>
+ <pre class="example asn">
+ entity(ex1:derek, [ type="foaf:Person", foaf:givenName = "Derek",
+ foaf:mbox= "<mailto:derek@example.org>"]).
+ agent(ex1:derek).
+
+ wasControlledBy(ex1:aggregated, ex1:derek).
+ wasControlledBy(ex1:illustrated, ex1:derek).
+ </pre>
+ </section>
+
+ <section>
+ <h3>Roles</h3>
+ <p>
+ Roles are not declared directly in PROV-DM, rather they are attributes of
+ relations. Thus, the entire Turtle example in sec. 3.5 is rendered as follows:
+ </p>
+ <pre class="example asn">
+ used(ex1:aggregated, ex1:dataSet1, [ prov:role = "dataToAggregate"]).
+ used(ex1:aggregated, ex1:regionList1, [ prov:role = "regionsToAggregteBy"]).
+ </pre>
+ <p>
+ In the first assertion above, note that this adds a "role" attribute to the first 'used' assertion of Ex. 3.
+ Similarly in the second assertion, we have added a "role" attribute to the second 'used' assertion of Ex. 3.
+ </p>
+ </section>
+
+ <section>
+ <h3>Revision</h3>
+ <pre class="example asn">
+ wasRevisionOf(ex1:dataSet2, ex1:dataSet1).
+ </pre>
+ </section>
+
+ <!--
+ <section>
+ <h3>Complementarity</h3>
+ <pre class="example asn">
+ entity(ex1:dataSet, [ type="ex1:DataSet", ex1:regions ="(ex1:North, ex1:NorthWest, ex1:East)",
+ dc:creator="ex1:DataGov", dc:title="Regional incidence dataset 2011" ]).
+
+ wasComplementOf(dataSet1, dataSet).
+ wasComplementOf(dataSet2, dataSet).
+
+ entity(ex1:dataSet1, [ type="ex1:DataSet", ex1:postCodes="( 'N1', 'N2', 'NW1', 'E1', 'E2' ) ",
+ ex1:totalIncidents = "141", dc:creator = " ex1:DataGov",
+ dc:title = "Regional incidence dataset 2011" ]).
+ </pre>
+ </section>
+ -->
+
+ <section>
+ <h3>Derivation</h3>
+ <pre class="example asn">
+ dependedOn(ex1:chart2, ex1:dataSet2).
+ wasEventuallyDerivedFrom(ex1:chart2, ex1:dataSet2).
+ wasDerivedFrom(ex1:chart2, ex1:dataSet2).
+ wasGeneratedBy(ex1:chart2, ex1:compiled2).
+ </pre>
+ </section>
+ </section>
+
+ <section class="appendix">
+ <h2>Acknowledgements</h2>
+ <p>
+ WG membership to be listed here.
+ </p>
+ </section>
+
+ </body></html>
Binary file primer/overview.png has changed