--- a/model/ProvenanceModel.html	Tue Oct 11 14:34:25 2011 -0400
+++ b/model/ProvenanceModel.html	Tue Oct 11 21:07:05 2011 +0100
@@ -47,7 +47,7 @@
       };
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-          specStatus:           "FPWD",
+          specStatus:           "ED",
           
           // the specification's short name, as in http://www.w3.org/TR/short-name/
           shortName:            "prov-dm",
@@ -57,7 +57,7 @@
           // subtitle   :  "Initial draft for internal discussion",
  
           // if you wish the publication date to be other than today, set this
-           publishDate:  "2011-10-18",
+          // publishDate:  "2011-10-18",
  
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -65,8 +65,8 @@
  
           // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
           // and its maturity status
-          // previousPublishDate:  "1977-03-15",
-          // previousMaturity:  "WD",
+          previousPublishDate:  "2011-10-18",
+          previousMaturity:  "FPWD",
  
           // if there a publicly available Editor's Draft, this is the link
           edDraftURI:           "http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html",
@@ -119,14 +119,14 @@
           wgURI:        "http://www.w3.org/2011/prov/",
           
           // name (with the @w3c.org) of the public mailing to which comments are due
-          wgPublicList: "public-prov-wg@w3c.org",
+          wgPublicList: "public-prov-wg",
           
           // URI of the patent status for this WG, for Rec-track documents
           // !!!! IMPORTANT !!!!
           // This is important for Rec-track documents, do not copy a patent URI from a random
           // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
           // Team Contact.
-          wgPatentURI:  "",
+          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/46974/status",
 
           // Add extraReferences to bibliography database
           preProcess: [addExtraReferences],
@@ -395,7 +395,7 @@
 <p>
 The following ER diagram provides a high level overview of the <strong>structure of PROV-DM assertions</strong>. Examples of provenance assertions that conform to this schema are provided in the next section (note: cardinality constraints on the associations are 0..* unless otherwise stated)</p>
 
-  <img src="overview.png" style="align=center;" alt="PROV-DM overview"/>
+  <img src="overview.png" alt="PROV-DM overview"/>
 
 <p>The model includes the following elements:</p>
 <ul>
@@ -611,7 +611,7 @@
 <h3>Graphical Illustration</h3>
 
 Provenance assertions can be illustrated as a graph.
-Details about the graphical illustration can be found in <a href="#illustration-convention">appendix</a>.
+Details about the graphical illustration can be found in <a href="#illustration-conventions">appendix</a>.
 
 <img src="example-graphical.png" alt="example"/>
 
@@ -816,7 +816,7 @@
 <p>identified by identifier <span class="name">id</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</span>, start time <span class="name">t+1</span>, and end time <span class="name">t+1+epsilon</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span> (declared in some namespace with prefix <span class="name">app</span>).  The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity.  The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for subtyping to be expressed.
 </p>
 
-<p>The mere existence of a process execution assertion entails some event ordering in the world, since the start event precedes the end event.  This is expressed by constraint <a href="'#start-precedes-end'">start-precedes-end</a>.</p>
+<p>The mere existence of a process execution assertion entails some event ordering in the world, since the start event precedes the end event.  This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
 
 <div class='constraint' id='start-precedes-end'> From a process execution expression, one can infer that the
 start event precedes the end event of the represented activity.</div>
@@ -2383,7 +2383,7 @@
 </pre>
 <p>The corresponding graphical representation is shown below.</p>
 
-<img src="collections.png" style="align=center;" alt="collections"/>
+<img src="collections.png" alt="collections"/>
 
 
 <p>  With these assertions:</p>