--- a/ontology/ProvenanceFormalModel.html Sat Nov 05 17:17:37 2011 -0400
+++ b/ontology/ProvenanceFormalModel.html Sat Nov 05 21:19:54 2011 -0400
@@ -381,12 +381,12 @@
<div><b>OWL syntax</b></div>
<pre>prov:Recipe rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
- <p> An example of recipe from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario </a>may be the editing protocol followed by the journalists to edit a news report.
+ <p>An example of recipe from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario </a>may be the editing protocol followed by the journalists to edit a news report.
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#news_editing">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExection"/>
- <prov:hasRecipe rdf:resource="http://www.example.com/crimeFile#NewsReportEditingProtocol"/>
+ <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#NewsReportEditingProtocol"/>
</rdf:Description>
</pre>
</div>
@@ -437,28 +437,27 @@
<section id="object-properties">
<h3>Object Properties</h3>
- <p>The Provenance Model consists of the following object properties. </p>
+ <p>The PROV ontology has the following object properties. </p>
<p><i>Note: Names of properties starts with a verb in lower case followed by verb(s) starting with upper case </i></p>
<section id="wasgeneratedby">
<h4>wasGeneratedBy</h4>
- <p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
+ <p>The wasGeneratedBy property links the Entity class with the ProcessExecution class.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
<img src="diagram-history/khalidDiagrams/wasGeneratedBy.png"
style="height: 3em" alt="wasGeneratedBy links Entity to ProcessExecution" />
<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 pe0</i>. The RDF/XML syntax for asserting this is given below.
+ <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 pe0</i>. The RDF/XML syntax for asserting this information is given below.
+ </p>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#e1">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
- <rdf:type rdf:resource="http://www.example.com/crime#CrimeFile"/>
<prov:wasGeneratedBy>
<rdf:Description rdf:about="http://www.example.com/crimeFile#pe0">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
- <rdf:type rdf:resource="http://www.example.com/crime#FileCreation"/>
</rdf:Description>
<prov:wasGeneratedBy>
</rdf:Description>
@@ -468,16 +467,34 @@
<section id="revision">
<h4>wasRevisionOf</h4>
- <p>wasRevisionOf links two instances of Entity class, where one instance is a revision of another.</p>
+ <p>The wasRevisionOf property links two instances of Entity class, where one instance is a revision of another instance, and there is explicit role of an Agent in asserting this information.</p>
+ <div><b>Example</b></div>
+ <p>Example of wasRevisionOf property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e3 wasRevisionOf e2</i>. The RDF/XML syntax for asserting this information is given below.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
+ <prov:wasRevisionOf>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
+ </rdf:Description>
+ <prov:wasRevisionOf>
+ </rdf:Description>
+ </pre>
+ </div>
+ <div class='note'> Can instance of Agents be reasoning agents that infer the information that one Entity instance is a revision of another Entity instance and then asserts the information? In other words, is assertion after inference supported by this property?
+ </div>
</section>
<section id="wasderivedfrom">
<h4>wasDerivedFrom</h4>
- <p>wasDerivedFrom links two distinct characterized entities, where "some characterized entity is transformed from, created from, or affected by another characterized entity."</p>
+ <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="diagram-history/khalidDiagrams/wasDerivedFrom.png"
style="height: 3em" alt="wasDerivedFrom links Entity to Entity" />
<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.
+ <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.
+ </p>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#e3">
@@ -485,13 +502,13 @@
</rdf:Description>
</pre>
</div>
- <div class='issue'>Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
+ <div class='issue'>Should derivation have a time? Which time? This is <a href="http://www.w3.org/2011/prov/track/issues/43">ISSUE-43</a>.</div>
<div class='issue'>Should we specifically mention derivation of agents? This is <a href="http://www.w3.org/2011/prov/track/issues/42">ISSUE-42</a>.</div>
</section>
- <section>
+ <section id="waseventuallyderivedfrom">
<h4>wasEventuallyDerivedFrom</h4>
- <p>This object property is used to link two entities that are not directly used and generated respectively by a single instance of ProcessExecution.
+ <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 ProcessExecution class [[PROV-DM]].
</p>
<img src="diagram-history/khalidDiagrams/wasEventuallyDerivedFrom.png"
style="height: 3em" alt="wasEventuallyDerivedFrom links Entity to Entity" />
@@ -509,11 +526,11 @@
<section id="dependedon">
<h4>dependedOn</h4>
- <p>dependedOn links two instances of Entity to model derivation of one instance of Entity from another instance of Entity. This property is asserted to be transitive</p>
+ <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="diagram-history/khalidDiagrams/dependedOn.png"
- style="height: 3em" alt="dependedOn links Entity to Entity" />
+ style="height: 3em" alt="dependedOn links Entity to Entity"/>
<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>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>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#e5">
@@ -531,7 +548,7 @@
<section id="used">
<h4>used</h4>
- <p>used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
+ <p>The used property links the ProcessExecution class to the Entity class, where the Entity instance is "consumed" by a ProcessExecution instance.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
<img src="diagram-history/khalidDiagrams/used.png"
style="height: 3em" alt="used links ProcessExecution to Entity" />
@@ -549,7 +566,7 @@
<section id="hadparticipant">
<h4>hadParticipant</h4>
- <p>hadPariticipant links Entity to ProcessExecution, where Entity used or wasGeneratedBy ProcessExecution.
+ <p>The hadPariticipant property links Entity class to ProcessExecution class, where Entity used or wasGeneratedBy ProcessExecution.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
<img src="diagram-history/khalidDiagrams/hadParticipant.png"
style="height: 3em" alt="hadParticipant links ProcessExecution to Entity" />
@@ -563,22 +580,26 @@
</pre>
</div>
<div class='pending'>Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
+ <div class='note'> The current definition of hasParticipant does not account for involvement of an Entity in ProcessExecution where it was neither "used" or "generated". For example, a witness in a criminal activity.
+ </div>
</section>
<section id="wascomplementof">
<h4>wasComplementOf</h4>
- <p>wasComplementOf links two instances of Entity, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." <i>(from the Provenance Conceptual Model)</i></p>
+ <p>The wasComplementOf property links two instances of set of assertions about Entity instances, where "it is relationship between two characterized entities asserted to have compatible characterization over some continuous time interval." [[PROV-DM]]</p>
<img src="diagram-history/khalidDiagrams/wasComplementOf.png"
style="height: 3em" alt="wasComplementOf links Entity to Entity" />
+ <div class='note'> Should the wasComplementOf property link two instances of ProvenanceContainer (or Account) classes since they are two classes modeling a set of (one or more) provenance assertions?
+ </div>
</section>
<section id="wascontrolledby">
<h4>wasControlledBy</h4>
- <p>wasControlledBy links ProcessExecution to Agent, where "Control represents the involvement of an agent or a Entity in a process execution"<i>(from the Provenance Conceptual Model)</i></p>
+ <p>The wasControlledBy property links ProcessExecution class to Agent class, where control represents the involvement of the Agent in modifying the characteristics of the instance of the ProcessExecution class"[[PROV-DM]].</p>
<img src="diagram-history/khalidDiagrams/wasControlledBy.png"
style="height: 3em" alt="wasControlledBy links ProcessExecution to Agent" />
<div><b>Example</b></div>
@@ -600,16 +621,12 @@
<section id="hadrecipe">
<h4>hadRecipe</h4>
- <p>The ProcessExecution activity performed can be described as
- having the given recipe resource. It is out of the scope for PROV to
- define the structure or meaning of the recipe. The recipe
- might or might not have been followed exactly by the Process
- Execution.
+ <p>This property links the ProcessExecution class to the Recipe class, which describes the execution characteristics of the instance of the ProcessExecution class. The recipe might or might not have been followed exactly by the ProcessExecution.
</p>
<img src="diagram-history/khalidDiagrams/hadRecipe.png"
style="height: 3em" alt="hadRecipe links ProcessExecution to Agent" />
<div><b>Example</b></div>
- <p> Example of hadRecipe 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 pe1 using some file appending instructions (instructions1) (<i> pe1 hadRecipe instructions1</i>). The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of hadRecipe property in the (extended)<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is that pe1 (instance of ProcessExecution class) followed some file appending instructions (instructions1). 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#pe1">
@@ -623,7 +640,7 @@
<section id="wasinformedby">
<h4>wasInformedBy</h4>
- <p> This object property links two process executions. It is used to express the fact that a given process execution used an entity that was generated by another process execution.
+ <p> This object property links two instances of the ProcessExecution 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="diagram-history/khalidDiagrams/wasInformedBy.png"
style="height: 3em" alt="wasInformedBy links ProcessExecution to ProcessExecution" />
@@ -643,7 +660,7 @@
<section id="wascheduledafter">
<h4>wasScheduledAfter</h4>
<p>
- This object property links two instances of ProcessExecution to specify the order in which they took place. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
+ This property links two instances of ProcessExecution 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="diagram-history/khalidDiagrams/wasScheduledAfter.png"
style="height: 3em" alt="wasScheduledAfter links ProcessExecution to ProcessExecution" />
@@ -658,25 +675,44 @@
</div>
</section>
- <section id="followed">
- <h4>followed</h4>
- <p>wasInformedBy links two instances of ProcessExecution to model ordering of the ProcessExecution instances.</p>
- <img src="diagram-history/khalidDiagrams/followed.png"
- style="height: 3em" alt="followed links ProcessExecution to ProcessExecution" />
- <div><b>Example</b></div>
- <p> Example of followed property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 followed pe1</i>. The RDF/XML syntax for asserting this is given below.</p>
- <div class="exampleOuter">
+
+ <section id="hadtemporalvalue">
+ <h4>hadTemporalValue</h4>
+ <p> This object property links an instance of <code>ProcessExecution</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>
+ <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 pe3 ProcessExecution instanc</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#pe4">
- <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#pe1"/>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe3">
+ <prov:hasTemporalValue rdf:resource="http://www.example.com/crimeFile#t+3"/>
</rdf:Description>
</pre>
- </div>
- </section>
+ </div>
+ </section>
+ <section id="wasassumedby">
+ <h4>wasAssumedBy</h4>
+ <p>This property links an instance of <code>Entity</code> to its assumed <em>role</em>. This allows an instance of an Entity to participate in different or same instances of ProcessExecution class in different ways.
+ </p>
+ <img src="diagram-history/khalidDiagrams/wasAssumedBy.png"
+ style="height: 3em" alt="wasAssumedBy links EntityInRole to Entity" />
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
+ <prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ <p>
+ The example above corresponds to the PROV-ASN assertion:<code>used(pe1, bob, qualifier(role="author")</code>
+ </p>
+ </section>
+
<section id="attribution">
<h4>wasAttributedTo</h4>
- <p>wasAttributedTo links an instance of the Entity class to an instance of Agent class.</p>
+ <p>The wasAttributedTo property links an instance of the Entity class to an instance of Agent class.</p>
<img src="diagram-history/khalidDiagrams/wasAttributedTo.png"
style="height: 3em" alt="wasAttributedTo links Entity to Agent" />
<div><b>Example</b></div>
@@ -692,11 +728,11 @@
<section id="quotation">
<h4>wasQuoteOf</h4>
- <p>wasQuoteOf links an instance of the Entity class to an instance of of the Agent class.</p>
+ <p>The wasQuoteOf property links an instance of the Entity class to an instance of the Agent class.</p>
<img src="diagram-history/khalidDiagrams/wasQuoteOf.png"
style="height: 3em" alt="wasQuoteOf links Entity to Agent" />
<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 words, recorded by Bob (<i> e2 wasQuoteOf Alice</i>). The RDF/XML syntax for asserting this is given below.</p>
+ <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>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
@@ -708,7 +744,7 @@
<section id="summary">
<h4>wasSummaryOf</h4>
- <p>wasSummaryOf links two instances of the Entity class.</p>
+ <p>The wasSummaryOf property links two instances of the Entity class.</p>
<img src="diagram-history/khalidDiagrams/wasSummaryOf.png"
style="height: 3em" alt="wasSummaryOf links Entity to Entity" />
<div><b>Example</b></div>
@@ -724,7 +760,7 @@
<section id="originalsource">
<h4>hadOriginalSource</h4>
- <p>hadOriginalSource links two instances of the Entity class. This property is defined to be a specialization of the wasEventuallyDerivedFrom propery.</p>
+ <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="diagram-history/khalidDiagrams/hadOriginalSource.png"
style="height: 3em" alt="hadOriginalSource links Entity to Entity" />
<div><b>Example</b></div>
@@ -736,202 +772,196 @@
</rdf:Description>
</pre>
</div>
- </section>
-
- <section id="hadtemporalvalue">
- <h4>hadTemporalValue</h4>
- <p> This object property links an instance of
- <code>ProcessExecution</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. This property can be
- considered an abstract property, specialised by
- <code>startedAt</code>, <code>endedAt</code>,
- <code>wasGeneratedAt</code> and
- <code>assumedRoleAt</code> where the time MUST be specified as
- an <code>time:Instant</code> or more specifically MAY be
- specified using the PROV-O subclass <code>Time</code>
- which mandates the use of the
- <code>time:inXSDDateTime</code> data property.
- </p>
- </section>
- <section id="startedAt">
- <h4>startedAt</h4>
- <p> This object property defines the time when a
- <code>ProcessExecution</code> started. The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/startedAt.png"
- style="height: 3em" alt="startedAt links ProcessExecution to Instant" />
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:startedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-10-20T16:26:45Z</time:inXSDDateTime>
- </prov:startedAt>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <section id="endedAt">
- <h4>endedAt</h4>
- <p> This object property defines the time when a
- <code>ProcessExecution</code> ended. The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/endedAt.png"
- style="height: 3em" alt="endedAt links ProcessExecution to Instant" />
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:endedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-11-21T18:36:52Z</time:inXSDDateTime>
- </prov:endedAt>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <section id="wasGeneratedAt">
- <h4>wasGeneratedAt</h4>
- <p> This object property defines the time when a
- <code>Entity</code> was generated (as specified using
- <code>wasGeneratedBy</code>), meaning the instant when the entity
- first existed (and could be used by other process
- executions). The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/wasGeneratedAt.png"
- style="height: 3em" alt="wasGeneratedAt links Entity to Instant" />
- <p>
- Note that by constraint
- </p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
- <prov:wasGeneratedAt rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
- </prov:wasGeneratedAt>
- </rdf:Description>
- </pre>
- </div>
- </section>
- <section id="wasAssumedBy">
- <h4>wasAssumedBy</h4>
- <p>This object property defines which
- <code>Entity</code> assumed a <em>role</em>, forming
- a placeholder <code>EntityInRole</code> for use in
- relations such as <code>used</code> and
- <code>wasGeneratedBy</code>.
- <code>wasAssumedBy</code> is a required, functional property of
- <code>EntityInRole</code>, so an <code>EntityInRole</code>
- is assumed by one and only one <code>Entity</code>.
- <code>wasAssumedBy</code> is a subproperty of <code>wasComplementOf</code>.
- </p>
- <img src="diagram-history/khalidDiagrams/wasAssumedBy.png"
- style="height: 3em" alt="wasAssumedBy links EntityInRole to Entity" />
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <strong><prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/></strong>
- <prov:assumedRole rdf:resource="http://www.example.com/crime#author"/>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
- </rdf:Description>
- </pre>
- </div>
- <p>
- The example above corresponds to the PROV-ASN assertion:
- <code>used(pe1, bob, qualifier(role="author")</code>
- </p>
- </section>
- <section id="assumedRole">
- <h4>assumedRole</h4>
- <p>This object property defines which
- <code>Role</code> has been assumed in an
- <code>EntityInRole</code>. This property is applied in
- relations such as <code>used</code> and
- <code>wasGeneratedBy</code>.
- </p>
- <img src="diagram-history/khalidDiagrams/assumedRole.png"
- style="height: 3em" alt="assumedRole links EntityInRole to Role" />
- <p>
- The definition and interpretation of the <code>Role</code>
- is outside the scope for PROV-O. The <code>Role</code> class is
- a placeholder that can be extended and specialized.
- </p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/>
- <strong><prov:assumedRole rdf:resource="http://www.example.com/crime#author"/></strong>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used>
- </rdf:Description>
- </pre>
- </div>
- <p>
- The example above corresponds to the PROV-ASN assertion:
- <code>used(pe1, bob, qualifier(role="author")</code>
- </p>
- <div class="issue">
- It has been suggested that roles should be represented as
- classes, allowing hierarchies and composition of roles. <a
- href="http://www.w3.org/TR/owl2-new-features/#F12:_Punning">OWL2 punning</a>
- would allow both <code>:entityInRole rdf:type :ExampleRole</code> and
- <code>:entityInRole prov:assumedRole :ExampleRole</code>.
- </div>
- </section>
- <section id="assumedRoleAt">
- <h4>assumedRoleAt</h4>
- <p> This object property defines the first time an
- <code>Entity</code> assumed a <em>role</em>, ie. when the
- <code>EntityInRole</code> which <code>wasAssumedBy</code> was active.
- This is intended to be used together with a
- <code>used</code> statement to define the instant when an
- entity was first used. The time is specified as an
- <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
- <code>Time</code> subclass by specifying the time using a
- <code>time:inXSDDateTime</code> data property.
- </p>
- <img src="diagram-history/khalidDiagrams/assumedRoleAt.png"
- style="height: 3em" alt="assumedRoleAt links EntityInRole to Instant" />
- <p>
- According to the constraint <a
- href="#provenance-constraint-on-wasgeneratedby-generation-unicity">generation-unicity</a>
- from [[PROV-DM]] an entity can only be generated once by a single process
- execution. This ontology further assumes that all
- assertions about that generation must have the same
- start time.
- </p>
- <div class="exampleOuter">
- <pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <prov:used rdf:parseType="Resource">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
- <strong><prov:assumedRoleAt rdf:parseType="Resource"></strong>
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
- <strong><time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime></strong>
- </prov:assumedRoleAt>
- </prov:used>
- </rdf:Description>
- </pre>
- </div>
- </section>
+ </section>
+
+ <section>
+ <h4>Holding Section for Properties</h4>
+ <p>Temporary section for terms not part of "core" ontology.</p>
+ <section id="followed">
+ <h4>followed</h4>
+ <p>The followed links two instances of ProcessExecution to model ordering of the ProcessExecution instances.</p>
+ <img src="diagram-history/khalidDiagrams/followed.png"
+ style="height: 3em" alt="followed links ProcessExecution to ProcessExecution" />
+ <div><b>Example</b></div>
+ <p> Example of followed property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 followed pe1</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#pe4">
+ <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#pe1"/>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
+ <section>
+ <h4>hadTemporalValue</h4>
+ <p>This property can be considered an abstract property, specialised by
+ <code>startedAt</code>, <code>endedAt</code>,
+ <code>wasGeneratedAt</code> and
+ <code>assumedRoleAt</code> where the time MUST be specified as
+ an <code>time:Instant</code> or more specifically MAY be
+ specified using the PROV-O subclass <code>Time</code>
+ which mandates the use of the
+ <code>time:inXSDDateTime</code> data property.
+ </p>
+ </section>
+
+ <section>
+ <h4>wasAssumedBy</h4>
+ <p>, forming a placeholder <code>EntityInRole</code> for use in
+ relations such as <code>used</code> and
+ <code>wasGeneratedBy</code>.
+ <code>wasAssumedBy</code> is a required, functional property of
+ <code>EntityInRole</code>, so an <code>EntityInRole</code>
+ is assumed by one and only one <code>Entity</code>.
+ <code>wasAssumedBy</code> is a subproperty of <code>wasComplementOf</code>.</p>
+ </section>
+ <section id="startedAt">
+ <h4>startedAt</h4>
+ <p> This object property defines the time when a
+ <code>ProcessExecution</code> started. The time is specified as an
+ <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
+ <code>Time</code> subclass by specifying the time using a
+ <code>time:inXSDDateTime</code> data property.
+ </p>
+ <img src="diagram-history/khalidDiagrams/startedAt.png"
+ style="height: 3em" alt="startedAt links ProcessExecution to Instant" />
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:startedAt rdf:parseType="Resource">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <time:inXSDDateTime>2011-10-20T16:26:45Z</time:inXSDDateTime>
+ </prov:startedAt>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
+ <section id="endedAt">
+ <h4>endedAt</h4>
+ <p> This object property defines the time when a
+ <code>ProcessExecution</code> ended. The time is specified as an
+ <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
+ <code>Time</code> subclass by specifying the time using a
+ <code>time:inXSDDateTime</code> data property.
+ </p>
+ <img src="diagram-history/khalidDiagrams/endedAt.png"
+ style="height: 3em" alt="endedAt links ProcessExecution to Instant" />
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:endedAt rdf:parseType="Resource">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <time:inXSDDateTime>2011-11-21T18:36:52Z</time:inXSDDateTime>
+ </prov:endedAt>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
+ <section id="wasGeneratedAt">
+ <h4>wasGeneratedAt</h4>
+ <p> This object property defines the time when a
+ <code>Entity</code> was generated (as specified using
+ <code>wasGeneratedBy</code>), meaning the instant when the entity
+ first existed (and could be used by other process
+ executions). The time is specified as an
+ <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
+ <code>Time</code> subclass by specifying the time using a
+ <code>time:inXSDDateTime</code> data property.
+ </p>
+ <img src="diagram-history/khalidDiagrams/wasGeneratedAt.png"
+ style="height: 3em" alt="wasGeneratedAt links Entity to Instant" />
+ <p>
+ Note that by constraint
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#e2">
+ <prov:wasGeneratedAt rdf:parseType="Resource">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
+ </prov:wasGeneratedAt>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
+
+ <section id="assumedRole">
+ <h4>assumedRole</h4>
+ <p>This object property defines which
+ <code>Role</code> has been assumed in an
+ <code>EntityInRole</code>. This property is applied in
+ relations such as <code>used</code> and
+ <code>wasGeneratedBy</code>.
+ </p>
+ <img src="diagram-history/khalidDiagrams/assumedRole.png"
+ style="height: 3em" alt="assumedRole links EntityInRole to Role" />
+ <p>
+ The definition and interpretation of the <code>Role</code>
+ is outside the scope for PROV-O. The <code>Role</code> class is
+ a placeholder that can be extended and specialized.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:used>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
+ <prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/>
+ <strong><prov:assumedRole rdf:resource="http://www.example.com/crime#author"/></strong>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:used>
+ </rdf:Description>
+ </pre>
+ </div>
+ <p>
+ The example above corresponds to the PROV-ASN assertion:
+ <code>used(pe1, bob, qualifier(role="author")</code>
+ </p>
+ <div class="issue">
+ It has been suggested that roles should be represented as
+ classes, allowing hierarchies and composition of roles. <a
+ href="http://www.w3.org/TR/owl2-new-features/#F12:_Punning">OWL2 punning</a>
+ would allow both <code>:entityInRole rdf:type :ExampleRole</code> and
+ <code>:entityInRole prov:assumedRole :ExampleRole</code>.
+ </div>
+ </section>
+ <section id="assumedRoleAt">
+ <h4>assumedRoleAt</h4>
+ <p> This object property defines the first time an
+ <code>Entity</code> assumed a <em>role</em>, ie. when the
+ <code>EntityInRole</code> which <code>wasAssumedBy</code> was active.
+ This is intended to be used together with a
+ <code>used</code> statement to define the instant when an
+ entity was first used. The time is specified as an
+ <code>time:Instant</code> [[!OWL-TIME]], which MAY be a
+ <code>Time</code> subclass by specifying the time using a
+ <code>time:inXSDDateTime</code> data property.
+ </p>
+ <img src="diagram-history/khalidDiagrams/assumedRoleAt.png"
+ style="height: 3em" alt="assumedRoleAt links EntityInRole to Instant" />
+ <p>
+ According to the constraint <a
+ href="#provenance-constraint-on-wasgeneratedby-generation-unicity">generation-unicity</a>
+ from [[PROV-DM]] an entity can only be generated once by a single process
+ execution. This ontology further assumes that all
+ assertions about that generation must have the same
+ start time.
+ </p>
+ <div class="exampleOuter">
+ <pre class="example">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <prov:used rdf:parseType="Resource">
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/>
+ <strong><prov:assumedRoleAt rdf:parseType="Resource"></strong>
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <strong><time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime></strong>
+ </prov:assumedRoleAt>
+ </prov:used>
+ </rdf:Description>
+ </pre>
+ </div>
+ </section>
+ </section>
</section>