exampleref javascript processing
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Fri, 25 May 2012 10:14:06 +0100
changeset 2979 ddd6e33c8459
parent 2978 70f3e0d479fd
child 2980 e2f24ffc93cf
exampleref javascript processing
model/prov-dm.html
--- a/model/prov-dm.html	Fri May 25 09:58:34 2012 +0100
+++ b/model/prov-dm.html	Fri May 25 10:14:06 2012 +0100
@@ -84,12 +84,30 @@
         });
       }
 
+
+      function updateExamplesRefs() {
+        $('.anexample-ref').each(function(index) {
+
+          myhref=$(this).attr('href');
+
+          console.log( "example ref for " + myhref);
+
+          mycount=$(myhref).attr('count');
+
+          console.log( "example ref for " + myhref + " " + mycount);
+
+          $(this).children('span').replaceWith(function(){return $('<span>').append("Example " + mycount)});
+
+        });
+      }
+
       $(document).ready(function(){
         // if glossary is in a string:
         $('#glossary_div').html(glossary_string)
         updateGlossaryRefs();
         updateFigCaptions();
         updateExamples();
+        updateExamplesRefs();
       });
 
     </script>
@@ -2394,7 +2412,10 @@
 </p>
 
 
-<p>The provenance of provenance can then be described using PROV constructs, as illustrated by the following examples.</p>
+<p>The provenance of provenance can then be described using PROV constructs, as illustrated by
+<a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example REF</span></a>
+and
+<a href="#anexample-provenance-aggregation" class="anexample-ref"><span>Example REF</span></a>.</p>
 
 <div class="anexample" id="anexample-provenance-of-provenance">
 <p>Let us consider two entities <span class="name">ex:report1</span> and <span class="name">ex:report2</span>.</p>
@@ -2472,7 +2493,7 @@
 <h3>Provenance Locator</h3>
 
 
-In <a href="#anexample-provenance-of-provenance">Example anexample-provenance-of-provenance</a>, we initially presented a scenario involving two entities <span class="name">report1</span> and <span class="name">report2</span>, and showed how the descriptions can be organized into two bundles.  There is no explicit indication that the second bundle "continues" the description offered by the first bundle.  Given that bundles may be retrieved separately [[PROV-AQ]], it is not obvious for a provenance consumer to navigate descriptions across bundles.  To aid consumers,
+In <a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example REF</span></a>, we initially presented a scenario involving two entities <span class="name">report1</span> and <span class="name">report2</span>, and showed how the descriptions can be organized into two bundles.  There is no explicit indication that the second bundle "continues" the description offered by the first bundle.  Given that bundles may be retrieved separately [[PROV-AQ]], it is not obvious for a provenance consumer to navigate descriptions across bundles.  To aid consumers,
  Alice may wish to express that there is further provenance information about <span class="name">report1</span> in bundle <span class="name">bob:bundle1</span>.  To this end, PROV introduces the notion of provenance locator, inspired by [[PROV-AQ]].