--- a/ontology/ProvenanceFormalModel.html Tue Sep 27 18:02:06 2011 +0100
+++ b/ontology/ProvenanceFormalModel.html Tue Sep 27 18:10:02 2011 +0100
@@ -496,6 +496,8 @@
style="width: 60%; min-width: 20em; max-width: 40em" /><br>
<em>Example extension of PROV ontology in order to describe
workflow provenance</em>
+ <div class='issue'>Some property names in this figure don't
+ match the text below</div>
</p>
<section>
<h4>Workflow extensions to PROV classes</h4>
@@ -570,6 +572,8 @@
multiple executions of the same workflow definition,
each of the separate <i>wf:Process</i>es will link to
the same definition.
+ <div class='issue'>Need prov:recipe in ontology -Stian</div>
+
</dd>
<dt>wf:ranInWorkflowEngine</dt>
<dd>
@@ -592,6 +596,7 @@
This subproperty of <i>prov:wasControlledBy</i> links a
<i>wf:Process</i> to another <i>prov:Process</i>, indicating
this is a child execution
+ <div class='issue'>Should there be a general way to state subprocesses? -Stian</div>
</dd>
<dt>wf:wasReadFrom</dt>
<dd>
@@ -625,6 +630,8 @@
pointed at Value because one can consider this
entity to to have the same attributes, but in
addition the <i>wf:seenAtPort</i> property is fixed.
+ <div class='issue'>Should be subproperty of
+ not-yet-existing prov:assumedBy -Stian</div>
</dd>
<dt>wf:wasSeenAtPort</dt>
@@ -640,6 +647,8 @@
<i>generation</i> of a value. The
<i>wf:ValueAtPort</i> is linked to the
<i>wf:Entity</i> using <i>prov:wasComplementOf</i>
+ <div class='issue'>Need
+ prov:assumedRole in ontology -Stian</div>
</dd>
</dl>
</section>