--- a/ontology/ProvenanceFormalModel.html Mon Oct 17 21:32:43 2011 -0400
+++ b/ontology/ProvenanceFormalModel.html Mon Oct 17 22:00:59 2011 -0400
@@ -293,17 +293,17 @@
<section id="time">
- <h4>Time</h4>
+ <h4>TemporalEntity</h4>
<div><b>Class Description</b></div>
- <p>Time represents temporal information about entities in the Provenance model.</p>
+ <p>TemporalEntity represents temporal information about entities in the Provenance model. This class has been re-used from the OWL Time ontology. The PROV ontology also models the two sub classes of TemporalEntity, namely Instant and Interval.</p>
<div><b>OWL syntax</b></div>
- <pre>prov:Time rdfs:subClassOf owl:Thing.</pre>
+ <pre>time:TemporalEntity rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
- <p> Example of instances of class Time from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of Time is given below.
+ <p> Example of instances of class TemporalEntity from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. The RDF/XML syntax for this asserting that t+1 is an instance of class Instant is given below.
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#t+1">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/>
+ <rdf:type rdf:resource="http://www.w3.org/2006/time#Instant"/>
</rdf:Description>
</pre>
</div>
@@ -327,10 +327,15 @@
<p>ProvenanceContainer is defined to be an aggregation of provenance assertions. A provenance container should have an URI associated with it. The ProvenanceContainer class can also be used to model the PROV-DM concept of <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#expression-Account">Account</a>.</p>
<div><b>OWL syntax</b></div>
<pre>prov:ProvenanceContainer rdfs:subClassOf owl:Thing.</pre>
- <p>Examples of instance of class ProvenanceContainer includes a file describing the manufacturing details of a car, such as its batch number, manufacturer, date of manufacture, place of manufacture etc. </p>
+ <p>Examples of instance of class ProvenanceContainer includes a file describing the manufacturing details of a car, such as its batch number, manufacturer, date of manufacture, place of manufacture etc. </p>
+
<div class='note'> According to the definitions of ProvenanceContainer and Account, both contain a set of provenance assertions and have an identifier. Hence, ProvenanceContainer class can also be used to create instances of accounts.
</div>
<div class='issue'>Scope and Identifiers. This is <a href="http://www.w3.org/2011/prov/track/issues/81">ISSUE-81</a>.</div>
+ <section>
+ <h4>Modeling ProvenanceContainer and Account as RDF Graph</h4>
+ <p>Placeholder for Tim's description</p>
+ </section>
</section>
@@ -436,6 +441,19 @@
</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>
+ <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>
+ <div class='issue'>Is the current definition of wasEventuallyDerivedFrom inconsistent with definition of wasDerivedFrom? This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/126">ISSUE-126</a></div>
+ </section>
+
+ <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>
+ <div class='issue'>Is dependedOn a parent property of wasDerivedFrom? This is <a href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a>
+ </section>
</section>
@@ -531,6 +549,17 @@
style="height: 3em" alt="wasScheduledAfter links ProcessExecution to ProcessExecution" />
</section>
+ <section id="followed">
+ <h4>followed</h4>
+ <p>wasInformedBy links two instances of ProcessExecution to model ordering of the ProcessExecution instances.</p>
+ </section>
+
+ <section id="hastemporalvalue">
+ <h4>hasTemporalValue</h4>
+ <p> This object property links an instance of ProcessExecution or Entity with TemporalEntity thereby allowing association of time value with instances of the two classes and their subclasses
+ </p>
+ </section>
+
</section>
<section id="characteristics-of-object-properties">
@@ -1399,7 +1428,7 @@
<section id="provenance-constraint-on-wasgeneratedby-generation-pe-ordering">
<h4>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
<p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of the PE instance.</p>
- <div class='note'> Without an explicit association of <a href="#time">Time</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
</div>
</section>
<section id="provenance-constraint-on-wasgeneratedby-generation-unicity">
@@ -1429,7 +1458,7 @@
<h4>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</h4>
<p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1), then the for time instant t1 associated with a PE instance that "used" is less than the time instant t2 associated with "generation" of e2.
</p>
- <div class='note'> Without an explicit association of <a href="#time">Time</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
</div>
</section>
<section id ="provenance-constraint-on-derivation-events">
@@ -1457,7 +1486,7 @@
<h4>Provenance constraint on wasEventuallyDerivedFrom (derivation-generation-generation-ordering)</h4>
<p>The PROV-DM describes a constraint that if wasEventuallyDerivedFrom property is asserted between two Entity instances e1 and e2, then generation of e1 occurred before generation of e2.
</p>
- <div class='note'> Without an explicit association of <a href="#time">Time</a> (or event) with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> (or event) with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
</div>
</section>
<section id ="provenance-constraint-on-derivation-linked-independent">