--- a/ontology/ProvenanceFormalModel.html Sun Oct 09 16:16:56 2011 -0400
+++ b/ontology/ProvenanceFormalModel.html Sun Oct 09 18:06:32 2011 -0400
@@ -1315,18 +1315,16 @@
<p>In addition to RDF Semantics, the OWL2 semantics as described in [[!OWL2-DIRECT-SEMANTICS]], [[!OWL2-RDF-BASED-SEMANTICS]] are also applicable to PROV ontology. We consider the OWL2 RDF-Based Semantics (since it is a semantics superset of OWL2 Direct Semantics) and specifically the extension of the D-interpretation, which satisfies the constraints for rdf-interpretation, rdfs-interpretation (as defined in previous section), graphs with blank nodes, and interpretation defined for RDF datatypes (see Section 5.1 in RDF Semantics [[!RDF-MT]]). The OWL2 RDF-based semantics introduces the notion of "facets" to constrain datatypes, both the rdf:XMLLiteral defined in the RDF Semantics [[!RDF-MT]] and datatypes defined in the OWL2 Structural Specifications [[!OWL2-SYNTAX]]. The OWL2 RDF-based interpretation, also called <b>D-interpretation with facets</b> is a D-interpretation that also satisfies the OWL2 RDF-based semantics called "semantic constraints" (see Section 5 in OWL2 RDF-Based Semantics [[!OWL2-RDF-BASED-SEMANTICS]]).
</p>
</section>
-
-
<section>
<h3>Provenance-specific Entailments Supported by PROV Ontology</h3>
<p>The PROV-DM [[PROV-DM]] introduces a set of specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.</p>
-
- <ul>
-<li> <a name="PROV:0001" href="#PROV:0001">PROV:0001</a> "From the
- assertion of a process execution, one can infer that the start
- precedes the end of the represented activity." (<a href="../model/ProvenanceModel.html#PROV:0001">link</a>)
-</li>
-
+ <section>
+ <h4>Provenance constraint on ProcessExecution</h4>
+ <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#processexecution">ProcessExecution.</a> </p>
+ <div class='issue'>"From a process execution expression, one can infer that the start event precedes the end event of the represented activity." This is <a href="http://www.w3.org/2011/prov/track/issues/121">ISSUE-121</a></div>
+ </section>
+ <section>
+ <h4>Provenance constraint on wasGeneratedBy</h4>
<li> <a name="PROV:0002" href="#PROV:0002">PROV:0002</a> "Given a process execution <b>pe</b>, entity <b>e</b>, role <b>r</b>, and optional time <b>t</b>,
if the assertion <b>wasGeneratedBy(e,pe,r)</b>
or <b>wasGeneratedBy(e,pe,r,t)</b> holds, the values of <em>some</em> of <b>e</b>'s
@@ -1337,7 +1335,7 @@
asserted."
(<a href="../model/ProvenanceModel.html#PROV:0002">link</a>)
</li>
-
+ </section>
<li><a name="PROV:0003" href="#PROV:0003">PROV:0003</a> "Given an assertion <b>wasGeneratedBy(x,pe,r)</b> or <b>wasGeneratedBy(x,pe,r,t)</b>, one can
infer that the generation of the thing denoted by <b>x</b> precedes the end
of <b>pe</b> and follows the beginning of <b>pe</b> "