automatic restaging
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Thu, 21 Feb 2013 00:03:34 +0000
changeset 5636 9df76a4c14e9
parent 5635 3971808d7bbb
child 5637 c8e3c7cd9b15
automatic restaging
model/Makefile
model/releases/PR-dummy-xhtml/Overview.html
model/respec2xhtml.js
--- a/model/Makefile	Wed Feb 20 23:49:04 2013 +0000
+++ b/model/Makefile	Thu Feb 21 00:03:34 2013 +0000
@@ -75,12 +75,18 @@
 	cd diff; $(MAKE) rel
 
 stage.dm:
-	$(MAKE) DOCUMENT_TO_STAGE=prov-dm.html  RELEASE_DIR=releases/PR-prov-dm-20130312 stage.document
+	$(MAKE) DOCUMENT_TO_STAGE=prov-dm.html  RELEASE_DIR=releases/PR-prov-dm-20130312 stage.document.html
 stage.n:
-	$(MAKE) DOCUMENT_TO_STAGE=prov-n.html  RELEASE_DIR=releases/PR-prov-n-20130312 stage.document
+	$(MAKE) DOCUMENT_TO_STAGE=prov-n.html  RELEASE_DIR=releases/PR-prov-n-20130312 stage.document.html
 stage.constraints:
-	$(MAKE) DOCUMENT_TO_STAGE=prov-constraints.html  RELEASE_DIR=releases/PR-prov-constraints-20130312 stage.document
+	$(MAKE) DOCUMENT_TO_STAGE=prov-constraints.html  RELEASE_DIR=releases/PR-prov-constraints-20130312 stage.document.html
 
-stage.document:
+stage.document.html:
 	$(PHANTOM_JS) respec2html.js $(DOCUMENT_TO_STAGE) $(RELEASE_DIR)/Overview.html
 
+stage.document.xhtml:
+	$(PHANTOM_JS) respec2xhtml.js $(DOCUMENT_TO_STAGE) $(RELEASE_DIR)/Overview.html
+
+stage.dm.xhtml:
+	$(MAKE) DOCUMENT_TO_STAGE=prov-dm.html  RELEASE_DIR=releases/PR-dummy-xhtml stage.document.xhtml
+
--- a/model/releases/PR-dummy-xhtml/Overview.html	Wed Feb 20 23:49:04 2013 +0000
+++ b/model/releases/PR-dummy-xhtml/Overview.html	Thu Feb 21 00:03:34 2013 +0000
@@ -1,9 +1,8 @@
-<?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'>
-<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml">
+<!DOCTYPE html>
+<html lang="en" dir="ltr">
 <head> 
 <title>PROV-DM: The PROV Data Model</title> 
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 
 
  
 
@@ -15,9 +14,7 @@
 
 
 
-
 <!-- javascript for button to hide examples -->
-
 <script type="text/javascript">
 /*
 	Written by Jonathan Snook, http://www.snook.ca/jonathan
@@ -769,13 +766,11 @@
 .section dl.attrs dd, .section dl.eldef dd {
     margin-bottom:  0;
 }
-</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-PR" />
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
-</head> 
+</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-PR"><!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]--></head> 
   <body><div class="head">
   <p>
     
-      <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C" /></a>
+      <a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a>
     
   </p>
   <h1 class="title" id="title">PROV-DM: The PROV Data Model</h1>
@@ -842,7 +837,7 @@
       </p>
     
   
-  <hr />
+  <hr>
 </div> 
 
     <section id="abstract" class="introductory"><h2>Abstract</h2>
@@ -970,7 +965,7 @@
       
     
   
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction<br />
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction<br>
 </a><ul class="toc"><li class="tocline"><a href="#compliance-with-this-document" class="tocxref"><span class="secno">1.1 </span>Compliance with this Document</a></li><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.2 </span>Structure of this Document</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.3 </span>Notational Conventions</a></li><li class="tocline"><a href="#namespaces" class="tocxref"><span class="secno">1.4 </span>Namespaces</a></li></ul></li><li class="tocline"><a href="#section-prov-overview" class="tocxref"><span class="secno">2. </span>PROV Overview</a><ul class="toc"><li class="tocline"><a href="#core-structures" class="tocxref"><span class="secno">2.1 </span>PROV Core Structures</a><ul class="toc"><li class="tocline"><a href="#section-entity-activity" class="tocxref"><span class="secno">2.1.1 </span>Entity and Activity</a></li><li class="tocline"><a href="#section-derivation" class="tocxref"><span class="secno">2.1.2 </span>Derivation</a></li><li class="tocline"><a href="#section-agents-attribution-association-delegation" class="tocxref"><span class="secno">2.1.3 </span>Agents and Responsibility</a></li></ul></li><li class="tocline"><a href="#section-extended-structures" class="tocxref"><span class="secno">2.2 </span>PROV Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-mechanisms" class="tocxref"><span class="secno">2.2.1 </span>Mechanisms to Define Extended Structures</a><ul class="toc"><li class="tocline"><a href="#section-prov-extended-approach-subtyping" class="tocxref"><span class="secno">2.2.1.1 </span>Subtyping</a></li><li class="tocline"><a href="#section-prov-extended-approach-expanded-relation" class="tocxref"><span class="secno">2.2.1.2 </span>Expanded Relations</a></li><li class="tocline"><a href="#section-prov-extended-approach-optional-identification" class="tocxref"><span class="secno">2.2.1.3 </span>Optional Identification</a></li><li class="tocline"><a href="#section-prov-extended-approach-further-relations" class="tocxref"><span class="secno">2.2.1.4 </span>Further Relations</a></li></ul></li><li class="tocline"><a href="#section-provenance-of-provnance" class="tocxref"><span class="secno">2.2.2 </span>Provenance of Provenance</a></li><li class="tocline"><a href="#section-collections" class="tocxref"><span class="secno">2.2.3 </span>Collections</a></li></ul></li><li class="tocline"><a href="#section-overview-components" class="tocxref"><span class="secno">2.3 </span>Modular Organization</a></li></ul></li><li class="tocline"><a href="#prov-notation" class="tocxref"><span class="secno">3. </span>The Provenance Notation</a></li><li class="tocline"><a href="#prov-dm-example" class="tocxref"><span class="secno">4. </span>Illustration of PROV-DM by an Example</a><ul class="toc"><li class="tocline"><a href="#section-example-one" class="tocxref"><span class="secno">4.1 </span>Example: The Authors View</a></li><li class="tocline"><a href="#section-example-two" class="tocxref"><span class="secno">4.2 </span>Example: The Process View</a></li><li class="tocline"><a href="#section-example-c" class="tocxref"><span class="secno">4.3 </span>Example: Attribution of Provenance</a></li></ul></li><li class="tocline"><a href="#data-model-components" class="tocxref"><span class="secno">5. </span>PROV-DM Types and Relations</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">5.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#term-entity" class="tocxref"><span class="secno">5.1.1 </span>Entity</a></li><li class="tocline"><a href="#term-Activity" class="tocxref"><span class="secno">5.1.2 </span>Activity</a></li><li class="tocline"><a href="#term-Generation" class="tocxref"><span class="secno">5.1.3 </span>Generation</a></li><li class="tocline"><a href="#term-Usage" class="tocxref"><span class="secno">5.1.4 </span>Usage</a></li><li class="tocline"><a href="#term-Communication" class="tocxref"><span class="secno">5.1.5 </span>Communication</a></li><li class="tocline"><a href="#term-Start" class="tocxref"><span class="secno">5.1.6 </span>Start</a></li><li class="tocline"><a href="#term-End" class="tocxref"><span class="secno">5.1.7 </span>End</a></li><li class="tocline"><a href="#term-Invalidation" class="tocxref"><span class="secno">5.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">5.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#term-Derivation" class="tocxref"><span class="secno">5.2.1 </span>Derivation</a></li><li class="tocline"><a href="#term-revision" class="tocxref"><span class="secno">5.2.2 </span>Revision</a></li><li class="tocline"><a href="#term-quotation" class="tocxref"><span class="secno">5.2.3 </span>Quotation</a></li><li class="tocline"><a href="#term-primary-source" class="tocxref"><span class="secno">5.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">5.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#term-agent" class="tocxref"><span class="secno">5.3.1 </span>Agent</a></li><li class="tocline"><a href="#term-attribution" class="tocxref"><span class="secno">5.3.2 </span>Attribution</a></li><li class="tocline"><a href="#term-Association" class="tocxref"><span class="secno">5.3.3 </span>Association</a></li><li class="tocline"><a href="#term-delegation" class="tocxref"><span class="secno">5.3.4 </span>Delegation</a></li><li class="tocline"><a href="#term-influence" class="tocxref"><span class="secno">5.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">5.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#term-bundle" class="tocxref"><span class="secno">5.4.1 </span>Bundle constructor</a></li><li class="tocline"><a href="#term-bundle-entity" class="tocxref"><span class="secno">5.4.2 </span>Bundle Type</a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">5.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#term-specialization" class="tocxref"><span class="secno">5.5.1 </span>Specialization</a></li><li class="tocline"><a href="#term-alternate" class="tocxref"><span class="secno">5.5.2 </span>Alternate</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">5.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#term-collection" class="tocxref"><span class="secno">5.6.1 </span>Collection</a></li><li class="tocline"><a href="#term-membership" class="tocxref"><span class="secno">5.6.2 </span>Membership</a></li></ul></li><li class="tocline"><a href="#second-class-elements" class="tocxref"><span class="secno">5.7 </span>Further Elements of PROV-DM</a><ul class="toc"><li class="tocline"><a href="#term-identifier" class="tocxref"><span class="secno">5.7.1 </span>Identifier</a></li><li class="tocline"><a href="#term-attribute" class="tocxref"><span class="secno">5.7.2 </span>Attribute</a><ul class="toc"><li class="tocline"><a href="#term-attribute-label" class="tocxref"><span class="secno">5.7.2.1 </span>prov:label</a></li><li class="tocline"><a href="#term-attribute-location" class="tocxref"><span class="secno">5.7.2.2 </span>prov:location</a></li><li class="tocline"><a href="#term-attribute-role" class="tocxref"><span class="secno">5.7.2.3 </span>prov:role</a></li><li class="tocline"><a href="#term-attribute-type" class="tocxref"><span class="secno">5.7.2.4 </span>prov:type</a></li><li class="tocline"><a href="#term-attribute-value" class="tocxref"><span class="secno">5.7.2.5 </span>prov:value</a></li></ul></li><li class="tocline"><a href="#term-value" class="tocxref"><span class="secno">5.7.3 </span>Value</a></li><li class="tocline"><a href="#term-NamespaceDeclaration" class="tocxref"><span class="secno">5.7.4 </span>Namespace Declaration</a></li><li class="tocline"><a href="#term-qualified-name" class="tocxref"><span class="secno">5.7.5 </span>Qualified Name</a></li></ul></li></ul></li><li class="tocline"><a href="#extensibility-section" class="tocxref"><span class="secno">6. </span>PROV-DM Extensibility Points</a></li><li class="tocline"><a href="#valid-provenance" class="tocxref"><span class="secno">7. </span>Creating Valid Provenance</a></li><li class="tocline"><a href="#cross-references-to-prov-o-and-prov-n" class="tocxref"><span class="secno">A. </span>Cross-References to PROV-O and PROV-N</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno">B. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#changes-since-last-version" class="tocxref"><span class="secno">B.1 </span>Changes since last version</a></li><li class="tocline"><a href="#changes-since-last-call" class="tocxref"><span class="secno">B.2 </span>Changes since Last Call</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">C. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></section> 
 
 
@@ -980,9 +975,7 @@
 
 
     <section id="introduction"> 
-      
-<!--OddPage-->
-<h2><span class="secno">1. </span>Introduction<br />
+      <!--OddPage--><h2><span class="secno">1. </span>Introduction<br>
 </h2> 
 
 <p> 
@@ -1057,7 +1050,7 @@
 </p><ul>
 <li> Information in tables is normative if it appears in a normative section. </li>
 <li> All figures (including UML diagrams) are informative. </li>
-<li> Text in boxes labeled &quot;Example&quot; is informative.
+<li> Text in boxes labeled "Example" is informative.
 </li></ul>
 </section>
 
@@ -1090,10 +1083,10 @@
 
 
 
-<p>The key words &quot;<em class="rfc2119" title="must">must</em>&quot;, &quot;<em class="rfc2119" title="must not">must not</em>&quot;, &quot;<em class="rfc2119" title="required">required</em>&quot;, &quot;<em class="rfc2119" title="shall">shall</em>&quot;, &quot;<em class="rfc2119" title="shall
+<p>The key words "<em class="rfc2119" title="must">must</em>", "<em class="rfc2119" title="must not">must not</em>", "<em class="rfc2119" title="required">required</em>", "<em class="rfc2119" title="shall">shall</em>", "<em class="rfc2119" title="shall
       not">shall
-      not</em>&quot;, &quot;<em class="rfc2119" title="should">should</em>&quot;, &quot;<em class="rfc2119" title="should not">should not</em>&quot;, &quot;<em class="rfc2119" title="recommended">recommended</em>&quot;,  &quot;<em class="rfc2119" title="may">may</em>&quot;, and
-      &quot;<em class="rfc2119" title="optional">optional</em>&quot; in this document are to be interpreted as described in
+      not</em>", "<em class="rfc2119" title="should">should</em>", "<em class="rfc2119" title="should not">should not</em>", "<em class="rfc2119" title="recommended">recommended</em>",  "<em class="rfc2119" title="may">may</em>", and
+      "<em class="rfc2119" title="optional">optional</em>" in this document are to be interpreted as described in
       [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
 
 <p> 
@@ -1112,14 +1105,12 @@
 
 </p><div style="text-align: left;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="namespace-table"><span>Table 1<sup><a class="internalDFN" href="#namespace-table"><span class="diamond"> ◊:</span></a></sup> </span>Prefix and Namespaces used in this specification</caption> 
-<!-- Table 1-->
-
+<caption id="namespace-table"><span>Table 1<sup><a class="internalDFN" href="#namespace-table"><span class="diamond"> ◊:</span></a></sup> </span>Prefix and Namespaces used in this specification</caption> <!-- Table 1-->
 <tbody><tr><td><b>prefix</b></td><td><b>namespace IRI</b></td> <td><b>definition</b></td></tr>
 <tr><td>prov</td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see <a class="section-ref" href="#term-NamespaceDeclaration"><span>Section 5.7.4</span></a>)</td></tr>
 <tr><td>xsd</td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [<cite><a class="bibref" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>]</td></tr>
 <tr><td>rdf</td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace  [<cite><a class="bibref" href="#bib-RDF-CONCEPTS">RDF-CONCEPTS</a></cite>]</td></tr>
-<tr><td>(others)</td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br /> In particular, IRIs starting with &quot;http://example.com&quot; represent<br /> some application-dependent IRI [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>]</td></tr>
+<tr><td>(others)</td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br> In particular, IRIs starting with "http://example.com" represent<br> some application-dependent IRI [<cite><a class="bibref" href="#bib-RFC3987">RFC3987</a></cite>]</td></tr>
 </tbody></table>
 </div>
 
@@ -1131,9 +1122,7 @@
 
 
 <section class="informative" id="section-prov-overview"> 
-
-<!--OddPage-->
-<h2><span class="secno">2. </span>PROV Overview</h2><p><em>This section is non-normative.</em></p>
+<!--OddPage--><h2><span class="secno">2. </span>PROV Overview</h2><p><em>This section is non-normative.</em></p>
 
 <p>This section introduces provenance concepts with informal explanations and illustrative
 examples. PROV distinguishes  <em>core structures</em>, forming the essence of  provenance, from <em>extended structures</em> catering for more specific uses of provenance.  Core and extended structures are respectively presented in <a href="#core-structures">Section 2.1</a> and <a href="#section-extended-structures">Section 2.2</a>. Furthermore, the PROV data model is organized according to components, which form thematic groupings of concepts (see <a href="#section-overview-components">Section 2.3</a>). A <em>provenance description</em> is an instance of  a provenance structure, whether core or extended, described below.
@@ -1154,7 +1143,7 @@
 
 <div style="text-align: center; ">
  <span class="figure" id="prov-core-structures-top" style="max-width: 70%; ">
-<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; " /><br />
+<img src="uml/essentials.png" alt="PROV Core Structures" style="max-width: 70%; "><br>
 <span class="figcaption" id="prov-core-structures">Figure 1<sup><a class="internalDFN" href="#prov-core-structures"><span class="diamond"> ◊:</span></a></sup> PROV Core Structures (Informative)</span>
   </span>
 </div>
@@ -1172,9 +1161,7 @@
 
 <div style="text-align: left;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="overview-types-and-relations"><span>Table 2<sup><a class="internalDFN" href="#overview-types-and-relations"><span class="diamond"> ◊:</span></a></sup> </span>Mapping of PROV core concepts to  types and relations</caption> 
-<!-- Table 2 -->
-
+<caption id="overview-types-and-relations"><span>Table 2<sup><a class="internalDFN" href="#overview-types-and-relations"><span class="diamond"> ◊:</span></a></sup> </span>Mapping of PROV core concepts to  types and relations</caption> <!-- Table 2 -->
 <tbody><tr><td><b>PROV Concepts</b></td><td><b>PROV-DM types or relations</b></td><td><b>Name</b></td><td><b>Overview</b></td></tr>
 <tr>
 <td><a href="#concept-entity" class="internalDFN">Entity</a></td><td rowspan="3" style="text-align: center;">PROV-DM Types</td><td><a title="dfn-Entity" href="#dfn-entity" class="internalDFN">Entity</a></td><td style="text-align: center;"><a class="section-ref" href="#section-entity-activity"><span>Section 2.1.1</span></a></td></tr>
@@ -1199,8 +1186,8 @@
 
 
 <form action="#"><p> 
-<input id="hide-examples" onclick="set_display_by_class('div','anexample conceptexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button" value="Hide Concept Examples" /> 
-<input id="show-examples" onclick="set_display_by_class('div','anexample conceptexample',''); set_display_by_id('hide-examples',''); set_display_by_id('show-examples','none');" style="display: none" type="button" value="Show Concept Examples" /> 
+<input id="hide-examples" onclick="set_display_by_class('div','anexample conceptexample','none'); set_display_by_id('hide-examples','none'); set_display_by_id('show-examples','');" type="button" value="Hide Concept Examples"> 
+<input id="show-examples" onclick="set_display_by_class('div','anexample conceptexample',''); set_display_by_id('hide-examples',''); set_display_by_id('show-examples','none');" style="display: none" type="button" value="Show Concept Examples"> 
 </p> 
 </form> 
 
@@ -1212,7 +1199,7 @@
 <h4><span class="secno">2.1.1 </span>Entity and Activity</h4><p><em>This section is non-normative.</em></p>
 
 
-<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed aspects. The term &quot;things&quot; encompasses a broad diversity of notions, including digital objects such as a file or web page, 
+<p>In PROV, things we want to describe the provenance of are called <em>entities</em> and have some fixed aspects. The term "things" encompasses a broad diversity of notions, including digital objects such as a file or web page, 
 physical things such as a mountain, a building, a printed book, or a car as well as abstract concepts and ideas. 
 </p>
 
@@ -1285,8 +1272,8 @@
 correspond to several entities; in this case, a car in Boston may be a
 different entity from the same car in Cambridge.  
 Thus, among other things,
-an entity &quot;car in Boston&quot; would be used, and a new entity &quot;car in
-Cambridge&quot; would be generated by this activity of driving.  The
+an entity "car in Boston" would be used, and a new entity "car in
+Cambridge" would be generated by this activity of driving.  The
 provenance trace of the car might include: designed in Japan,
 manufactured in Korea, shipped to Boston USA, purchased by customer,
 driven to Cambridge, serviced by engineer in Cambridge, etc., all of
@@ -1355,12 +1342,10 @@
 of creating a painting, an artist may have mixed some paint that was
 never actually applied to the canvas: the painting would typically
 not be considered a derivation from the unused paint.  
-
 <!-- The provenance
 model does not attempt to define what constitutes derivation; rather,
 it is considered to be something that is asserted, having been
 determined by unspecified means. -->
-
 PROV does not attempt to specify the conditions under which derivations
 exist; rather, derivation is considered to have been determined by unspecified means. 
 Thus, while a chain of usage and generation is necessary for a
@@ -1625,10 +1610,8 @@
 
 </p><div id="components-overview-div" style="text-align: center;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="components-overview"><span>Table 3<sup><a class="internalDFN" href="#components-overview"><span class="diamond"> ◊:</span></a></sup> </span>Components Overview</caption> 
-<!-- Table 3:  -->
-
-<tbody><tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br />Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr> 
+<caption id="components-overview"><span>Table 3<sup><a class="internalDFN" href="#components-overview"><span class="diamond"> ◊:</span></a></sup> </span>Components Overview</caption> <!-- Table 3:  -->
+<tbody><tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br>Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 <tr><td style="	padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr> 
 <tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component2">5.2</a></td><td style="text-align: left;">about derivation and its subtypes</td></tr> 
@@ -1645,9 +1628,7 @@
 
 
 <section class="informative" id="prov-notation">  
-
-<!--OddPage-->
-<h2><span class="secno">3. </span>The Provenance Notation</h2><p><em>This section is non-normative.</em></p>
+<!--OddPage--><h2><span class="secno">3. </span>The Provenance Notation</h2><p><em>This section is non-normative.</em></p>
 
 
 <p>To illustrate the application of PROV concepts to a concrete example (see <a href="#prov-dm-example">Section 4</a>) and to provide examples of concepts (see <a href="#data-model-components">Section 5</a>),
@@ -1678,7 +1659,7 @@
 <div class="anexample" id="anexample-prov-n"><div class="anexampleTitle">Example 16<sup><a class="internalDFN" href="#anexample-prov-n"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
-</p><pre class="codeexample">activity(a1, [ prov:type=&quot;createFile&quot; ])
+</p><pre class="codeexample">activity(a1, [ prov:type="createFile" ])
 </pre>
 Two entities with identifiers <span class="name">e1</span> and <span class="name">e2</span>.
 <pre class="codeexample">entity(e1)
@@ -1700,9 +1681,7 @@
 
 
 <section class="informative" id="prov-dm-example"> 
-
-<!--OddPage-->
-<h2><span class="secno">4. </span>Illustration of PROV-DM by an Example</h2><p><em>This section is non-normative.</em></p>
+<!--OddPage--><h2><span class="secno">4. </span>Illustration of PROV-DM by an Example</h2><p><em>This section is non-normative.</em></p>
 
 <p><a href="#section-prov-overview">Section 2</a> has introduced some provenance concepts, and how they are expressed as types or relations in the PROV data model. The purpose of this section is to put these concepts into practice in order to express the provenance of some document published on the Web.  
 With this realistic example, PROV concepts are  composed together,  and a graphical illustration shows a provenance description forming a directed graph, rooted at the entity we want to explain the provenance of, and pointing to the entities, activities, and agents it depended on. This example also shows that, sometimes, multiple provenance descriptions about the same entity can co-exist, which then justifies the need for provenance of provenance.</p>
@@ -1735,22 +1714,20 @@
 
 <div style="text-align: center; ">
   <span class="figure" id="prov-a-document1-top">
-  <img src="images/dm/w3c-publication1.png" alt="Provenance of a Document (1)" style="max-width: 98%; " /><br />
-<span class="figcaption" id="prov-a-document1">Figure 2<sup><a class="internalDFN" href="#prov-a-document1"><span class="diamond"> ◊:</span></a></sup> Provenance of a Document (part 1)  (Informative)</span> 
-<!-- Figure 2 -->
-
+  <img src="images/dm/w3c-publication1.png" alt="Provenance of a Document (1)" style="max-width: 98%; "><br>
+<span class="figcaption" id="prov-a-document1">Figure 2<sup><a class="internalDFN" href="#prov-a-document1"><span class="diamond"> ◊:</span></a></sup> Provenance of a Document (part 1)  (Informative)</span> <!-- Figure 2 -->
   </span>
 </div>
 
 
 <ul>
 <li>There was a document <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which from the author's perspective was a document in its second version. 
-<pre>entity(tr:WD-prov-dm-20111215, [ prov:type=&quot;document&quot;, ex:version=&quot;2&quot; ])
+<pre>entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
 </pre>
 </li>
 
 <li>There was an editing activity.
-<pre>activity(ex:edit1, [ prov:type=&quot;edit&quot; ])
+<pre>activity(ex:edit1, [ prov:type="edit" ])
 </pre>
 </li>
 
@@ -1767,8 +1744,8 @@
 </li>
 
 <li>Agents were assigned various responsibilities in the editing activity: contributor and editor. The plan the agent relied upon is not specified, hence, the marker '-'.
-<pre>wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role=&quot;editor&quot; ])
-wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role=&quot;contributor&quot; ])
+<pre>wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
+wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
 </pre>
 </li>
 </ul>
@@ -1795,9 +1772,9 @@
 Consortium publishes documents according to its publication
 policy.  Working drafts are published regularly to reflect the work
 accomplished by working groups. Every publication of a working draft
-must be preceded by a &quot;publication request&quot; to the Webmaster.  The
+must be preceded by a "publication request" to the Webmaster.  The
 very first version of a document must also be preceded by a
-&quot;transition request&quot; to be approved by the <abbr title="World Wide Web Consortium">W3C</abbr> director.  All working
+"transition request" to be approved by the <abbr title="World Wide Web Consortium">W3C</abbr> director.  All working
 drafts are made available at a unique IRI.  In this scenario, we consider two successive versions of a given document, the policy according to which they were published, and the associated requests.
 </p>
 
@@ -1823,10 +1800,8 @@
 
 </p><div style="text-align: center;">
   <span class="figure" id="prov-a-document2-top">
-  <img src="images/dm/w3c-publication2.png" alt="Provenance of a Document (2)" style="max-width: 90%; " /><br />
-<span class="figcaption" id="prov-a-document2">Figure 3<sup><a class="internalDFN" href="#prov-a-document2"><span class="diamond"> ◊:</span></a></sup> Provenance of a Document (part 2) (Informative)</span> 
-<!-- figure 3 -->
-
+  <img src="images/dm/w3c-publication2.png" alt="Provenance of a Document (2)" style="max-width: 90%; "><br>
+<span class="figcaption" id="prov-a-document2">Figure 3<sup><a class="internalDFN" href="#prov-a-document2"><span class="diamond"> ◊:</span></a></sup> Provenance of a Document (part 2) (Informative)</span> <!-- figure 3 -->
   </span>
 </div>
 
@@ -1838,7 +1813,7 @@
 </pre>
 </li>
 <li>There was a publication activity.
-<pre>activity(ex:act2, [ prov:type=&quot;publish&quot; ])
+<pre>activity(ex:act2, [ prov:type="publish" ])
 </pre>
 </li>
 
@@ -1923,9 +1898,7 @@
 
 <section id="data-model-components"> 
 
-
-<!--OddPage-->
-<h2><span class="secno">5. </span>PROV-DM Types and Relations</h2>
+<!--OddPage--><h2><span class="secno">5. </span>PROV-DM Types and Relations</h2>
 
 <p>Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components that are defined in this section.
 The components and their dependencies are illustrated in <a href="#prov-dm-components">Figure 4</a>. A component that relies on concepts defined in another is displayed above it in the figure.  So, for example, component 5 (alternate) depends on concepts defined in component 4 (bundles), itself dependent on concepts defined in component 1 (entity and activity).
@@ -1946,25 +1919,21 @@
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-4-prov-dm-components-informative" style="max-width: 95%; ">
-<img usemap="#componentMap" src="images/dm/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; " />
+<img usemap="#componentMap" src="images/dm/components-dependencies.png" alt="PROV-DM Components" style="max-width: 90%; ">
 <map id="componentMap" name="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="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,0,402,201" alt="bundles" 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,0,402,201" alt="bundles" shape="rect">
 </map>
-<br />
-<span class="figcaption" id="prov-dm-components">Figure 4<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> ◊:</span></a></sup> PROV-DM Components (Informative)</span>  
-<!-- Figure 4 -->
-
+<br>
+<span class="figcaption" id="prov-dm-components">Figure 4<sup><a class="internalDFN" href="#prov-dm-components"><span class="diamond"> ◊:</span></a></sup> PROV-DM Components (Informative)</span>  <!-- Figure 4 -->
 </span>
 </div>
 
@@ -1976,13 +1945,11 @@
 
 <div id="relations-at-a-glance-div" style="text-align: center;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="relations-at-a-glance"><span>Table 4<sup><a class="internalDFN" href="#relations-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Relations At a Glance</caption> 
-<!-- Table 4 -->
-
+<caption id="relations-at-a-glance"><span>Table 4<sup><a class="internalDFN" href="#relations-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Relations At a Glance</caption> <!-- Table 4 -->
 <tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="6">Object</td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="2">Entity</td><td colspan="2">Activity</td><td colspan="2">Agent</td></tr> 
-<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential internalDFN" title="wasDerivedFrom" href="#dfn-wasderivedfrom">WasDerivedFrom</a><br /><a href="#concept-revision" class="internalDFN">Revision</a><br /><a href="#concept-quotation" class="internalDFN">Quotation</a><br /><a title="Primary Source" href="#concept-primary-source" class="internalDFN">PrimarySource</a></div><div class="component5-color"><a title="alternateOf" href="#dfn-alternateof" class="internalDFN">AlternateOf</a><br /><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">SpecializationOf</a></div><div class="component6-color"><a title="hadMember" href="#dfn-hadmember" class="internalDFN">HadMember</a></div></td><td class="component1-color"><a class="essential internalDFN" title="wasGeneratedBy" href="#dfn-wasgeneratedby">WasGeneratedBy</a><br /><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br /><a title="time" href="#dfn-time" class="internalDFN">T</a><br /><a title="location" href="#concept-location" class="internalDFN">L</a><br /></td><td class="component3-color" colspan="2"><a class="essential internalDFN" title="wasAttributedTo" href="#dfn-wasattributedto">WasAttributedTo</a></td></tr>
-<tr><td>Activity</td><td class="component1-color"><a class="essential internalDFN" title="used" href="#dfn-used">Used</a><br /><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a><br /><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br /><a title="time" href="#dfn-time" class="internalDFN">T</a><br /><a title="location" href="#concept-location" class="internalDFN">L</a><br /></td><td colspan="2" class="component1-color"><a class="essential internalDFN" title="wasInformedBy" href="#dfn-wasinformedby">WasInformedBy</a></td><td class="component3-color"><a class="essential internalDFN" title="wasAssociatedWith" href="#dfn-wasassociatedwith">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br /></td></tr>
+<tr><td rowspan="3">Subject</td><td>Entity</td><td colspan="2"><div class="component2-color"><a class="essential internalDFN" title="wasDerivedFrom" href="#dfn-wasderivedfrom">WasDerivedFrom</a><br><a href="#concept-revision" class="internalDFN">Revision</a><br><a href="#concept-quotation" class="internalDFN">Quotation</a><br><a title="Primary Source" href="#concept-primary-source" class="internalDFN">PrimarySource</a></div><div class="component5-color"><a title="alternateOf" href="#dfn-alternateof" class="internalDFN">AlternateOf</a><br><a title="specializationOf" href="#dfn-specializationof" class="internalDFN">SpecializationOf</a></div><div class="component6-color"><a title="hadMember" href="#dfn-hadmember" class="internalDFN">HadMember</a></div></td><td class="component1-color"><a class="essential internalDFN" title="wasGeneratedBy" href="#dfn-wasgeneratedby">WasGeneratedBy</a><br><a title="wasInvalidatedBy" href="#dfn-wasinvalidatedby" class="internalDFN">WasInvalidatedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br><a title="time" href="#dfn-time" class="internalDFN">T</a><br><a title="location" href="#concept-location" class="internalDFN">L</a><br></td><td class="component3-color" colspan="2"><a class="essential internalDFN" title="wasAttributedTo" href="#dfn-wasattributedto">WasAttributedTo</a></td></tr>
+<tr><td>Activity</td><td class="component1-color"><a class="essential internalDFN" title="used" href="#dfn-used">Used</a><br><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a><br><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a></td><td class="component1-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br><a title="time" href="#dfn-time" class="internalDFN">T</a><br><a title="location" href="#concept-location" class="internalDFN">L</a><br></td><td colspan="2" class="component1-color"><a class="essential internalDFN" title="wasInformedBy" href="#dfn-wasinformedby">WasInformedBy</a></td><td class="component3-color"><a class="essential internalDFN" title="wasAssociatedWith" href="#dfn-wasassociatedwith">WasAssociatedWith</a></td><td class="component3-color" style="font-style: italic; "><a title="role" href="#concept-role" class="internalDFN">R</a><br></td></tr>
 <tr><td>Agent</td><td colspan="2">—</td><td colspan="2">—</td><td class="component3-color" colspan="2"><a class="essential internalDFN" title="actedOnBehalfOf" href="#dfn-actedonbehalfof">ActedOnBehalfOf</a></td></tr>
 </tbody></table>
 </div>
@@ -2003,13 +1970,11 @@
 
 <div id="secondary-elements-relations-at-a-glance-div" style="text-align: center;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="secondary-elements-relations-at-a-glance"><span>Table 5<sup><a class="internalDFN" href="#secondary-elements-relations-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>Secondary optional elements in PROV-DM Relations</caption> 
-<!-- Table 4 -->
-
+<caption id="secondary-elements-relations-at-a-glance"><span>Table 5<sup><a class="internalDFN" href="#secondary-elements-relations-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>Secondary optional elements in PROV-DM Relations</caption> <!-- Table 4 -->
 <tbody><tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td colspan="3">Secondary Object</td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td>Entity</td><td>Activity</td><td>Agent</td></tr> 
 <tr><td rowspan="3">Subject</td><td>Entity</td><td>—</td><td class="component2-color"><a title="wasDerivedFrom" href="#dfn-wasderivedfrom" class="internalDFN">WasDerivedFrom</a> (<a href="#derivation.activity">activity</a>)</td><td>—</td></tr>
-<tr><td>Activity</td><td class="component3-color"><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN">WasAssociatedWith</a> (<a href="#association.plan">plan</a>)</td><td class="component1-color"><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a> (<a href="#start.starter">starter</a>)<br /><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a> (<a href="#end.ender">ender</a>)</td><td>—</td></tr>
+<tr><td>Activity</td><td class="component3-color"><a title="wasAssociatedWith" href="#dfn-wasassociatedwith" class="internalDFN">WasAssociatedWith</a> (<a href="#association.plan">plan</a>)</td><td class="component1-color"><a title="wasStartedBy" href="#dfn-wasstartedby" class="internalDFN">WasStartedBy</a> (<a href="#start.starter">starter</a>)<br><a title="wasEndedBy" href="#dfn-wasendedby" class="internalDFN">WasEndedBy</a> (<a href="#end.ender">ender</a>)</td><td>—</td></tr>
 <tr><td>Agent</td><td>—</td><td class="component3-color"><a title="actedOnBehalfOf" href="#dfn-actedonbehalfof" class="internalDFN">ActedOnBehalfOf</a> (<a href="#delegation.activity">activity</a>)</td><td>—</td></tr>
 </tbody></table>
 </div>
@@ -2020,9 +1985,7 @@
 
 <div id="prov-dm-types-and-relations-fig" style="text-align: left;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-types-and-relations"><span>Table 6<sup><a class="internalDFN" href="#prov-dm-types-and-relations"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Types and Relations</caption> 
-<!-- Table 6-->
-
+<caption id="prov-dm-types-and-relations"><span>Table 6<sup><a class="internalDFN" href="#prov-dm-types-and-relations"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Types and Relations</caption> <!-- Table 6-->
 <tbody><tr><td><b>Type or Relation Name</b></td><td><b>Representation in the PROV-N notation</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>
 
@@ -2086,10 +2049,8 @@
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-5-entities-and-activities-component-overview-informative" style="max-width: 95%; ">
-<img src="uml/component1.png" alt="entities and activities" /><br />
-<span class="figcaption" id="figure-component1">Figure 5<sup><a class="internalDFN" href="#figure-component1"><span class="diamond"> ◊:</span></a></sup> Entities and Activities Component Overview (Informative)</span> 
-<!-- Figure 5 -->
-
+<img src="uml/component1.png" alt="entities and activities"><br>
+<span class="figcaption" id="figure-component1">Figure 5<sup><a class="internalDFN" href="#figure-component1"><span class="diamond"> ◊:</span></a></sup> Entities and Activities Component Overview (Informative)</span> <!-- Figure 5 -->
 </span>
 </div>
 
@@ -2114,7 +2075,7 @@
 <div class="anexample" id="anexample-entity"><div class="anexampleTitle">Example 17<sup><a class="internalDFN" href="#anexample-entity"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following expression</p>
-<pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type=&quot;document&quot;, ex:version=&quot;2&quot; ])
+<pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
 </pre>
 states the existence of an entity, denoted by identifier <span class="name">tr:WD-prov-dm-20111215</span>,  with type <span class="name">document</span> and version number <span class="name">2</span>. The attribute <span class="name">ex:version</span> is application specific, whereas the attribute <span class="name">type</span> (see <a href="#term-attribute-type">Section 5.7.4.4</a>) is reserved in the <a title="prov-namespace" href="#dfn-prov-namespace" class="internalDFN">PROV namespace</a>.
 </div>
@@ -2142,7 +2103,7 @@
 <p>
 The following expression</p>
 <pre class="codeexample">activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,
-        [ ex:host=&quot;server.example.org&quot;, prov:type='ex:edit' ])
+        [ ex:host="server.example.org", prov:type='ex:edit' ])
 </pre>
 <p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span>.  The attribute <span class="name">host</span>  is application specific  (declared in some namespace with prefix <span class="name">ex</span>).  The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed  (see <a class="section-ref" href="#term-attribute-type"><span>Section 5.7.2.4</span></a>).</p>
 </div>
@@ -2174,7 +2135,7 @@
 <li><span class="attribute" id="generation.entity">entity</span>:  an identifier (<span class="name">e</span>) for a created entity; </li>
 <li><span class="attribute" id="generation.activity">activity</span>:  an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">a</span>) for the activity that creates the entity;</li>
 
-<li><span class="attribute" id="generation.time">time</span>: an <em class="rfc2119" title="optional">optional</em> &quot;generation time&quot; (<span class="name">t</span>), the time at which the entity was completely created;</li>
+<li><span class="attribute" id="generation.time">time</span>: an <em class="rfc2119" title="optional">optional</em> "generation time" (<span class="name">t</span>), the time at which the entity was completely created;</li>
 
 <li><span class="attribute" id="generation.attributes">attributes</span>:  an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this generation.</li>
 </ul></div>
@@ -2187,8 +2148,8 @@
 <div class="anexample" id="anexample-generation1"><div class="anexampleTitle">Example 19<sup><a class="internalDFN" href="#anexample-generation1"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following expressions</p>
-<pre class="codeexample">  wasGeneratedBy(e1, a1, 2001-10-26T21:32:52, [ ex:port=&quot;p1&quot; ])
-  wasGeneratedBy(e2, a1, 2001-10-26T10:00:00, [ ex:port=&quot;p2&quot; ])
+<pre class="codeexample">  wasGeneratedBy(e1, a1, 2001-10-26T21:32:52, [ ex:port="p1" ])
+  wasGeneratedBy(e2, a1, 2001-10-26T10:00:00, [ ex:port="p2" ])
 </pre>
 <p>state the existence of two generations (with respective times <span class="name">2001-10-26T21:32:52</span> and <span class="name">2001-10-26T10:00:00</span>), at which new entities,  identified by <span class="name">e1</span> and <span class="name">e2</span>, were created by an
 activity,  identified by <span class="name">a1</span>.
@@ -2221,7 +2182,7 @@
 <li><span class="attribute" id="usage.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier for a usage;</li> 
 <li><span class="attribute" id="usage.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity that used an entity;</li>
 <li><span class="attribute" id="usage.entity">entity</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">e</span>) for the  entity being used;</li>
-<li><span class="attribute" id="usage.time">time</span>: an <em class="rfc2119" title="optional">optional</em> &quot;usage time&quot; (<span class="name">t</span>), the time at which the entity started to be used;</li>
+<li><span class="attribute" id="usage.time">time</span>: an <em class="rfc2119" title="optional">optional</em> "usage time" (<span class="name">t</span>), the time at which the entity started to be used;</li>
 <li><span class="attribute" id="usage.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this usage.</li>
 </ul></div>
 
@@ -2235,8 +2196,8 @@
 
 <div class="anexample" id="anexample-usage"><div class="anexampleTitle">Example 21<sup><a class="internalDFN" href="#anexample-usage"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following usages</p>
-<pre class="codeexample">  used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter=&quot;p1&quot; ])
-  used(a1, e2, 2011-11-16T16:00:01, [ ex:parameter=&quot;p2&quot; ])
+<pre class="codeexample">  used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter="p1" ])
+  used(a1, e2, 2011-11-16T16:00:01, [ ex:parameter="p2" ])
 </pre>
 <p>state that the activity identified by <span class="name">a1</span> used two entities identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">2011-11-16T16:00:00</span> and  <span class="name">2011-11-16T16:00:01</span>, respectively; the first
 one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>.  The semantics of <span class="name">parameter</span> is application specific.</p>
@@ -2276,8 +2237,8 @@
 <div class="anexample" id="anexample-communication"><div class="anexampleTitle">Example 22<sup><a class="internalDFN" href="#anexample-communication"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 Consider two activities  <span class="name">a1</span> and <span class="name">a2</span>, the former performed by a government agency, and the latter by a driver caught speeding. 
-</p><pre class="codeexample">activity(a1, [ prov:type=&quot;traffic regulations enforcing&quot; ])
-activity(a2, [ prov:type=&quot;fine paying&quot; ])
+</p><pre class="codeexample">activity(a1, [ prov:type="traffic regulations enforcing" ])
+activity(a2, [ prov:type="fine paying" ])
 wasInformedBy(a2, a1)
 </pre>
 The last line indicates that some implicit entity was generated by  <span class="name">a1</span> and used by  <span class="name">a2</span>; this entity may be a traffic ticket that had a notice of fine, amount, and payment mailing details.
@@ -2309,15 +2270,15 @@
 <div class="anexample" id="anexample-start1"><div class="anexampleTitle">Example 23<sup><a class="internalDFN" href="#anexample-start1"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following example contains the description of an activity <span class="name">a1</span> (a discussion), which was started at a specific time, and was triggered by an email message <span class="name">e1</span>.</p>
-<pre class="codeexample">entity(e1, [ prov:type=&quot;email message&quot;] )
-activity(a1, [ prov:type=&quot;Discuss&quot; ])
+<pre class="codeexample">entity(e1, [ prov:type="email message"] )
+activity(a1, [ prov:type="Discuss" ])
 wasStartedBy(a1, e1, -, 2011-11-16T16:05:00)
 </pre>
 Furthermore, if the message is also an input to the activity, this can be described as follows:
 <pre class="codeexample">used(a1, e1, -)
 </pre>
 <p>Alternatively, one can also describe the activity that generated the email message.</p>
-<pre class="codeexample">activity(a0, [ prov:type=&quot;Write&quot; ])
+<pre class="codeexample">activity(a0, [ prov:type="Write" ])
 wasGeneratedBy(e1, a0)
 wasStartedBy(a1, e1, a0, 2011-11-16T16:05:00)
 </pre>
@@ -2386,8 +2347,8 @@
 <div class="anexample" id="anexample-end"><div class="anexampleTitle">Example 26<sup><a class="internalDFN" href="#anexample-end"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following example is a description of an activity <span class="name">a1</span> (editing) that was ended following an approval document <span class="name">e1</span>.</p>
-<pre class="codeexample">entity(e1, [ prov:type=&quot;approval document&quot; ])
-activity(a1, [ prov:type=&quot;Editing&quot; ])
+<pre class="codeexample">entity(e1, [ prov:type="approval document" ])
+activity(a1, [ prov:type="Editing" ])
 wasEndedBy(a1, e1)
 </pre>
 </div>
@@ -2408,11 +2369,11 @@
 <ul>
 <li> an entity was destroyed: e.g. a painting was destroyed by fire; a Web page is taken out of a site;
 </li><li> an entity was consumed: e.g. Bob ate all his soup, Alice ran out of gas when driving to work;
-</li><li> an entity expires: e.g. a &quot;buy one beer, get one free&quot; offer is valid during happy hour (7-8pm);
+</li><li> an entity expires: e.g. a "buy one beer, get one free" offer is valid during happy hour (7-8pm);
 </li><li> an entity is time limited: e.g. the BBC news site on April 3rd, 2012;
 </li><li> an entity attribute is changing: e.g. the traffic light changed from green to red.
 </li></ul>
-<p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting.  In the third case, there may be an &quot;offer voucher&quot; that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the 
+<p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting.  In the third case, there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the 
 green traffic light (an entity with a fixed aspect green light) became the
 red traffic light (another entity with a fixed aspect red light).
 </p>
@@ -2426,7 +2387,7 @@
 <li><span class="attribute" id="invalidation.entity">entity</span>:  an identifier for the invalidated entity; </li>
 <li><span class="attribute" id="invalidation.activity">activity</span>:  an <em class="rfc2119" title="optional">optional</em> identifier for the activity that invalidated the entity;</li>
 
-<li><span class="attribute" id="invalidation.time">time</span>: an <em class="rfc2119" title="optional">optional</em> &quot;invalidation time&quot;, the time at which the entity began to be invalidated;</li>
+<li><span class="attribute" id="invalidation.time">time</span>: an <em class="rfc2119" title="optional">optional</em> "invalidation time", the time at which the entity began to be invalidated;</li>
 
 <li><span class="attribute" id="invalidation.attributes">attributes</span>:  an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs representing additional information about this invalidation.</li>
 </ul></div>
@@ -2442,7 +2403,7 @@
 agent(ex:Picasso)
 wasAttributedTo(ex:The-Painter, ex:Picasso)
 activity(ex:crash)
-wasInvalidatedBy(ex:The-Painter, ex:crash, 1998-09-03T01:31:00, [ ex:circumstances=&quot;plane accident&quot; ])
+wasInvalidatedBy(ex:The-Painter, ex:crash, 1998-09-03T01:31:00, [ ex:circumstances="plane accident" ])
 </pre>
 </div>
 
@@ -2466,7 +2427,7 @@
 
 <div class="anexample" id="anexample-invalidation3"><div class="anexampleTitle">Example 29<sup><a class="internalDFN" href="#anexample-invalidation3"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-In this example, the  &quot;buy one beer, get one free&quot; offer expired at the end of the happy hour.</p>
+In this example, the  "buy one beer, get one free" offer expired at the end of the happy hour.</p>
 <pre class="codeexample">entity(buy_one_beer_get_one_free_offer_during_happy_hour)
 wasAttributedTo(buy_one_beer_get_one_free_offer_during_happy_hour, proprietor)
 wasInvalidatedBy(buy_one_beer_get_one_free_offer_during_happy_hour,
@@ -2512,16 +2473,14 @@
 (<a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>) and binary association WasDerivedFrom
 (<a href="#concept-derivation" class="internalDFN">Derivation</a>). PROV extended structures are found outside this
 area. UML association classes express expanded n-ary relations.
-The subclasses are marked by the UML stereotype &quot;prov:type&quot; to indicate that the corresponding types are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
+The subclasses are marked by the UML stereotype "prov:type" to indicate that the corresponding types are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
 </p>
 
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-6-derivation-component-overview-informative" style="max-width: 95%; ">
-<img src="uml/component2.png" alt="derivation" /><br />
-<span class="figcaption" id="figure-component2">Figure 6<sup><a class="internalDFN" href="#figure-component2"><span class="diamond"> ◊:</span></a></sup> Derivation Component Overview (Informative)</span> 
-<!-- Figure 6 -->
-
+<img src="uml/component2.png" alt="derivation"><br>
+<span class="figcaption" id="figure-component2">Figure 6<sup><a class="internalDFN" href="#figure-component2"><span class="diamond"> ◊:</span></a></sup> Derivation Component Overview (Informative)</span> <!-- Figure 6 -->
 </span>
 </div>
 
@@ -2559,7 +2518,7 @@
 <div class="anexample" id="anexample-derivation"><div class="anexampleTitle">Example 30<sup><a class="internalDFN" href="#anexample-derivation"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following descriptions are about derivations between  <span class="name">e2</span> and  <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
 <pre class="codeexample">wasDerivedFrom(e2, e1)
-wasDerivedFrom(e2, e1, [ prov:type=&quot;physical transform&quot; ])
+wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
 </pre>
 <p>The following description expresses that activity  <span class="name">a</span>, 
 using the entity <span class="name">e1</span> according to usage <span class="name">u1</span>,
@@ -2611,9 +2570,7 @@
 
 
 
-</section>  
-<!-- end revision -->
-
+</section>  <!-- end revision -->
 
 <section id="term-quotation">
 <h4><span class="secno">5.2.3 </span>Quotation</h4>
@@ -2623,7 +2580,7 @@
 </p>
 
 <p>A <dfn id="dfn-quotation" class="internalDFN">quotation</dfn><sup><a class="internalDFN" href="#dfn-quotation"><span class="diamond"> ◊</span></a></sup> relation
- is a kind of  <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a> relation, for which an entity was derived from a preceding entity by copying, or &quot;quoting&quot;, some or all of it.
+ is a kind of  <a title="Derivation" href="#concept-derivation" class="internalDFN">derivation</a> relation, for which an entity was derived from a preceding entity by copying, or "quoting", some or all of it.
 The type of a quotation relation is denoted by:
 <dfn title="dfn-prov:quotation" id="dfn-prov:quotation" class="internalDFN"><span class="name">prov:Quotation</span></dfn><sup><a class="internalDFN" href="#dfn-prov:quotation"><span class="diamond"> ◊</span></a></sup>.
 PROV defines no quotation-specific attributes.
@@ -2635,7 +2592,7 @@
 <p>
 The following paragraph is a quote from one of  <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/">the author's blogs</a>.
 </p><blockquote id="bl-dagstuhl"><em>
-&quot;During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax.  This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection.&quot;</em>
+"During the workshop, it became clear to me that the consensus based models (which are often graphical in nature) can not only be formalized but also be directly connected to these database focused formalizations. I just needed to get over the differences in syntax.  This could imply that we could have nice way to trace provenance across systems and through databases and be able to understand the mathematical properties of this interconnection."</em>
 </blockquote>
 <p>If <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/"><span class="name">wp:thoughts-from-the-dagstuhl-principles-of-provenance-workshop/</span></a> denotes the original blog by agent <span class="name">ex:Paul</span>, and 
  <a href="#bl-dagstuhl"><span class="name">dm:bl-dagstuhl</span></a> denotes the above paragraph, then the following descriptions express that the above paragraph was copied by agent <span class="name">ex:Luc</span> from a part of the blog, attributed to the agent <span class="name">ex:Paul</span>.</p>
@@ -2653,9 +2610,7 @@
 </div>
 
 
-</section>  
-<!-- end quotation -->
-
+</section>  <!-- end quotation -->
 
 
 <section id="term-primary-source">
@@ -2667,7 +2622,7 @@
 
 <p>Because of the directness
 of <a href="http://en.wikipedia.org/wiki/Primary_source">primary
-sources</a>, they &quot;speak for themselves&quot; in ways that cannot be
+sources</a>, they "speak for themselves" in ways that cannot be
 captured through the filter of secondary sources. As such, it is
 important for secondary sources to reference those primary sources
 from which they were derived, so that their reliability can be
@@ -2695,8 +2650,8 @@
 to Napoleon's army during the Russian campaign. This primary source relation
 can be encoded as follows.</p>
 
-<pre class="codeexample">entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type=&quot;map&quot; ])
-entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type=&quot;journal&quot; ])
+<pre class="codeexample">entity(ex:la-campagne-de-Russie-1812-1813, [ prov:type="map" ])
+entity(ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII, [ prov:type="journal" ])
 wasDerivedFrom(ex:la-campagne-de-Russie-1812-1813,
                ex:revue-d-Histoire-de-la-Pharmacie-t-XVIII,
                [ prov:type='prov:PrimarySource' ])
@@ -2705,9 +2660,7 @@
 
 
 
-</section>  
-<!-- end primary source -->
-
+</section>  <!-- end primary source -->
 
 
 </section>
@@ -2717,16 +2670,14 @@
 
 <p>The third component of PROV-DM, depicted in  <a href="#figure-component3">Figure 7</a>, is concerned with <a title="Agent" href="#concept-agent" class="internalDFN">agents</a> and the relations WasAttributedTo
 (<a href="#concept-attribution" class="internalDFN">Attribution</a>), WasAssociatedWith (<a href="#concept-association" class="internalDFN">Association</a>), ActedOnBehalfOf (<a href="#concept-delegation" class="internalDFN">Delegation</a>), relating agents to entities, activities, and agents, respectively.
- Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">SofwareAgent</a>, and <a href="#concept-organization" class="internalDFN">Organization</a>. The subclasses are marked by the UML stereotype &quot;prov:type&quot; to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
+ Core structures are displayed in the yellow area and include three classes and three binary associations. Outside the yellow area, extended structures comprise UML association classes to express expanded n-ary relations, and subclasses <a href="#concept-plan" class="internalDFN">Plan</a>, <a href="#concept-person" class="internalDFN">Person</a>, <a title="software-agent" href="#concept-software-agent" class="internalDFN">SofwareAgent</a>, and <a href="#concept-organization" class="internalDFN">Organization</a>. The subclasses are marked by the UML stereotype "prov:type" to indicate that that these are valid values for the attribute <a href="#term-attribute-type">prov:type</a>.
 </p>
 
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-7-agents-and-responsibility-overview-informative" style="max-width: 95%; ">
-<img src="uml/component3.png" alt="agents and responsibilities" /><br />
-<span class="figcaption" id="figure-component3">Figure 7<sup><a class="internalDFN" href="#figure-component3"><span class="diamond"> ◊:</span></a></sup> Agents and Responsibility Overview (Informative)</span> 
-<!-- Figure 7 -->
-
+<img src="uml/component3.png" alt="agents and responsibilities"><br>
+<span class="figcaption" id="figure-component3">Figure 7<sup><a class="internalDFN" href="#figure-component3"><span class="diamond"> ◊:</span></a></sup> Agents and Responsibility Overview (Informative)</span> <!-- Figure 7 -->
 </span>
 </div>
 
@@ -2735,10 +2686,8 @@
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-8-influence-overview-informative" style="max-width: 95%; ">
-<img src="uml/Component3b.png" alt="Influence Overview" /><br />
-<span class="figcaption" id="figure-component3b">Figure 8<sup><a class="internalDFN" href="#figure-component3b"><span class="diamond"> ◊:</span></a></sup> Influence Overview (Informative)</span> 
-<!-- Figure 8 -->
-
+<img src="uml/Component3b.png" alt="Influence Overview"><br>
+<span class="figcaption" id="figure-component3b">Figure 8<sup><a class="internalDFN" href="#figure-component3b"><span class="diamond"> ◊:</span></a></sup> Influence Overview (Informative)</span> <!-- Figure 8 -->
 </span>
 </div>
 
@@ -2788,7 +2737,7 @@
 
 <div class="anexample" id="example_34"><div class="anexampleTitle">Example 34<sup><a class="internalDFN" href="#example_34"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following expression is about an agent identified by <span class="name">e1</span>, which is a person, named Alice, with employee number 1234.</p>
-<pre class="codeexample">agent(e1, [ex:employee=&quot;1234&quot;, ex:name=&quot;Alice&quot;, prov:type='prov:Person' ])
+<pre class="codeexample">agent(e1, [ex:employee="1234", ex:name="Alice", prov:type='prov:Person' ])
 </pre>
 <p>It is optional to specify the type of an agent. When present, it is expressed using the <span class="name">prov:type</span> attribute.</p>
 </div>
@@ -2819,14 +2768,12 @@
 </p><pre class="codeexample">agent(ex:Paolo, [ prov:type='prov:Person' ])
 agent(ex:Simon, [ prov:type='prov:Person' ])
 entity(tr:WD-prov-dm-20111215, [ prov:type='rec54:WD' ])
-wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [ prov:type=&quot;editorship&quot; ])
-wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [ prov:type=&quot;authorship&quot; ])
+wasAttributedTo(tr:WD-prov-dm-20111215, ex:Paolo, [ prov:type="editorship" ])
+wasAttributedTo(tr:WD-prov-dm-20111215, ex:Simon, [ prov:type="authorship" ])
 </pre>
 </div>
 
-</section>  
-<!-- end attribution -->
-
+</section>  <!-- end attribution -->
 
 
 <section id="term-Association">
@@ -2861,14 +2808,14 @@
 
 <div class="anexample" id="anexample-wasAssociatedWith"><div class="anexampleTitle">Example 36<sup><a class="internalDFN" href="#anexample-wasAssociatedWith"><span class="diamond"> ◊</span></a></sup></div>
 <p>In the following example, a designer agent and an operator agent are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an entity of type <span class="name"><a title="dfn-prov:plan" href="#dfn-prov:plan" class="internalDFN">plan</a></span>.   </p>
-<pre class="codeexample">activity(ex:a, [ prov:type=&quot;workflow execution&quot; ])
-agent(ex:ag1,  [ prov:type=&quot;operator&quot; ])
-agent(ex:ag2,  [ prov:type=&quot;designer&quot; ])
-wasAssociatedWith(ex:a, ex:ag1, -,     [ prov:role=&quot;loggedInUser&quot;, ex:how=&quot;webapp&quot; ])
-wasAssociatedWith(ex:a, ex:ag2, ex:wf, [ prov:role=&quot;designer&quot;, ex:context=&quot;project1&quot; ])
+<pre class="codeexample">activity(ex:a, [ prov:type="workflow execution" ])
+agent(ex:ag1,  [ prov:type="operator" ])
+agent(ex:ag2,  [ prov:type="designer" ])
+wasAssociatedWith(ex:a, ex:ag1, -,     [ prov:role="loggedInUser", ex:how="webapp" ])
+wasAssociatedWith(ex:a, ex:ag2, ex:wf, [ prov:role="designer", ex:context="project1" ])
 entity(ex:wf, [ prov:type='prov:Plan' , 
-                ex:label=&quot;Workflow 1&quot;, 
-                prov:location=&quot;http://example.org/workflow1.bpel&quot; %% xsd:anyURI ])
+                ex:label="Workflow 1", 
+                prov:location="http://example.org/workflow1.bpel" %% xsd:anyURI ])
 </pre>
 Since the workflow <span class="name">ex:wf</span> is itself an entity, its provenance can also be expressed in PROV: it can be generated by some activity and derived from other entities,
 for instance.
@@ -2876,11 +2823,11 @@
 
 <div class="anexample" id="anexample-wasAssociatedWith-2"><div class="anexampleTitle">Example 37<sup><a class="internalDFN" href="#anexample-wasAssociatedWith-2"><span class="diamond"> ◊</span></a></sup></div>
 <p>In some cases, one wants to indicate a plan was followed, without having to specify which agent was involved.</p>
-<pre class="codeexample">activity(ex:a, [ prov:type=&quot;workflow execution&quot; ])
+<pre class="codeexample">activity(ex:a, [ prov:type="workflow execution" ])
 wasAssociatedWith(ex:a, -, ex:wf)
 entity(ex:wf, [ prov:type='prov:Plan', 
-                ex:label=&quot;Workflow 1&quot;, 
-                ex:url=&quot;http://example.org/workflow1.bpel&quot; %% xsd:anyURI])
+                ex:label="Workflow 1", 
+                ex:url="http://example.org/workflow1.bpel" %% xsd:anyURI])
 </pre>
 In this case, it is assumed that an agent exists, but it has not been specified.
 </div>
@@ -2888,9 +2835,7 @@
 
 
 
-</section>  
-<!-- end wasAssociatedWith -->
-
+</section>  <!-- end wasAssociatedWith -->
 
 <section id="term-delegation">
 
@@ -2923,20 +2868,19 @@
 <p>The following fragment describes three agents: a programmer, a researcher, and a funder.  The programmer and researcher are associated with a workflow activity.  The programmer acts on behalf
 of the researcher (line-management) encoding the commands specified by the researcher; the researcher acts on behalf of the funder, who has a contractual agreement with the researcher. The terms
 'line-management' and 'contract' used in this example are domain specific.</p>
-<pre class="codeexample">activity(a,[ prov:type=&quot;workflow&quot; ])
-agent(ag1, [ prov:type=&quot;programmer&quot; ])
-agent(ag2, [ prov:type=&quot;researcher&quot; ])
-agent(ag3, [ prov:type=&quot;funder&quot; ])
-wasAssociatedWith(a, ag1, [ prov:role=&quot;loggedInUser&quot; ])
+<pre class="codeexample">activity(a,[ prov:type="workflow" ])
+agent(ag1, [ prov:type="programmer" ])
+agent(ag2, [ prov:type="researcher" ])
+agent(ag3, [ prov:type="funder" ])
+wasAssociatedWith(a, ag1, [ prov:role="loggedInUser" ])
 wasAssociatedWith(a, ag2)
 wasAssociatedWith(a, ag3)
-actedOnBehalfOf(ag1, ag2, a, [ prov:type=&quot;line-management&quot; ])
-actedOnBehalfOf(ag2, ag3, a, [ prov:type=&quot;contract&quot; ])
+actedOnBehalfOf(ag1, ag2, a, [ prov:type="line-management" ])
+actedOnBehalfOf(ag2, ag3, a, [ prov:type="contract" ])
 </pre>
 </div>
 
 
-
 <!-- too strong, move to part 2.
 <p>Further considerations:</p>
 <ul>
@@ -2945,7 +2889,6 @@
 </li>
 </ul>
 -->
-
 </section>
 
 <section id="term-influence">
@@ -2981,9 +2924,7 @@
 <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-start" class="internalDFN">Start</a>, <a href="#concept-end" class="internalDFN">End</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-communication" class="internalDFN">Communication</a>, <a href="#concept-derivation" class="internalDFN">Derivation</a>, <a href="#concept-attribution" class="internalDFN">Attribution</a>, <a href="#concept-association" class="internalDFN">Association</a>, and <a href="#concept-delegation" class="internalDFN">Delegation</a>.
 
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="mapping-relations-to-influence-table"><span>Table 7<sup><a class="internalDFN" href="#mapping-relations-to-influence-table"><span class="diamond"> ◊:</span></a></sup> </span>Mapping Relations to Influence</caption> 
-<!-- Table 7-->
-
+<caption id="mapping-relations-to-influence-table"><span>Table 7<sup><a class="internalDFN" href="#mapping-relations-to-influence-table"><span class="diamond"> ◊:</span></a></sup> </span>Mapping Relations to Influence</caption> <!-- Table 7-->
 <tbody><tr><td><b>Relation Name</b></td><td><b><a class="attribute" href="#influence.influencee">influencee</a></b></td><td><b><a class="attribute" href="#influence.influencer">influencer</a></b></td></tr>
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 
@@ -3041,7 +2982,7 @@
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-9-bundle-component-overview-informative" style="max-width: 95%; ">
 
-<img src="uml/component4.png" alt="bundles" /><br />
+<img src="uml/component4.png" alt="bundles"><br>
 <span class="figcaption" id="figure-component4">Figure 9<sup><a class="internalDFN" href="#figure-component4"><span class="diamond"> ◊:</span></a></sup> Bundle Component Overview (Informative)</span>
 </span>
 </div>
@@ -3108,9 +3049,9 @@
 <div class="anexample" id="anexample-provenance-of-provenance"><div class="anexampleTitle">Example 40<sup><a class="internalDFN" href="#anexample-provenance-of-provenance"><span class="diamond"> ◊</span></a></sup></div>
 <p>Let us consider two entities <span class="name">ex:report1</span> and <span class="name">ex:report2</span>.</p>
 <pre class="codeexample"> 
-entity(ex:report1, [ prov:type=&quot;report&quot;, ex:version=1 ])
+entity(ex:report1, [ prov:type="report", ex:version=1 ])
 wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
-entity(ex:report2, [ prov:type=&quot;report&quot;, ex:version=2])
+entity(ex:report2, [ prov:type="report", ex:version=2])
 wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
 wasDerivedFrom(ex:report2, ex:report1)
 </pre>
@@ -3119,7 +3060,7 @@
 A first bundle can be expressed.</p>
 <pre class="codeexample"> 
 bundle bob:bundle1
-  entity(ex:report1, [ prov:type=&quot;report&quot;, ex:version=1 ])
+  entity(ex:report1, [ prov:type="report", ex:version=1 ])
   wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
 endBundle
 </pre>
@@ -3130,7 +3071,7 @@
 <pre class="codeexample"> 
 bundle alice:bundle2
   entity(ex:report1)
-  entity(ex:report2, [ prov:type=&quot;report&quot;, ex:version=2 ])
+  entity(ex:report2, [ prov:type="report", ex:version=2 ])
   wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
@@ -3156,10 +3097,10 @@
 <p>A provenance aggregator could merge two bundles, resulting in a novel bundle, whose provenance is described as follows.</p>
 <pre class="codeexample"> 
 bundle agg:bundle3
-  entity(ex:report1, [ prov:type=&quot;report&quot;, ex:version=1 ])
+  entity(ex:report1, [ prov:type="report", ex:version=1 ])
   wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
 
-  entity(ex:report2, [ prov:type=&quot;report&quot;, ex:version=2 ])
+  entity(ex:report2, [ prov:type="report", ex:version=2 ])
   wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
@@ -3193,7 +3134,7 @@
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-10-alternates-component-overview-informative" style="max-width: 95%; ">
-<img src="uml/component5.png" alt="alternates" /><br />
+<img src="uml/component5.png" alt="alternates"><br>
 <span class="figcaption" id="figure-component5">Figure 10<sup><a class="internalDFN" href="#figure-component5"><span class="diamond"> ◊:</span></a></sup> Alternates Component Overview (Informative)</span>
 </span>
 </div>
@@ -3290,9 +3231,9 @@
 is an alternate of a 
  <a href="http://www.bbc.co.uk/news/mobile/science-environment-17526723">bbc:news/mobile/science-environment-17526723</a> for mobile devices.</p>
 <pre class="codeexample">entity(bbc:news/science-environment-17526723, 
-       [ prov:type=&quot;a news item for desktop&quot;])
+       [ prov:type="a news item for desktop"])
 entity(bbc:news/mobile/science-environment-17526723, 
-       [ prov:type=&quot;a news item for mobile devices&quot;])
+       [ prov:type="a news item for mobile devices"])
 alternateOf(bbc:news/science-environment-17526723, 
             bbc:news/mobile/science-environment-17526723)
 </pre>
@@ -3327,7 +3268,7 @@
 
 <div style="text-align: center;">
 <span class="figure" id="fig-figure-11-collections-component-overview-informative" style="max-width: 95%; ">
-<img src="uml/component6.png" alt="collection" /><br />
+<img src="uml/component6.png" alt="collection"><br>
 <span class="figcaption" id="figure-component6">Figure 11<sup><a class="internalDFN" href="#figure-component6"><span class="diamond"> ◊:</span></a></sup> Collections Component Overview (Informative)</span>
 </span>
 </div>
@@ -3399,9 +3340,7 @@
 
 
   
-</section>   
-<!-- end collections-->
-
+</section>   <!-- end collections-->
 
 
 
@@ -3440,9 +3379,7 @@
 
 <div id="attributes-at-a-glance-divz" style="text-align: left;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="attributes-at-a-glance"><span>Table 8<sup><a class="internalDFN" href="#attributes-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Attributes At a Glance</caption> 
-<!-- Table 8 -->
-
+<caption id="attributes-at-a-glance"><span>Table 8<sup><a class="internalDFN" href="#attributes-at-a-glance"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Attributes At a Glance</caption> <!-- Table 8 -->
 <tbody><tr><td><b>Attribute</b></td><td><b>Allowed In</b></td><td><b>value</b></td><td><b>Section</b></td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 <tr><td><a title="label" href="#concept-label" class="internalDFN">prov:label</a></td><td><em>any construct</em></td><td>A <a title="value" href="#concept-value" class="internalDFN">Value</a> of type <a class="section-ref" href="http://www.w3.org/TR/xmlschema11-2/#string">xsd:string</a></td><td><a class="section-ref" href="#term-attribute-label"><span>Section 5.7.2.1</span></a> </td></tr>
@@ -3467,11 +3404,11 @@
 
 <div class="anexample" id="example_48"><div class="anexampleTitle">Example 48<sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following entity is provided with a label attribute.</p>
-<pre class="codeexample"> entity(ex:e1, [ prov:label=&quot;This is a human-readable label&quot; ])
+<pre class="codeexample"> entity(ex:e1, [ prov:label="This is a human-readable label" ])
 </pre>
 
 <p>The following entity has two label attributes, in French and English.</p>
-<pre class="codeexample"> entity(ex:car01, [ prov:label=&quot;Voiture 01&quot;@fr, prov:label=&quot;Car 01&quot;@en ])
+<pre class="codeexample"> entity(ex:car01, [ prov:label="Voiture 01"@fr, prov:label="Car 01"@en ])
 </pre>
 </div>
 </section>
@@ -3493,10 +3430,10 @@
 
 <div class="anexample" id="example-location"><div class="anexampleTitle">Example 49<sup><a class="internalDFN" href="#example-location"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following expression describes entity Mona Lisa, a painting, with a location attribute. </p>
-<pre class="codeexample"> entity(ex:MonaLisa, [ prov:location=&quot;Le Louvre, Paris&quot;, prov:type=&quot;StillImage&quot; ])
+<pre class="codeexample"> entity(ex:MonaLisa, [ prov:location="Le Louvre, Paris", prov:type="StillImage" ])
 </pre>
 <p>The following expression describes a cell, at coordinates (5,5), with value 10. </p>
-<pre class="codeexample"> entity(ex:cell, [ prov:location=&quot;(5,5)&quot;, prov:value=&quot;10&quot; %% xsd:integer ])
+<pre class="codeexample"> entity(ex:cell, [ prov:location="(5,5)", prov:value="10" %% xsd:integer ])
 </pre>
 </div>
 </section>
@@ -3514,10 +3451,10 @@
 
 <div class="anexample" id="anexample-role"><div class="anexampleTitle">Example 50<sup><a class="internalDFN" href="#anexample-role"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following activity is associated with an agent acting as the operator. </p>
-<pre class="codeexample"> wasAssociatedWith(a, ag, [ prov:role=&quot;operator&quot; ])
+<pre class="codeexample"> wasAssociatedWith(a, ag, [ prov:role="operator" ])
 </pre>
 <p>In the following expression, the activity <span class="name">ex:div01</span> used entity <span class="name">ex:cell</span> in the role of divisor.</p>
-<pre class="codeexample">used(ex:div01, ex:cell, [ prov:role=&quot;divisor&quot; ])
+<pre class="codeexample">used(ex:div01, ex:cell, [ prov:role="divisor" ])
 </pre>
 </div>
 </section>
@@ -3543,9 +3480,7 @@
 
 
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-predefined-types"><span>Table 9<sup><a class="internalDFN" href="#prov-dm-predefined-types"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Predefined Types</caption> 
-<!-- Table 9 -->
-
+<caption id="prov-dm-predefined-types"><span>Table 9<sup><a class="internalDFN" href="#prov-dm-predefined-types"><span class="diamond"> ◊:</span></a></sup> </span>PROV-DM Predefined Types</caption> <!-- Table 9 -->
 <tbody><tr><td><b>Type</b></td><td><b>Specification</b></td><td><b>Core concept</b></td></tr>
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 <tr><td><a title="dfn-prov:bundle" href="#dfn-prov:bundle" class="internalDFN"><span class="name">prov:Bundle</span></a></td><td><a class="section-ref" href="#term-bundle"><span>Section 5.4.1</span></a></td><td><a href="#concept-entity" class="internalDFN">Entity</a></td></tr>
@@ -3573,12 +3508,12 @@
 <p>The attribute <span class="name">prov:value</span> is an <em class="rfc2119" title="optional">optional</em> attribute of entity.  The value associated with the  attribute <span class="name">prov:value</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <em class="rfc2119" title="may">may</em> occur at most once in a set of attribute-value pairs.</p>
 
 <div class="anexample" id="anexample-value1"><div class="anexampleTitle">Example 52<sup><a class="internalDFN" href="#anexample-value1"><span class="diamond"> ◊</span></a></sup></div>
-<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">&quot;abcd&quot;</span>.
+<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
 The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
 </p>
-<pre class="codeexample">entity(ex:in, [ prov:value=&quot;abcd&quot; ]) 
+<pre class="codeexample">entity(ex:in, [ prov:value="abcd" ]) 
 entity(ex:out, [ prov:value=4 ]) 
-activity(ex:len, [ prov:type=&quot;string-length&quot; ])
+activity(ex:len, [ prov:type="string-length" ])
 used(ex:len, ex:in)
 wasGeneratedBy(ex:out, ex:len)
 wasDerivedFrom(ex:out, ex:in)
@@ -3599,7 +3534,7 @@
 <pre class="codeexample">entity(ex:in1, [ prov:value=3 ]) 
 entity(ex:in2, [ prov:value=1 ]) 
 entity(ex:out2, [ prov:value=4 ])      // ex:out2 also has value 4
-activity(ex:add1, [ prov:type=&quot;addition&quot; ])
+activity(ex:add1, [ prov:type="addition" ])
 used(ex:add1, ex:in1)
 used(ex:add1, ex:in2)
 wasGeneratedBy(ex:out2, ex:add1)
@@ -3643,7 +3578,7 @@
 <li>otherwise, the feature is optional in PROV and the reference is informative only.</li>
 </ul>
 </li></ul>
-<p>This &quot;change in normative reference&quot; is effective as of the publication of RDF 1.1 as a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. However, <abbr title="World Wide Web Consortium">W3C</abbr> expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</p>
+<p>This "change in normative reference" is effective as of the publication of RDF 1.1 as a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. However, <abbr title="World Wide Web Consortium">W3C</abbr> expects to publish a new edition of PROV once RDF 1.1 becomes a Recommendation to update the reference explicitly.</p>
 
 
 
@@ -3652,16 +3587,16 @@
 
 <div class="anexample" id="anexample-value"><div class="anexampleTitle">Example 54<sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-The following examples respectively are the string &quot;abc&quot;, the integer number 1, and the IRI &quot;http://example.org/foo&quot;.
-</p><pre class="codeexample">  &quot;abc&quot;
-  &quot;1&quot; %% xsd:integer
-  &quot;http://example.org/foo&quot; %% xsd:anyURI
+The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
+</p><pre class="codeexample">  "abc"
+  "1" %% xsd:integer
+  "http://example.org/foo" %% xsd:anyURI
 </pre>
 <p>The following example shows a value of type <span class="name">prov:QUALIFIED_NAME</span> (see
 <span class="name"><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></span> [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>]).
 The prefix <span class="name">ex</span>  must be bound to a <a href="#dfn-namespace" class="internalDFN">namespace</a> declared in a <a href="#dfn-namespaceDeclaration" class="internalDFN">namespace declaration</a>.</p>
 <pre class="codeexample"> 
-  &quot;ex:value&quot; %% prov:QUALIFIED_NAME
+  "ex:value" %% prov:QUALIFIED_NAME
 </pre>
 Alternatively, the same value can be expressed using the following convenience notation.
 <pre class="codeexample"> 
@@ -3721,14 +3656,10 @@
 </section>
 
 
-
 <!-- end sec. 5 -->
 
-
     <section id="extensibility-section"> 
-
-<!--OddPage-->
-<h2><span class="secno">6. </span>PROV-DM Extensibility Points</h2>
+<!--OddPage--><h2><span class="secno">6. </span>PROV-DM Extensibility Points</h2>
 
 
 <p>The PROV data model provides extensibility points that allow designers to specialize it for specific applications or domains. We summarize these extensibility points here. </p>
@@ -3772,8 +3703,8 @@
   activity(ex:work)
   entity(ex:laptop4)
   entity(ex:desktop9)
-  used(ex:work, ex:laptop4,  [prov:role=&quot;day-to-day machine&quot;])
-  used(ex:work, ex:desktop9, [prov:role=&quot;backup machine&quot;])
+  used(ex:work, ex:laptop4,  [prov:role="day-to-day machine"])
+  used(ex:work, ex:desktop9, [prov:role="backup machine"])
 </pre>
 </div>
 </li>
@@ -3797,9 +3728,7 @@
 
 
 <section id="valid-provenance">
-
-<!--OddPage-->
-<h2><span class="secno">7. </span>Creating Valid Provenance</h2>
+<!--OddPage--><h2><span class="secno">7. </span>Creating Valid Provenance</h2>
 
 <p>This specification defines PROV-DM, a data model that allows 
 descriptions of the people, institutions, entities, and activities,
@@ -3818,7 +3747,7 @@
 
 <p> The example of <a href="#prov-dm-example">section 3</a> contains identifiers such as <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span>, which denotes a specific version of a technical report.  On the other hand, an IRI such as <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a> denotes the latest version of a document. One needs to ensure that provenance descriptions for the latter resource remain valid as the resource state changes. </p>
 
-<p>To this end, PROV allows asserters to describe &quot;<em>partial states</em>&quot; of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
+<p>To this end, PROV allows asserters to describe "<em>partial states</em>" of entities by means of attributes and associated values. Some further constraints apply to the use of these attributes, since the values associated with them are expected to remain unchanged for some period of time. The constraints associated to attributes allow provenance descriptions to be refined, they can also be found in the companion specification [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>].</p>
 
 
 
@@ -3827,18 +3756,14 @@
 
 
 <section class="appendix" id="cross-references-to-prov-o-and-prov-n">
-
-<!--OddPage-->
-<h2><span class="secno">A. </span>Cross-References to PROV-O and PROV-N</h2>
+<!--OddPage--><h2><span class="secno">A. </span>Cross-References to PROV-O and PROV-N</h2>
 
 <p>PROV-DM is a conceptual data model which can be serialized in various ways. 
 The following table contains the PROV-O classes and properties, as described in [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], and PROV-N productions, as described in [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] that correspond to PROV-DM concepts.</p> 
 
 <div id="prov-dm-to-prov-o-and-prov-n-fig" style="text-align: left;">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
-<caption id="prov-dm-to-prov-o-and-prov-n"><span>Table 10<sup><a class="internalDFN" href="#prov-dm-to-prov-o-and-prov-n"><span class="diamond"> ◊:</span></a></sup> </span>Cross-References to PROV-O and PROV-N</caption> 
-<!-- Table 10-->
-
+<caption id="prov-dm-to-prov-o-and-prov-n"><span>Table 10<sup><a class="internalDFN" href="#prov-dm-to-prov-o-and-prov-n"><span class="diamond"> ◊:</span></a></sup> </span>Cross-References to PROV-O and PROV-N</caption> <!-- Table 10-->
 <tbody><tr><td><b>PROV-DM</b></td><td><b>PROV-O</b></td><td><b>PROV-N</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><td style="border-width: 0px; "></td></tr>
 
@@ -3846,7 +3771,7 @@
 <td><a title="Entity" href="#concept-entity" class="internalDFN">Entity</a></td>
 <td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Entity">Entity</a></td>
 <td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-entityExpression">entityExpression</a></code>
-</td><td rowspan="8"><a href="#component1">Component 1:<br /> Entities/Activities</a></td></tr>
+</td><td rowspan="8"><a href="#component1">Component 1:<br> Entities/Activities</a></td></tr>
 
 <tr class="component1-color">
 <td><a title="Activity" href="#concept-activity" class="internalDFN">Activity</a></td>
@@ -3898,7 +3823,7 @@
 <td><a title="Derivation" href="#concept-derivation" class="internalDFN">Derivation</a></td>
 <td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#wasDerivedFrom">wasDerivedFrom</a>, <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Derivation">Derivation</a></td>
 <td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-derivationExpression">derivationExpression</a></code></td>
-<td rowspan="4"><a href="#component2">Component 2:<br /> Derivations</a></td>
+<td rowspan="4"><a href="#component2">Component 2:<br> Derivations</a></td>
 </tr>
 
 <tr class="component2-color">
@@ -3926,7 +3851,7 @@
 <td><a title="Agent" href="#concept-agent" class="internalDFN">Agent</a></td>
 <td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Agent">Agent</a></td>
 <td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-agentExpression">agentExpression</a></code></td>
-<td rowspan="9"><a href="#component3">Component 3: <br />Agents, Responsibility, <br />Influence</a></td>
+<td rowspan="9"><a href="#component3">Component 3: <br>Agents, Responsibility, <br>Influence</a></td>
 </tr>
 
 <tr class="component3-color">
@@ -3986,7 +3911,7 @@
 <td><a title="Bundle" href="#concept-bundle" class="internalDFN">Bundle constructor</a></td>
 <td> <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#description-bundle">bundle description</a> </td>
 <td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-bundle">bundle</a></code></td>
-<td rowspan="2"><a href="#component5">Component 4: <br /> Bundles</a></td>
+<td rowspan="2"><a href="#component5">Component 4: <br> Bundles</a></td>
 </tr>
 
 <tr class="component4-color"><td class="provType"><a title="Bundle Type" href="#dfn-bundle-type" class="internalDFN">Bundle type</a></td>
@@ -4001,7 +3926,7 @@
 <td><a title="Alternate" href="#concept-alternate" class="internalDFN">Alternate</a></td>
 <td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#alternateOf">alternateOf</a></td>
 <td><code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#prod-alternateExpression">alternateExpression</a></code></td>
-<td rowspan="2"><a href="#component4">Component 5: <br /> Alternate</a></td>
+<td rowspan="2"><a href="#component4">Component 5: <br> Alternate</a></td>
 </tr>
 
 <tr class="component5-color">
@@ -4017,7 +3942,7 @@
 <td><a title="Collection" href="#concept-collection" class="internalDFN">Collection</a></td>
 <td><a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Collection">Collection</a></td>
 <td>type <code><a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/#provn-type-Collection">Collection</a></code></td>
-<td rowspan="3"><a href="#component6">Component 6: <br /> Collections</a></td>
+<td rowspan="3"><a href="#component6">Component 6: <br> Collections</a></td>
 </tr>
 
 <tr class="component6-color">
@@ -4036,9 +3961,7 @@
 </section>
 
 <section class="appendix" id="change-log"> 
-      
-<!--OddPage-->
-<h2><span class="secno">B. </span>Change Log</h2> 
+      <!--OddPage--><h2><span class="secno">B. </span>Change Log</h2> 
 
 <section id="changes-since-last-version">
       <h3><span class="secno">B.1 </span>Changes since last version</h3> 
@@ -4064,21 +3987,21 @@
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/508">ISSUE-508</a>: Clarified the bold names and parameters  in  text preceding <a href="#prov-dm-types-and-relations-fig">Table 5</a>.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/501">ISSUE-501</a>: Put the example about driving a car to Boston in a box.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/450">ISSUE-450</a>, <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added table with secondary objects in relations.
-</li><li> <a href="http://www.w3.org/2011/prov/track/issues/512">ISSUE-512</a>: simplied type of activity a2 to &quot;fine paying&quot;
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/512">ISSUE-512</a>: simplied type of activity a2 to "fine paying"
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/509">ISSUE-509</a>: modified the introductory text to UML figures, so that they refer to relation names (e.g. WasStartedBy) as visualized in figures
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/515">ISSUE-515</a>: fixed typo
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/531">ISSUE-531</a>: added sentence on the use of prov:location attribute.
 
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/519">ISSUE-519</a>, <a href="http://www.w3.org/2011/prov/track/issues/523">ISSUE-523</a>, <a href="http://www.w3.org/2011/prov/track/issues/524">ISSUE-524</a>, <a href="http://www.w3.org/2011/prov/track/issues/529">ISSUE-529</a>: changed UML diagram of figure 8 by removing explicit inheritance from influence for  usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation.  Instead, introduced correspondance table 7.  Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: made explicit which section, figure, table was informative or normative.
-</li><li> <a href="http://www.w3.org/2011/prov/track/issues/521">ISSUE-521</a>: now states that &quot;an agent relied on a plan&quot; instead of &quot;an agent adopted a plan&quot;.
+</li><li> <a href="http://www.w3.org/2011/prov/track/issues/521">ISSUE-521</a>: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/499">ISSUE-499</a>: Made explicit that generation/usage/invalidation/start/end are implicit.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/449">ISSUE-449</a>: Clarified definition of prov:value attribute and added an example.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/516">ISSUE-516</a>: Stating that there moust be some underpinning activity or activities for a derivation, instead of just activities.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/525">ISSUE-525</a>: Made it explicit that Membership, Alternate, Specialization are not Influence
-</li><li> Copied the sentence &quot; An agent may be a particular type of entity or activity. This means that the model can be
- used to express provenance of the agents themselves.  &quot; from the informative section into the normative section.
+</li><li> Copied the sentence " An agent may be a particular type of entity or activity. This means that the model can be
+ used to express provenance of the agents themselves.  " from the informative section into the normative section.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/504">ISSUE-504</a>: Updated definition of collection.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/503">ISSUE-503</a>: Rephrased the introduction of expanded association in section 2.2.1.2 Expanded Relations.
 </li><li> <a href="http://www.w3.org/2011/prov/track/issues/514">ISSUE-514</a>: added links to the attributes listed in the secondary element table. Also removed PrimarySource, Quotation, Revision.
@@ -4096,9 +4019,7 @@
 </section>
 
 <section class="appendix" id="acknowledgements"> 
-      
-<!--OddPage-->
-<h2><span class="secno">C. </span>Acknowledgements</h2> 
+      <!--OddPage--><h2><span class="secno">C. </span>Acknowledgements</h2> 
       <p> 
 
 This  document has been produced by the Provenance Working Group, and its contents reflect extensive discussion within the Working Group as a whole. The editors extend special thanks to  Sandro Hawke (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="Massachusetts Institute of Technology">MIT</abbr>) and Ivan Herman (<abbr title="World Wide Web Consortium">W3C</abbr>/<abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>), <abbr title="World Wide Web Consortium">W3C</abbr> contacts for the Provenance Working Group.
@@ -4186,9 +4107,7 @@
 
  
 
-<section id="references" class="appendix">
-<!--OddPage-->
-<h2><span class="secno">D. </span>References</h2><section id="normative-references"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><cite>Constraints of the PROV Data Model</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</a>
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">D. </span>References</h2><section id="normative-references"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/"><cite>Constraints of the PROV Data Model</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</a>
 </dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/"><cite>PROV-N: The Provenance Notation</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-n-20130312/">http://www.w3.org/TR/2013/PR-prov-n-20130312/</a>
 </dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/"><cite>PROV-O: The PROV Ontology</cite></a>. 12 March 2013, W3C Proposed Recommendation. URL: <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/">http://www.w3.org/TR/2013/PR-prov-o-20130312/</a>
 </dd><dt id="bib-RDF-CONCEPTS">[RDF-CONCEPTS]</dt><dd>Graham Klyne; Jeremy J. Carroll. <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210"><cite>Resource Description Framework (RDF): Concepts and Abstract Syntax</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-concepts-20040210">http://www.w3.org/TR/2004/REC-rdf-concepts-20040210</a>
@@ -4207,4 +4126,4 @@
 </dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 12 March 2013, Working Draft. URL: <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</a>
 </dd><dt id="bib-RDF-CONCEPTS11">[RDF-CONCEPTS11]</dt><dd>Richard Cyganiak; David Wood; eds. <a href="http://www.w3.org/TR/rdf11-concepts/"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. Working Draft. URL: <a href="http://www.w3.org/TR/rdf11-concepts/">http://www.w3.org/TR/rdf11-concepts/</a>
 </dd><dt id="bib-UML">[UML]</dt><dd>Object Management Group <a href="http://www.omg.org/spec/UML/2.0/Superstructure/PDF/"><cite>Unified Modeling Language: Superstructure</cite></a>. version 2.0, 2005 URL: <a href="http://www.omg.org/spec/UML/2.0/Superstructure/PDF/">http://www.omg.org/spec/UML/2.0/Superstructure/PDF/</a>
-</dd></dl></section></section></body></html>
+</dd></dl></section></section></body></html>
\ No newline at end of file
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/model/respec2xhtml.js	Thu Feb 21 00:03:34 2013 +0000
@@ -0,0 +1,56 @@
+// respec2html is a command line utility that converts a ReSpec source file to an HTML file.
+// Depends on PhantomJS <http://phantomjs.org>.
+
+var page = require('webpage').create(),
+    args = require('system').args,
+    fs = require('fs'),
+    source = args[1],
+    output = args[2],
+    timeout = (!isNaN(args[3])) ? parseInt(args[3], 10) : 10;
+
+if (args.length !== 3 && args.length !== 4) {
+    console.log('Usage:\n   phantomjs respec2html.js respec-source html-output [timeout]\n');
+    console.log('   respec-source  ReSpec source file, or an URL to the file');
+    console.log('   html-output    Name for the HTML file to be generated');
+    console.log('   [timeout]      An optional timeout in seconds, default is 10\n');
+    phantom.exit();
+}
+
+page.open(source, function(status) {
+    page.onResourceRequested = function(request) {
+        console.log('Loading ' + request.url);
+    };
+    
+    if (status !== 'success') {
+        console.log('Unable to access ReSpec source file.');
+        phantom.exit();
+    } else {
+        console.log('Loading ' + source);
+        var timer = setInterval(function() {
+            // Poll document.respecDone for doneness. A proper way would be to listen
+            // for the end-all message on respecEvents (unsupported by PhantomJS).
+            var done = page.evaluate(function() { return (document.respecDone) ? true : false; });
+            if (done) {
+                clearInterval(timer);
+                console.log('Serializing the DOM into XHTML...');
+                var html = page.evaluate(function() {
+                    // Serialize the DOM using the built-in serializer.
+                    (new berjon.respec()).toXHTMLSource();
+                    var outer = document.querySelector('html').outerHTML;
+                    return '<!DOCTYPE html>\n' + outer.replace('<head>', '\n<head>');
+                });
+                fs.write(output, html, 'w');
+                console.log(output + ' created!\n');
+                phantom.exit();
+            } else {
+                if (timeout === 0) {
+                    clearInterval(timer);
+                    console.log('Timeout loading ' + source + '. Is it a valid ReSpec source file?');
+                    phantom.exit();
+                } else {
+                    console.log('Timing out in ' + timeout-- + ' s');
+                }
+            }
+        }, 1000);
+    }
+});