move enumerated constraints to appendix
authorSatya Sahoo <satya.sahoo@case.edu>
Wed, 23 Nov 2011 13:48:32 -0500
changeset 1020 db56253a6ffe
parent 1019 0309b252587d
child 1021 84b590566a58
move enumerated constraints to appendix
ontology/ProvenanceFormalModel.html
--- a/ontology/ProvenanceFormalModel.html	Wed Nov 23 17:58:25 2011 +0000
+++ b/ontology/ProvenanceFormalModel.html	Wed Nov 23 13:48:32 2011 -0500
@@ -1803,7 +1803,16 @@
 	</section>
 	<section id = "entailments-supported-by-the-provenance-model">
 	<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>
+	<p>The PROV-DM [[PROV-DM]] introduces a set of provenance-specific constraints. These provenance constraints will be modeled in PROV ontology as OWL axioms or as rules using the Rule Interchange Framework (RIF) [[!RIF-OVERVIEW]]. These constraints are expected to be used by provenance applications in addition to the PROV ontology file.</p>
+	<div class='note'> The provenance-specific constraints are currently under review and discussion. Individual constraints will be added to the PROV ontology or as RIF rules after the relevant issues are resolved. The provenance constraints are enumerated in Appendix
+	</div>
+	     
+    </section>   	  
+    </section>   	  
+
+	<section class="appendix"> 
+	<h2>Provenance-specific Constraints</h2>
+	<p>This section lists the provenance-specific constraints introduced by the PROV-DM [[PROV-DM]], but are still under discussion.
 	<section id="provenance-constraint-on-activity">
 	  <h4>Provenance constraint on Activity</h4>
 	  <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#activity">Activity.</a> </p>
@@ -1901,11 +1910,8 @@
 	    *wasControlledBy(pe,e) holds, or
 	    *wasComplementOf(e1,e) holds for some entity expression identified by e1, and hadParticipant(pe,e1) holds some process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
 	  </div>
-	</section>     
-    </section>   	  
-    </section>   	  
-
-
+	</section>
+	</section>
 
     <section class='appendix'>
       <h2>Acknowledgements</h2>