--- a/bp/index.html	Mon Apr 08 00:52:08 2013 +0200
+++ b/bp/index.html	Thu Apr 11 02:42:58 2013 -0400
@@ -69,10 +69,17 @@
 
 The following best practices are discussed in this document and listed here for convenience.
 
-<p class='stmt'><a href="#IDENTIFY">IDENTIFY</a> The first step is indentifying data sets that other people may wish to re-use.
+<p class='stmt'><a href="#IDENTIFY">IDENTIFY</a> Indentify data sets that other people may wish to re-use.
 </p>
 
-<p class='stmt'><a href="#MODEL">MODEL</a> Sketch the main objects the data describes.  Use lines to describe how they are related to each other.  Denormalize the data as necessary. Model the data in an application-independent, objective way in terms of representation.
+<p class='stmt'><a href="#MODEL">MODEL</a> Model the data in an application-independent, objective way in terms of representation.  Denormalize the data as necessary.
+</p>
+
+<p class='stmt'><a href="#METADATA">METADATA</a> Provide basic metadata, including MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s). 
+</p>
+
+<p class='stmt'><a href="#IDENTIFY">PII</a> Do not Publish Personally Identifiable Information as Open Data on the Web
+Data on the public Web can be potentially misused. Examples of personally identifiable data include: individual names, national identification number, phone number, credit card number and driver license number. 
 </p>
 
 <p class='stmt'><a href="#NAME">NAME</a> Use HTTP URIs as names for your objects. Give careful consideration to the URI naming strategy. Consider how the data will change over time and name as necessary.
@@ -81,22 +88,25 @@
 <p class='stmt'><a href="#STANDARD-VOCABULARIES">STANDARD_VOCABULARIES</a> Describe objects with standard vocabularies whenever possible.
 </p>
 
-<p class='stmt'><a href="#CONSISTENT-REPRESENTATION">CONSISTENT_REPRESENTATION</a> Provide representations of a resource consistently and predictably.
+<p class='stmt'><a href="#REPRESENTATION">REPRESENTATION</a> Convert the source data into a Linked Data representation, also called an RDF serialization including Turtle, Notation-3 (N3), N-Triples, XHTML with embedded RDFa, and RDF/XML.
 </p>
 
-<p class='stmt'><a href="#DESCRIPTIONS">DESCRIPTIONS</a> Publish human and machine readable descriptions with your Linked Data.
+<p class='stmt'><a href="#HUMAN">HUMAN READABLE</a> Provide human readable descriptions with your Linked Data.
 </p>
 
-<p class='stmt'><a href="#CONVERT">CONVERT</a> Convert the source data into a Linked Data representation, also called an RDF serialization including Turtle, Notation-3 (N3), N-Triples, XHTML with embedded RDFa, and RDF/XML.
+<p class='stmt'><a href="#MACHINE">MACHINE ACCESSIBLE</a>Provide access to the data representation via RESTful API, SPARQL endpoint(s) and RDF download.
 </p>
 
 <p class='stmt'><a href="#SPECIFY-LICENSE">SPECIFY_LICENSE</a> Specify an appropriate license.
 </p>
 
-<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE</a> Host Linked Open Data on the public Web and announce it.  
+<p class='stmt'><a href="#HOST">HOST</a> Deliver open government data on authoritative domain to increase perceived trust.  
 </p>
 
-<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT</a> Maintenance is critical. If you move or remove data that is published to the Web, you may break third party applications or mashups.
+<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE</a> Announce open government data, have a feedback mechanism and be prepared to be responsive to feedback. 
+</p>
+
+<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT</a> Maintenance is critical. Without a permanent identifier scheme, if you move or remove data that is published to the Web, you may break third party applications or mashups which is clearly undesireable.  URI strategy and implementation are critical.
 </p>
 
 
@@ -658,10 +668,6 @@
 " target="_blank">PROV Family of Documents</a> defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web. 
 </p>
 
-<p>
-The W3C Government Linked Data Working Group offers the following best practices for government stakeholders to assist people using open government data available on the public Web.
-</p>
-
 <!-- todo: Talk to John Erickson to develop this more for possible inclusion
 <p>W3C GLD could recommend a simple <b>provenance scoring system</b> for GLD analogous to TBL's 5 stars for linked data. Such a system might include:</p>
 <ul>
@@ -688,13 +694,6 @@
 </section> <!-- Pragmatic Provenance >> -->
 
 
-<!--    VERSIONING   -->
-<section>
-<h2>Versioning</h2>
-
-<p class="todo">(Editors) Propose that we remove Versioning because it has not been given sufficient attention by the WG to make a recommendation.</p>
-
-
 <!-- <p class="todo">To Review: John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Hadley Beeman (LinkedGov)</p> -->
 <!--
 <p>
@@ -739,18 +738,6 @@
 
 
 
-<!--   SOURCE DATA   -->
-<section>
-<h2>Source Data</h2>
-
-<p class="todo"> (Biplav Srivastava/IBM) This is an important section but we're light on details (provide suggested approach, not a bunch of questions).
-</p>
-
-<p>
-This section contains advices concerning how to expose source data, data which is being maintained in pre-existing (non-linked-data) systems such as RDBs or spreadsheets.
-</p>
-
-
 <!--
 <p>Use case</p>
 <p>Suppose a city is considering opening up its data. It has certain concerns:</p>
@@ -772,27 +759,6 @@
 
 !-->
 
-
-<h3>Source Data Publication Checklist</h3>
-
-<p class="todo"> (Biplav) - This seems redundant with other parts of the document.  Should this be folded in above??
-
-<p class="highlight">Deliver open government data on authoritative domain to increase perceived trust.
-</p>
-
-<p class="highlight">Provide access to human and machine readable data via RESTful API, SPARQL endpoint or RDF download. <br/>
-</p>
-
-<p class="highlight">Provide basic metadata, i.e., MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s).
-</p>
-
-<p class="highlight">Specify an appropriate license<br/>
-</p>
-
-<p class="highlight">Do not Publish Personally Identifiable Information as Open Data on the Web</b><br/>
-Data on the public Web can be potentially misused, however the threat is balanced by benefits by privacy groups (including <a href="http://www.w3.org/Privacy/" target="_blank">W3C Privacy</a>) to provide recommendations. Examples of personally identifiable data are - individual names, national identification number, phone number, credit card number and driver license number.
-</p>
-
 </section>
 
 

--- a/bp/respec-config.js	Mon Apr 08 00:52:08 2013 +0200
+++ b/bp/respec-config.js	Thu Apr 11 02:42:58 2013 -0400
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "WD",
-    publishDate:          "2013-04-08",
+    publishDate:          "2013-04-11",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/