--- a/ontology/Overview.html Fri Feb 22 04:03:39 2013 -0500
+++ b/ontology/Overview.html Fri Feb 22 04:03:57 2013 -0500
@@ -2118,7 +2118,7 @@
.</pre>
</div>
- <div id="narrative-example-expanded-3" about="#narrative-example-expanded-3" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-expanded-3" about="#narrative-example-expanded-3" class="exampleOuter" >
<p>After some time, John wrote his own conclusions in his own post (<code>:post19201</code>) quoting the previous two posts.
Each quote that John makes (<code>:quote_from_monica</code> and <code>:quote_from_derek</code>) is a new entity derived from the
previous blogs and is annotated with the time that the quote was taken.
@@ -2182,7 +2182,7 @@
</div>
- <div id="narrative-example-expanded-4" about="#narrative-example-expanded-4" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-expanded-4" about="#narrative-example-expanded-4" class="exampleOuter" >
<p>Unfortunately, there was a problem in the servers where <code>:post19201</code> was being stored, and all the data related to the post was lost permanently.
Thus, the system invalidated the entity automatically and notified John about the error.
</p>
@@ -2406,7 +2406,7 @@
Because <span class="repeated">prov:Influence</span> is a broad relation, its most specific subclasses (e.g. <span class="repeated">prov:Communication</span>,
<span class="repeated">prov:Delegation</span>, <span class="repeated">prov:End</span>, <span class="repeated">prov:Revision</span>, etc.) should be used when applicable.
- </p><div id="narrative-example-qualified-1" about="#narrative-example-qualified-1" typeof="prov:Entity" class="exampleOuter" >
+ </p><div id="narrative-example-qualified-1" about="#narrative-example-qualified-1" class="exampleOuter" >
<p>
<a href="#narrative-example-qualified-1">Example 6</a>:
</p>
@@ -2428,7 +2428,7 @@
From this, the influence relation above can be restated with the <em>qualification pattern</em> as:
</p>
- <div id="narrative-example-qualified-2" about="#narrative-example-qualified-2" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-qualified-2" about="#narrative-example-qualified-2" class="exampleOuter" >
<p>
<a href="#narrative-example-qualified-2">Example 7</a>:
</p>
@@ -2522,7 +2522,7 @@
<p>The following two examples show the result of applying the Usage and Association patterns to the chart-making example from <a href="#description-starting-point-terms">Section 3.1</a>.
</p>
- <div id="narrative-example-qualified-3" about="#narrative-example-qualified-3" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-qualified-3" about="#narrative-example-qualified-3" class="exampleOuter" >
<p>
<a href="#narrative-example-qualified-3">Example 8</a>:
</p>
@@ -2553,7 +2553,7 @@
</div>
</div>
- <div id="narrative-example-qualified-4" about="#narrative-example-qualified-4" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-qualified-4" about="#narrative-example-qualified-4" class="exampleOuter" >
<p>
<a href="#narrative-example-qualified-4">Example 9</a>:
</p>
@@ -2595,7 +2595,7 @@
</p>
- <div id="narrative-example-qualified-5" about="#narrative-example-qualified-5" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-qualified-5" about="#narrative-example-qualified-5" class="exampleOuter" >
<p>
<a href="#narrative-example-qualified-5">Example 10</a>:
</p>
@@ -2626,7 +2626,7 @@
</div>
</div>
- <div id="narrative-example-qualified-6" about="#narrative-example-qualified-6" typeof="prov:Entity" class="exampleOuter" >
+ <div id="narrative-example-qualified-6" about="#narrative-example-qualified-6" class="exampleOuter" >
<p>
<a href="#narrative-example-qualified-6">Example 11</a>:
</p>
@@ -9933,7 +9933,7 @@
This extra effort can be reduced by preferring one inverse over another.
</p>
- <div about="#inverse-names-example-1" typeof="prov:Entity" class="exampleOuter" >
+ <div about="#inverse-names-example-1" class="exampleOuter" >
<p>For example, the first PROV-O statement (below) could just as easily be asserted as the second statement.
But if a client queries using <a class="qname" href="#wasDerivedFrom">prov:wasDerivedFrom</a> when <span class="repeated">:hadDerivation</span>
was used in the assertion, no results will be returned unless OWL reasoning is applied (or the size of the query is doubled).
@@ -9956,7 +9956,7 @@
they may be motivated to assert the inverse of any PROV-O property defined herein.
</p>
- <div about="#inverse-names-example-2" typeof="prov:Entity" class="exampleOuter" >
+ <div about="#inverse-names-example-2" class="exampleOuter" >
<p>For example, since PROV-O does not define the inverse of <a class="qname" href="#wasDerivedFrom">prov:wasDerivedFrom</a>,
and if three developers would rather model their assertions in the opposite direction, the following set of assertions might be found in the future web of provenance.
These assertions are not in an interoperable form without the use of an OWL reasoner, additional code, or larger queries.
@@ -9975,7 +9975,7 @@
Modelers wishing to use inverses of the properties defined by PROV-O <em class="rfc2119" title="should">should</em> use those reserved by this document.
</p>
- <div about="#inverse-names-example-3" typeof="prov:Entity" class="exampleOuter" >
+ <div about="#inverse-names-example-3" class="exampleOuter" >
<p>For example, the same three modelers above that defined <code>my:hadDerivation</code>, <code>your:ledTo</code>, and <code>their:derivedTo</code> should instead look for the <span class="repeated">http://www.w3.org/ns/prov#inverse</span> annotation on <a class="qname" href="#wasDerivedFrom">prov:wasDerivedFrom</a> to determine that they should use the property <span class="repeated">http://www.w3.org/ns/prov#hadDerivation</span>.
</p>
<pre class="example">@prefix prov: <http://www.w3.org/ns/prov#> .