additional updates in owl file
authorSatya Sahoo <satya.sahoo@case.edu>
Tue, 15 Nov 2011 11:03:20 -0500
changeset 899 141b6bd0df77
parent 898 ba947c45823d
child 900 c459d941b509
additional updates in owl file
ontology/ProvenanceFormalModel.html
ontology/ProvenanceOntology.owl
--- a/ontology/ProvenanceFormalModel.html	Tue Nov 15 15:58:06 2011 +0000
+++ b/ontology/ProvenanceFormalModel.html	Tue Nov 15 11:03:20 2011 -0500
@@ -968,85 +968,7 @@
 						</pre>
 					  </div>
 				</section>
-
-				<section id="assumedRole">
-			          <h4>assumedRole</h4>
-		              <p>This object property defines which
-		              <code>Role</code> has been assumed in an
-		              <code>EntityInRole</code>. This property is applied in
-		              relations such as <code>used</code> and
-		              <code>wasGeneratedBy</code>.
-		              </p>
-		              <img src="diagram-history/khalidDiagrams/assumedRole.png" 
-		               style="height: 3em"  alt="assumedRole links EntityInRole to Role" />	
-		              <p>
-		              The definition and interpretation of the <code>Role</code>
-		              is outside the scope for PROV-O. The <code>Role</code> class is
-		              a placeholder that can be extended and specialized.
-			          </p>
-		              <div class="exampleOuter">
-		                <pre class="example">
-		                    &lt;rdf:Description rdf:about="http://www.example.com/crimeFile#pe1"&gt;
-		                      &lt;prov:used&gt;
-		                        &lt;rdf:Description rdf:about="http://www.example.com/crimeFile#BobAsAuthor"&gt;
-		                            &lt;rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/&gt;
-		                            &lt;prov:wasAssumedBy rdf:resource="http://www.example.com/crimeFile#Bob"/&gt;
-		                            <strong>&lt;prov:assumedRole rdf:resource="http://www.example.com/crime#author"/&gt;</strong>
-		                        &lt;rdf:Description rdf:about="http://www.example.com/crimeFile#pe1"&gt;
-		                      &lt;prov:used&gt;
-		                    &lt;/rdf:Description&gt;	
-		                </pre>
-		              </div>		
-		              <p>
-		              The example above corresponds to the PROV-ASN assertion:
-		              <code>used(pe1, bob, qualifier(role="author")</code>
-		              </p>
-		              <div class="issue">
-		              It has been suggested that roles should be represented as
-		              classes, allowing hierarchies and composition of roles. <a
-		              href="http://www.w3.org/TR/owl2-new-features/#F12:_Punning">OWL2 punning</a>
-		              would allow both <code>:entityInRole rdf:type :ExampleRole</code> and
-		              <code>:entityInRole prov:assumedRole :ExampleRole</code>.
-		              </div>
-			    </section>
-				<section id="assumedRoleAt">
-			          <h4>assumedRoleAt</h4>
-		              <p> This object property defines the first time an
-		              <code>Entity</code> assumed a <em>role</em>, ie. when the
-		              <code>EntityInRole</code> which <code>wasAssumedBy</code> was active. 
-		              This is intended to be used together with a
-		              <code>used</code> statement to define the instant when an
-		              entity was first used. The time is specified as an
-		              <code>time:Instant</code> [[!OWL-TIME]], which MAY be a 
-		              <code>Time</code> subclass by specifying the time using a
-		              <code>time:inXSDDateTime</code> data property.
-			          </p>
-			          <img src="diagram-history/khalidDiagrams/assumedRoleAt.png" 
-		               style="height: 3em"  alt="assumedRoleAt links EntityInRole to Instant" />	
-		              <p>
-		              According to the constraint <a
-		              href="#provenance-constraint-on-wasgeneratedby-generation-unicity">generation-unicity</a>
-		              from [[PROV-DM]] an entity can only be generated once by a single process
-		              execution. This ontology further assumes that all
-		              assertions about that generation must have the same
-		              start time.
-		              </p>
-		              <div class="exampleOuter">
-		                <pre class="example">
-		                    &lt;rdf:Description rdf:about="http://www.example.com/crimeFile#pe1"&gt;
-		                      &lt;prov:used rdf:parseType="Resource"&gt;
-		                          &lt;rdf:type rdf:resource="http://www.w3.org/ns/prov-o/EntityInRole"/&gt;
-		                          <strong>&lt;prov:assumedRoleAt rdf:parseType="Resource"&gt;</strong>
-		                            &lt;rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Time"/&gt;
-		                            <strong>&lt;time:inXSDDateTime&gt;2011-10-20T17:14:12Z&lt;/time:inXSDDateTime&gt;</strong>
-		                         &lt;/prov:assumedRoleAt&gt;
-		                      &lt;/prov:used&gt;
-		                    &lt;/rdf:Description&gt;	
-		                </pre>
-		              </div>		
-			    </section>
-		</section>		
-
+		 </section>		
       </section>
 
 		<section id="characteristics-of-object-properties">
@@ -1137,19 +1059,7 @@
 		</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
 		</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
 		</td></tr></table>
-		<div class='note'>Some of them may be subject to discussion. In
-        particular, regarding the object properties
-        <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>used</i>,
-        we did not specify whether they are transitive or not. One may
-        argue that given that an agent can be a process execution, a
-        process execution, e.g., <i>pe1</i>, can be controlled by an
-        agent <i>pe2</i>, which happens to be a process execution that
-        is controlled by an agent <i>ag</i>, and that, therefore,
-        <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument
-        can be applied to <i>wasGeneratedBy</i> and <i>used</i>. That
-        said, we are not convinced that these properties should be
-        declared as transitive. In fact, we are more inclined towards
-        specifying that they are not.  </div>
+		<div class='note'>Some of the properties may be subject to discussion. In particular, regarding the object properties       <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>used</i>, we did not specify whether they are transitive or not. One may        argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an        agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore,        <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>used</i>. That        said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards        specifying that they are not.</div>
 	  </section>
 
 	  <section id="annotation-properties"> 
--- a/ontology/ProvenanceOntology.owl	Tue Nov 15 15:58:06 2011 +0000
+++ b/ontology/ProvenanceOntology.owl	Tue Nov 15 11:03:20 2011 -0500
@@ -221,18 +221,6 @@
     
 
 
-    <!-- http://www.w3.org/ns/prov-o/wasAssumedBy -->
-
-    <owl:ObjectProperty rdf:about="wasAssumedBy">
-        <rdf:type rdf:resource="&owl;AsymmetricProperty"/>
-        <rdf:type rdf:resource="&owl;FunctionalProperty"/>
-        <rdf:type rdf:resource="&owl;IrreflexiveProperty"/>
-        <rdfs:label xml:lang="en">assumed by</rdfs:label>
-        <rdfs:range rdf:resource="Entity"/>
-    </owl:ObjectProperty>
-    
-
-
     <!-- http://www.w3.org/ns/prov-o/wasAttributedTo -->
 
     <owl:ObjectProperty rdf:about="wasAttributedTo">