misc. changes to meet XHTML+RDFa validation requirements
authorStephan Zednik <zednis@rpi.edu>
Mon, 26 Nov 2012 18:10:35 -0700
changeset 5151 6c3fdb444a70
parent 5150 3b7770c9f1d5
child 5153 cff302516fcd
misc. changes to meet XHTML+RDFa validation requirements
--- a/xml/releases/WD-prov-xml-20121211/Overview.html	Mon Nov 26 19:21:19 2012 -0500
+++ b/xml/releases/WD-prov-xml-20121211/Overview.html	Mon Nov 26 18:10:35 2012 -0700
@@ -1,19 +1,9 @@
 <?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd'>
+<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.0//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd'>
 <html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
     <title>PROV-XML: The PROV XML Schema</title> 
-    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 
-      === NOTA BENE ===
-      For the three scripts below, if your spec resides on dev.w3 you can check them
-      out in the same tree and use relative links so that they'll work offline,
-      -->
-<!--  PM  -->
+    <meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> 
 	<style type="text/css">
 	    .note { font-size:small; margin-left:50px }
@@ -47,17 +37,12 @@
-    <script>
-    $(function() {
-    	$("pre.schema-type").before("<p>Type definition in XML Schema:</p>");
-	    $("pre.schema-usage").before("<p>Usage in XML:</p>");
-    });
-    </script>
@@ -614,7 +599,8 @@
 <h3>Structure of this Document</h3>
 <p><a href="#schema-components">Section 2</a> provides an overview of the PROV XML Schema elements and types</p>
 <p><a href="#prov-xml-schema">Appendix A</a> contains the full PROV-XML Schema</p>
-</section> <!-- end structure-of-this-document  -->
+ -->
 <div id="prov-namespace" class="section">
@@ -774,46 +760,29 @@
 <div style="text-align: center;">
-<figure style="max-width: 95%; ">
+<span class="figure" id="fig-figure-1-prov-dm-components-informative" style="max-width: 95%; ">
 <img usemap="#componentMap" src="http://dvcs.w3.org/hg/prov/raw-file/default/model/images/dm/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; " />
-<map id="componentMap" name="componentMap">
+<map id="componentMap">
 <area title="agents/responsibility" href="#component3" coords="0,0,67,268" alt="agents/responsibility" shape="rect" />
 <area title="agents/responsibility" href="#component3" coords="67,0,134,201" alt="agents/responsibility" shape="rect" />
 <area title="agents/responsibility" href="#component3" coords="134,0,201,67" alt="agents/responsibility" shape="rect" />
 <area title="derivations" href="#component2" coords="201,0,268,201" alt="derivations" shape="rect" />
 <area title="derivations" href="#component2" coords="134,67,201,201" alt="derivations" shape="rect" />
-<area title="alternate" href="#component5" coords="268,0,335,67" alt="alternate" shape="rect" />
 <area title="alternate" href="#component5" coords="335,0,402,201" alt="alternate" shape="rect" />
 <area title="collections" href="#component6" coords="402,0,469,201" alt="collections" shape="rect" />
 <area title="activities/entities" href="#component1" coords="67,201,469,268" alt="activities/entities" shape="rect" />
-<area title="bundles" href="#component4" coords="268,67,402,201" alt="bundles" shape="rect" />
+<area title="bundles" href="#component4" coords="268,0,402,201" alt="bundles" shape="rect" />
 <br />
-<figcaption id="prov-dm-components">PROV-DM Components (Informative)</figcaption>  
-<!--  Figure 4  -->
+<span class="figcaption" id="prov-dm-components">Figure 1<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> ◊:</span></a></sup> PROV-DM Components (Informative)</span>
-While  not all PROV-DM relations are binary, they all involve two primary elements. Hence, Table <a href="#relations-at-a-glance">relations-at-a-glance</a> indexes all relations according to their two primary elements.  The table adopts the same color scheme as Figure <a href="#prov-dm-components">prov-dm-components</a>, allowing components to be readily identified.
-Note that for simplicity, this table  does not include collection-oriented relations.
- -->
-<!--  TODO add mapping of PROV-DM relations to Schema -->
-<p><a href="#prov-schema-mapping">Table X</a></p>
-<div id="prov-schema-mapping" style="text-align: left;">
+<p><a href="#prov-schema-mapping">Table 1</a> is a mapping of PROV-DM types and relations in PROV-XML schema XML types and elements.</p>
+<div id="prov-schema-mapping-div" style="text-align: center;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-types-and-relations">PROV-DM Types and Relations to XML Schema Mapping</caption> 
-<!--  Table X -->
+<caption id="prov-schema-mapping"><span>Table 1<sup><a class="internalDFN" href="#prov-schema-mapping"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Types and Relations to XML Schema Mapping</caption> 
 <tbody><tr><td><a><b>Type or Relation Name</b></a></td><td><b>XML Schema ComplexType or usage</b></td><td><b>Component</b></td></tr>
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
@@ -892,7 +861,7 @@
 <tr class="component3-color">
 	<td class="provType"><a href="#concept-plan" class="internalDFN">Plan</a></td>
-	<td><a title="plan" <pre="" href="#concept-plan" class="internalDFN">use &lt;prov:type&gt;prov:Plan&lt;/prov:type&gt; in Entity</a></td>
+	<td><a title="plan" href="#concept-plan" class="internalDFN">use &lt;prov:type&gt;prov:Plan&lt;/prov:type&gt; in Entity</a></td>
 <tr class="component3-color">
 	<td class="provType"><a href="#concept-person" class="internalDFN">Person</a></td>
@@ -951,13 +920,13 @@
 	<td><a title="hadMember">prov:Membership</a></td>
-<!--  add section for 'further elements'  -->
+<!-- <caption id="prov-dm-types-and-relations">PROV-DM Types and Relations to XML Schema Mapping</caption> -->
 <div class="note">
 <p>This mapping table is still under discussion and it's structure is subject to change.</p>
 <p>In the rest of the section, each type is defined, in English initially, followed by its XML schema definition and some example.</p>