--- a/ontology/ProvenanceFormalModel.html Fri Oct 07 13:58:47 2011 -0400
+++ b/ontology/ProvenanceFormalModel.html Fri Oct 07 14:12:20 2011 -0400
@@ -170,8 +170,9 @@
<p>The PROV ontology consists of seven classes that can be organized in a taxonomic structure.
</p>
<img src="diagram-history/khalidDiagrams/Ontology_hierarchy.png"
- style="width: 50%; min-width: 25em; max-width: 37em" alt="Class hierarchy of the PROV OWL ontology"/><br>
- <p/>
+ style="width: 50%; min-width: 25em; max-width: 37em"
+ alt="Class hierarchy of the PROV OWL ontology"/>
+ <br>
<p><i>Note: CamelBack notation is used for class names</i></p>
<section>
<h4>Entity</h4>
@@ -323,7 +324,7 @@
<h4>wasGeneratedBy</h4>
<p>wasGeneratedBy links Entity with ProcessExecution representing that Entity was generated as a result of ProcessExecution</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b4/WasGeneratedBy.png" alt="wasGeneratedBy links Entity to ProcessExecution" />
<div><b>Example</b></div>
<p> Example of wasGeneratedBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -344,7 +345,7 @@
<section>
<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>
- <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/3/34/WasDerivedFrom.png" alt="wasDerivedFrom links Entity to Entity"/>
<div><b>Example</b></div>
<p> Example of wasDerivedFrom property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>e3 wasDerivedFrom e2</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -361,7 +362,7 @@
<h4>Used</h4>
<p>Used links ProcessExecution to Entity, where Entity is consumed by ProcessExecution.</p>
<p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/Used.png" alt="prov:used links ProcessExecution to Entity"/>
<div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
<div><b>Example</b></div>
<p> Example of Used property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>pe2 Used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
@@ -386,7 +387,7 @@
<section>
<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>
- <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/2f/WasControlledBy.png" alt="wasControlledBy links ProcessExecution to Agent"/>
<div><b>Example</b></div>
<p> Example of wasControlledBy property from the <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
@@ -413,23 +414,20 @@
might or might not have been followed exactly by the Process
Execution.
</p>
- <img
- src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png" alt="prov:hadRecipe links ProcessExecution to Recipe."/>
</section>
<section>
<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>
- <img
- src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/0/08/WasInformedBy.png" alt="prov:wasInformedBy links ProcessExecution to ProcessExecution"/>
</section>
<section>
<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.
</p>
- <img
- src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/b/b5/WasScheduledAfter.png" alt="prov:wasScheduledAfter links ProcessExecution to ProcessExecution"/>
</section>
<section>
<h3>Characteristics of Object Properties </h3>
@@ -546,7 +544,7 @@
<section>
<h3>Overview of the ontology</h3>
<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" />
+ <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 OWL ontology"/>
</section>
</section>
@@ -647,7 +645,7 @@
</pre>
</div>
<p>The following diagram illustrates the above specialization: </p>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png"/>
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:EmailProcessExecution, cf:Journalist) extend the classes in the PROV OWL Ontology (Entity, Agent, ProcessExecution)."/>
<br>
<em>Example extension of PROV ontology in order to describe the crime file scenario</em>
</p>
@@ -709,7 +707,9 @@
<p>
<img
src="examples/ontology-extensions/workflow/workflowOntology.png"
- style="width: 60%; min-width: 20em; max-width: 40em" /><br>
+ style="width: 60%; min-width: 20em; max-width: 40em"
+ alt="New classes wf:WorkFlowEngine, wf:Process, wf:ValueAtPort, wf:FileValue, and wf:Value extend prov:Agent, prov:ProcessExecution, prov:EntityInRole. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubProcessExecutionOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom." />
+ <br>
<em>Example extension of PROV ontology in order to describe
workflow provenance</em>
</p>
@@ -935,7 +935,8 @@
</section>
<section>
<h4>Example workflow</h4>
- <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png" />
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/56/Concatsha1.png"
+ alt="An example workflow with input, three processes, and two outputs." />
<p>This is an example workflow which defines a workflow
input <i>input</i>, three processes <i>String_constant</i>,
<i>Concatenate_two_strings</i> and <i>sha1</i>, and finally