provo narrative
authorTim L <lebot@rpi.edu>
Tue, 10 Jul 2012 18:01:10 -0400
changeset 3916 81f6bc92472e
parent 3915 a043f8d3a78f
child 3917 1d8babc2a9a5
provo narrative
ontology/prov-o-html-sections/description-qualified-terms.inc.html
--- a/ontology/prov-o-html-sections/description-qualified-terms.inc.html	Tue Jul 10 17:57:47 2012 -0400
+++ b/ontology/prov-o-html-sections/description-qualified-terms.inc.html	Tue Jul 10 18:01:10 2012 -0400
@@ -54,50 +54,57 @@
        <a class="qname" href="#activity">prov:activity</a>, or
        <a class="qname" href="#agent">prov:agent</a>, respectively).
          <p>
-For example, given the unqualified statement:
-<pre class="example">
-:e1 
-   a prov:Entity;
-   prov:wasGeneratedBy :a1;
-.
-
-:a1 a prov:Activity .
-</pre>
-</p>
-<p>Then we find in PROV-O that <a class="qname" href="#wasGeneratedBy">prov:wasGeneratedBy</a> can be qualified with  
-the qualification property <a class="qname" href='#qualifiedGeneration'>prov:qualifiedGeneration</a> 
-and
-the class <a class="qname" href='#Generation'>prov:Generation</a>, which is a subclass of <a class ="qname" href="#ActivityInfluence">prov:ActivityInfluence</a>. From this, we can restate the above relation using the <em>qualification pattern</em> as:
-</p>
-<pre class="example">
-:e1 
-   a prov:Entity;
-   prov:wasGeneratedBy      :a1;
-   prov:qualifiedGeneration :e1Gen; # Add the qualification
-.
+            For example, given the unqualified statement:
+            <pre class="example">
+            :e1 
+               a prov:Entity;
+               prov:wasGeneratedBy :a1;
+            .
 
-:a1 a prov:Activity .
+            :a1 a prov:Activity .
+            </pre>
+         </p>
 
-:e1Gen 
-   a prov:Generation;
-   prov:activity :a1;               # Cite the influencing Activity.
-   :foo :bar;
-.
-</pre>
-<p>
-The asserter can thus attach additional properties to <code>:e1Gen</code> to
-describe the generation of <code>:e1</code>. To simplify client queries, any
-qualified relation SHOULD be accompanied by the equivalent unqualified
-statement. Unqualified properties SHOULD NOT have the equivalent qualified form
-asserted unless it adds additional information.  
-   </p>
+         <p>One can find that <a class="qname" href="#wasGeneratedBy">prov:wasGeneratedBy</a> 
+            can be qualified using the qualification property <a class="qname" href='#qualifiedGeneration'>prov:qualifiedGeneration</a> 
+            and the class <a class="qname" href='#Generation'>prov:Generation</a> (a subclass of <a class ="qname" href="#ActivityInfluence">prov:ActivityInfluence</a>). 
+            From this, the influence relation above can be restated with the <em>qualification pattern</em> as:
+         </p>
 
-      <p>In addition to the previous two tables, <a href="#qualified-terms-figure">Figure 4</a> illustrates the classes and properties needed to apply the qualification pattern to the thirteen unqualified influence relations. 
+            <pre class="example">
+            :e1 
+               a prov:Entity;
+               prov:wasGeneratedBy      :a1;
+               prov:qualifiedGeneration :e1Gen; # Add the qualification
+            .
 
-   For example, while <a class="qname" href="#qualifiedUsage">prov:qualifiedUsage</a>, <a class="qname" href="#Usage">prov:Usage</a>, and <a class="qname" href="#entity">prov:entity</a> are used to qualify 
-      <span class="repeated">prov:used</span> relations, 
+            :a1 a prov:Activity .
+
+            :e1Gen 
+               a prov:Generation;
+               prov:activity :a1;               # Cite the influencing Activity.
+               :foo :bar;
+            .
+            </pre>
+
+         <p>
+            The asserter can thus attach additional properties to <code>:e1Gen</code> to
+            describe the generation of <code>:e1</code>. To simplify client queries, any
+            qualified relation SHOULD be accompanied by the equivalent unqualified
+            statement. Unqualified properties SHOULD NOT have the equivalent qualified form
+            asserted unless it adds additional information.  
+        </p>
+
+      <p>In addition to the previous two tables, <a href="#qualified-terms-figure">Figure 4</a> 
+         illustrates the classes and properties needed to apply the qualification pattern to the thirteen unqualified influence relations. 
+
+         For example, while <a class="qname" href="#qualifiedUsage">prov:qualifiedUsage</a>, 
+         <a class="qname" href="#Usage">prov:Usage</a>, and <a class="qname" href="#entity">prov:entity</a> are used to qualify 
+         <span class="repeated">prov:used</span> relations, 
    
-      <a class="qname" href="#qualifiedAssociation">prov:qualifiedAssociation</a>, <a class="qname" href="#Association">prov:Association</a>, and <a class="qname" href="#agent">prov:agent</a> are used to qualify <span class="repeated">prov:wasAssociatedWith</span> relations. This pattern applies to the eleven other influence relations that can be qualified.
+         <a class="qname" href="#qualifiedAssociation">prov:qualifiedAssociation</a>, <a class="qname" href="#Association">prov:Association</a>, 
+         and <a class="qname" href="#agent">prov:agent</a> are used to qualify <span class="repeated">prov:wasAssociatedWith</span> 
+         relations. This pattern applies to the eleven other influence relations that can be qualified.
       </p>
 
       <p>In subfigure <strong>a</strong> the <span class="repeated">prov:qualifiedUsage</span> property parallels the <span class="repeated">prov:used</span> property and references an instance of