case insensitive anchors
authorTim L <>
Fri, 22 Feb 2013 04:01:20 -0500
changeset 5698 e1010bc0c279
parent 5697 25128edc84d9
child 5699 e38fce071ebb
case insensitive anchors
--- a/ontology/Overview.html	Fri Feb 22 03:58:40 2013 -0500
+++ b/ontology/Overview.html	Fri Feb 22 04:01:20 2013 -0500
@@ -1946,7 +1946,7 @@
       then Agents may also start or end Activities.
-        <div id="narrative-example-expanded-1" about="#narrative-example-expanded-1" typeof="prov:Entity" class="exampleOuter" xmlns:prov="">
+        <div id="narrative-example-expanded-1"class="exampleOuter">
            <p>The following examples illustrate the expanded terms by elaborating the <a href="#narrative-example-simple-1">crime chart example</a> from the previous section.
               After aggregating the dataset and creating the chart, Derek published a post to exhibit his work.
@@ -3832,7 +3832,7 @@
-         <div class="prov-expanded owl-classes crossreference" prefix="prov:">
+         <div class="prov-expanded owl-classes crossreference" >
   <div id="Collection" class="entity">
     <h3 id="x13--------class--prov-collection-----------------back-to-expanded-classes">
@@ -5702,7 +5702,7 @@
-         <div class="prov-qualified owl-classes crossreference" prefix="prov:">
+         <div class="prov-qualified owl-classes crossreference" >
   <div id="Influence" class="entity">
     <h3 id="x36--------class--prov-influence-----------------back-to-qualified-classes">
@@ -9021,7 +9021,7 @@
-  <div id="activity" class="entity">
+  <div id="p_activity" class="entity">
     <h3 id="x75--------property--prov-activity-op-----------------back-to-qualified-properties">
       <span class="xref" id="eg75">(75)</span>
       Property: <a href="#p_activity"><span class="dotted" title="">prov:activity</span></a> <sup class="type-op" title="object property">op</sup>
@@ -9092,7 +9092,7 @@
-  <div id="agent" class="entity">
+  <div id="p_agent" class="entity">
     <h3 id="x76--------property--prov-agent-op-----------------back-to-qualified-properties">
       <span class="xref" id="eg76">(76)</span>
       Property: <a href="#p_agent"><span class="dotted" title="">prov:agent</span></a> <sup class="type-op" title="object property">op</sup>
@@ -9933,7 +9933,7 @@
       This extra effort can be reduced by preferring one inverse over another.
-     <div about="#inverse-names-example-1" typeof="prov:Entity" class="exampleOuter" prefix="prov:">
+     <div about="#inverse-names-example-1" typeof="prov:Entity" 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.
-     <div about="#inverse-names-example-2" typeof="prov:Entity" class="exampleOuter" prefix="prov:">
+     <div about="#inverse-names-example-2" typeof="prov:Entity" 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.
-     <div about="#inverse-names-example-3" typeof="prov:Entity" class="exampleOuter" prefix="prov:">
+     <div about="#inverse-names-example-3" typeof="prov:Entity" 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"></span> annotation on <a class="qname" href="#wasDerivedFrom">prov:wasDerivedFrom</a> to determine that they should use the property <span class="repeated"></span>. 
         <pre class="example">@prefix prov: &lt;; .