--- a/ontology/ProvenanceFormalModel.html Wed Jan 18 21:19:44 2012 -0500
+++ b/ontology/ProvenanceFormalModel.html Wed Jan 18 22:10:33 2012 -0500
@@ -638,7 +638,7 @@
<p>The wasGeneratedBy property links the Entity class with the Activity class.</p>
<p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
<img src="diagrams/wasGeneratedBy.png"
- style="height: 3em" alt="wasGeneratedBy links Entity to Activity" />
+ style="height: 5em" alt="wasGeneratedBy links Entity to Activity" />
<div class="anexample">
<div><b>Example</b></div>
<p>Example of wasGeneratedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy act0</i>. The RDF/XML syntax for asserting this information is given below.
@@ -686,7 +686,7 @@
<h4>wasDerivedFrom</h4>
<p>The wasDerivedFrom property links two instances of Entity class, where "some characterized entity is transformed from, created from, or affected by another characterized entity." [[PROV-DM]]</p>
<img src="diagrams/wasDerivedFrom.png"
- style="height: 3em" alt="wasDerivedFrom links Entity to Entity" />
+ style="height: 5em" alt="wasDerivedFrom links Entity to Entity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasDerivedFrom property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
@@ -708,7 +708,7 @@
<p>This object property is used to link two instances of Entity class that "...are not directly used and generated respectively" by a single instance of Activity class [[PROV-DM]].
</p>
<img src="diagrams/wasEventuallyDerivedFrom.png"
- style="height: 3em" alt="wasEventuallyDerivedFrom links Entity to Entity" />
+ style="height: 5em" alt="wasEventuallyDerivedFrom links Entity to Entity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasEventuallyDerivedFrom property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e5 wasEventuallyDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
@@ -727,7 +727,7 @@
<h4>dependedOn</h4>
<p>The dependedOn property links two instances of Entity class to model the derivation of one instance from another instance. This is a <i>transitive</i> property, in other words if an Entity instance a1 dependedOn a2 and a2 dependedOn a3, then a1 dependedOn a3 is also true.</p>
<img src="diagrams/dependedOn.png"
- style="height: 3em" alt="dependedOn links Entity to Entity"/>
+ style="height: 5em" alt="dependedOn links Entity to Entity"/>
<div class="anexample">
<div><b>Example</b></div>
<p>Example of dependedOn property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e5 dependedOn e2</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -752,7 +752,7 @@
<p>The used property links the Activity class to the Entity class, where the Entity instance is "consumed" by a Activity instance.</p>
<p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
<img src="diagrams/used.png"
- style="height: 3em" alt="used links Activity to Entity" />
+ style="height: 5em" alt="used links Activity to Entity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of used property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -767,19 +767,19 @@
</section>
- <section id="hadparticipant">
- <h4>hadParticipant</h4>
- <p>The hadPariticipant property links Entity class to Activity class, where Entity used or wasGeneratedBy Activity.</p>
- <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
- <img src="diagrams/hadParticipant.png"
- style="height: 3em" alt="hadParticipant links Activity to Entity" />
+ <section id="wasAssociatedWith">
+ <h4>wasAssociatedWith</h4>
+ <p>Agents are a particular entity that can be associated to activities, meaning that they can be assigned some degree of responsibility for an activity taking place. The wasAssociatedWith property links an Activity to an Agent responsible for the Activity in one way or another.</p>
+ <p><i>Note: No arity constraints are assumed between Activity and Agent</i></p>
+ <img src="diagrams/wasAssociatedWith.png"
+ style="height: 5em" alt="wasAssociatedWith links Activity to Entity" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of hadParticipant property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 hadParticipant e2</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of wasAssociatedWith property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 wasAssociatedWith e2</i>. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
- <prov:hadParticipant rdf:resource="http://www.example.com/crimeFile#e2"/>
+ <prov:wasAssociatedWith rdf:resource="http://www.example.com/crimeFile#e2"/>
</rdf:Description>
</pre>
</div>
@@ -795,14 +795,14 @@
<h4>alternateOf</h4>
<p>The alternateOf property is used to associate an instance of the class Entity to another instance of the same class, specifying that the two instances provide characterizations of the same entity. [[PROV-DM]]</p>
<img src="diagrams/alternateOf.png"
- style="height: 3em" alt="alternateOf links Entity to Entity" />
+ style="height: 5em" alt="alternateOf links Entity to Entity" />
</section>
<section id="specializationOf">
<h4>specializationOf</h4>
<p>The specialization property is used to associate an instance of the class Entity to another instance of the same class, specifying that the former is a more specific characterization of a given entity than the second. [[PROV-DM]]</p>
<img src="diagrams/specializationOf.png"
- style="height: 3em" alt="specializationOf links Entity to Entity" />
+ style="height: 20em" alt="specializationOf links Entity to Entity" />
</div>
</section>
@@ -812,7 +812,7 @@
<h4>wasAssociatedWith</h4>
<p>The wasAssociatedWith property links Agent class to Activity class, where association represents the involvement of the Agent in modifying the characteristics of the instance of the Activity class"[[PROV-DM]].</p>
<img src="diagrams/wasControlledBy.png"
- style="height: 3em" alt="wasControlledBy links Activity to Agent" />
+ style="height: 5em" alt="wasControlledBy links Activity to Agent" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasAssociatedWith property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>Bob wasAssociatedWith FileAppending</i> (Activity). The RDF/XML syntax for asserting this is given below.
@@ -907,7 +907,7 @@
<p> This object property links two instances of the Activity classes. It is used to express the information that a given process execution used an entity that was generated by another process execution.
</p>
<img src="diagrams/wasInformedBy.png"
- style="height: 3em" alt="wasInformedBy links Activity to Activity" />
+ style="height: 5em" alt="wasInformedBy links Activity to Activity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasInformedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasInformedBy act3</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -929,7 +929,7 @@
This property links two instances of Activity class to specify the order of their executions. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
</p>
<img src="diagrams/wasScheduledAfter.png"
- style="height: 3em" alt="wasScheduledAfter links Activity to Activity" />
+ style="height: 5em" alt="wasScheduledAfter links Activity to Activity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasScheduledAfter property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasScheduledAfter act3</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -951,7 +951,7 @@
<p> This object property links an instance of <code>Activity</code> or <code>Entity</code> with an <code>time:TemporalEntity</code> from [[!OWL-TIME]], thereby allowing association of time value with instances of the two classes and their subclasses.
</p>
<img src="diagrams/hadTemporalValue.png"
- style="height: 3em" alt="hadTemporalValue links Activity or Entity to time:TemporalValue" />
+ style="height: 10em" alt="hadTemporalValue links Activity or Entity to time:TemporalValue" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadTemporalValue property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> is <i>t+3</i> time value is associated with the act3 Activity instanc</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -969,7 +969,7 @@
<h4>startedAt</h4>
<p> This object property defines the time when <code>Activity</code> started. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
</p>
- <img src="diagrams/startedAt.png" style="height: 3em" alt="startedAt links Activity to Instant"/>
+ <img src="diagrams/startedAt.png" style="height: 5em" alt="startedAt links Activity to Instant"/>
<div class="anexample">
<div><b>Example</b></div>
<p> Example of startedAt property is that a act1 (instance of Activity class) is "2011-10-20T17:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
@@ -990,7 +990,7 @@
<h4>endedAt</h4>
<p> This object property defines the time when a <code>Activity</code> ended. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
</p>
- <img src="diagrams/endedAt.png" style="height: 3em" alt="endedAt links Activity to Instant"/>
+ <img src="diagrams/endedAt.png" style="height: 5em" alt="endedAt links Activity to Instant"/>
<div class="anexample">
<div><b>Example</b></div>
<p> Example of endedAt property is that a act1 (instance of Activity class) is "2011-10-20T20:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
@@ -1010,7 +1010,7 @@
<h4>wasGeneratedAt</h4>
<p> This object property defines the time when a <code>Entity</code> was generated by Activity.
</p>
- <img src="diagrams/wasGeneratedAt.png" style="height: 3em" alt="wasGeneratedAt links Entity to Instant"/>
+ <img src="diagrams/wasGeneratedAt.png" style="height: 5em" alt="wasGeneratedAt links Entity to Instant"/>
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasGeneratedAt property is that a e1 (instance of Entity class) wasGeneratedAt "2011-10-20T20:12:12Z". The RDF/XML syntax for asserting this is given below.</p>
@@ -1032,7 +1032,7 @@
<h4>wasAttributedTo</h4>
<p>The wasAttributedTo property links an instance of the Entity class to an instance of Agent class.</p>
<img src="diagrams/wasAttributedTo.png"
- style="height: 3em" alt="wasAttributedTo links Entity to Agent" />
+ style="height: 5em" alt="wasAttributedTo links Entity to Agent" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasAttributedTo property as an addition to the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is the attribution of e3 to David for writting editing the file (<i>e3 wasAttributedTo David</i>). The RDF/XML syntax for asserting this is given below.</p>
@@ -1050,7 +1050,7 @@
<h4>wasQuoteOf</h4>
<p>The wasQuoteOf property links an instance of the Entity class to an instance of the Agent class.</p>
<img src="diagrams/wasQuoteOf.png"
- style="height: 3em" alt="wasQuoteOf links Entity to Agent" />
+ style="height: 5em" alt="wasQuoteOf links Entity to Agent" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasQuoteOf property as an addition to the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is e2 quoting Alice, recorded by Bob (<i> e2 wasQuoteOf Alice</i>). The RDF/XML syntax for asserting this is given below.</p>
@@ -1068,7 +1068,7 @@
<h4>wasSummaryOf</h4>
<p>The wasSummaryOf property links two instances of the Entity class.</p>
<img src="diagrams/wasSummaryOf.png"
- style="height: 3em" alt="wasSummaryOf links Entity to Entity" />
+ style="height: 5em" alt="wasSummaryOf links Entity to Entity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of wasSummaryOf property as an addition to the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is e3 summarizing some additional statistics(<i> e3 wasSummaryOf statistics</i>). The RDF/XML syntax for asserting this is given below.</p>
@@ -1086,7 +1086,7 @@
<h4>hadOriginalSource</h4>
<p>The hadOriginalSource property links two instances of the Entity class. This property is defined to be a specialization of the wasEventuallyDerivedFrom propery.</p>
<img src="diagrams/hadOriginalSource.png"
- style="height: 3em" alt="hadOriginalSource links Entity to Entity" />
+ style="height: 5em" alt="hadOriginalSource links Entity to Entity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadOriginalSource property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> e6 hadOriginalSource e1</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -1104,7 +1104,7 @@
<h4>hadQualifiedUsage</h4>
<p>The hadQualifiedUsage property links the Activity class with the Usage class.</p>
<img src="diagrams/hadQualifiedUsage.png"
- style="height: 3em" alt="hadQualifiedUsage links Activity to Usage" />
+ style="height: 5em" alt="hadQualifiedUsage links Activity to Usage" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadQualifiedUsage property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> act1 hadQualifiedUsage u1</i>, where the hadRole describes the usage of e1 as a "load". The RDF/XML syntax for asserting this is given below.</p>
@@ -1122,7 +1122,7 @@
<h4>hadQualifiedParticipation</h4>
<p>The hadQualifiedParticipation property links the Activity class with the Participation class.</p>
<img src="diagrams/hadQualifiedParticipation.png"
- style="height: 3em" alt="hadQualifiedParticipation links Activity to Participation" />
+ style="height: 5em" alt="hadQualifiedParticipation links Activity to Participation" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadQualifiedParticipation property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> act1 hadQualifiedParticipation p1</i>, where the hadRole describes the participation of Alice as an "author" in act1. The RDF/XML syntax for asserting this is given below.</p>
@@ -1143,7 +1143,7 @@
hadPlan if going for a different term. -Stian</div>
<p>The hadQualifiedControl property links the Activity class with the Control class.</p>
<img src="diagrams/hadQualifiedAssociation.png"
- style="height: 3em" alt="hadQualifiedAssociation links Activity to Association" />
+ style="height: 5em" alt="hadQualifiedAssociation links Activity to Association" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadQualifiedControl property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> act0 hadQualifiedControl c1</i>, where the hadRole describes the control of act0 by Alice as "creator". The RDF/XML syntax for asserting this is given below.</p>
@@ -1161,7 +1161,7 @@
<h4>hadQualifiedGeneration</h4>
<p>The hadQualifiedGeneration property links the Activity class with the Generation class.</p>
<img src="diagrams/hadQualifiedGeneration.png"
- style="height: 3em" alt="hadQualifiedGeneration links Activity to Generation" />
+ style="height: 5em" alt="hadQualifiedGeneration links Activity to Generation" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadQualifiedGeneration property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> e1 hadQualifiedGeneration g1</i>, where the hadRole describes the generation of e1 by "save". The RDF/XML syntax for asserting this is given below.</p>
@@ -1179,7 +1179,7 @@
<h4>hadQualifiedEntity</h4>
<p>The hadQualifiedEntity property links the QualifiedInvolvement class with the Entity class.</p>
<img src="diagrams/hadQualifiedEntity.png"
- style="height: 3em" alt="hadQualifiedInvolvement links QualifiedInvolvement to Entity" />
+ style="height: 5em" alt="hadQualifiedInvolvement links QualifiedInvolvement to Entity" />
<div class="anexample">
<div><b>Example</b></div>
<p> Example of hadQualifiedEntity property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> u2 hadQualifiedEntity e2</i>, where the hadRole describes the usage of e2 as an "attachment". The RDF/XML syntax for asserting this is given below.</p>
@@ -1232,7 +1232,7 @@
</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
</td></tr>
<tr>
- <td style="border-style: solid; border-width: 0 1px 1px 0"> hadParticipant
+ <td style="border-style: solid; border-width: 0 1px 1px 0"> wasAssociatedWith
</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
</td><td style="border-style: solid; border-width: 0 1px 1px 0">?
@@ -1315,7 +1315,7 @@
<section id="overview-of-qualified-involvement">
<h3>Overview of Qualified Involvement</h3>
- <p>The <a href="#qualifiedinvolvement">QualifiedInvolvement</a> class describes qualifying information on the PROV-O properties, namely <a href="#used">used</a>, <a href="#wasgeneratedby">wasGeneratedBy</a>, <a href="#wascontrolledby">wasControlledBy</a>, and <a href="#hadparticipant">hadParticipant</a>. The following figure illustrates the representation of qualifying information using these PROV-O classes and properties.</p>
+ <p>The <a href="#qualifiedinvolvement">QualifiedInvolvement</a> class describes qualifying information on the PROV-O properties, namely <a href="#used">used</a>, <a href="#wasgeneratedby">wasGeneratedBy</a>, <a href="#wascontrolledby">wasControlledBy</a>, and <a href="#hadparticipant">wasAssociatedWith</a>. The following figure illustrates the representation of qualifying information using these PROV-O classes and properties.</p>
<img src="diagrams/QualifiedInvolvementDiagram.png"
style="min-width: 45em; width: 55em; max-width: 95%"
alt="Classes and properties of qualified involvement in the PROV ontology"/>
@@ -1421,6 +1421,7 @@
<section class="appendix">
<h2>Changes Since First Public Working Draft</h2>
<ul>
+ <li>2012-01-18: hadParticipant was replaced with wasAssociatedWith. Restyled domain/range diagrams.</li>
<li>2012-01-17: Recipe changed to Plan, linked to Association
(formerly Control)</li>
<li>2012-01-16: Added Agent subclasses Person, Organization
@@ -1521,13 +1522,13 @@
</div>
</section>
<section id ="provenance-constraint-on-hasParticipant-participant">
- <h4>Provenance constraint on hadParticipant (participant)</h4>
- <p>The PROV-DM describes a constraint that hadParticipant property holds between an instance of Entity and instance of Activity if the two instances are linked by "used" of "wasControlledBy" or "wasComplementOf".
+ <h4>Provenance constraint on wasAssociatedWith (participant)</h4>
+ <p>The PROV-DM describes a constraint that wasAssociatedWith property holds between an instance of Entity and instance of Activity if the two instances are linked by "used" of "wasControlledBy" or "wasComplementOf".
</p>
- <div class='issue'> "Given two identifiers act and e, respectively identifying a process execution expression and an entity expression, the expression hadParticipant(pe,e) holds if and only if:
+ <div class='issue'> "Given two identifiers act and e, respectively identifying a process execution expression and an entity expression, the expression wasAssociatedWith(pe,e) holds if and only if:
*used(pe,e) holds, or
*wasControlledBy(pe,e) holds, or
- *wasComplementOf(e1,e) holds for some entity expression identified by e1, and hadParticipant(pe,e1) holds some process execution expression identified by act." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
+ *wasComplementOf(e1,e) holds for some entity expression identified by e1, and wasAssociatedWith(pe,e1) holds some process execution expression identified by act." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
</div>
</section>
</section>