--- a/bp/index.html	Thu Jul 21 17:50:07 2011 +0100
+++ b/bp/index.html	Fri Jul 22 07:20:34 2011 +0100
@@ -20,14 +20,14 @@
 </section>
 
 <section id='sotd'>
-  <p>This document is work in progress.</p>
+  <p>This document is work in progress. You might also want to check the accompanying <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary">Wiki page</a> of the GLD Working Group for ongoing discussions.</p>
 </section>
 
 <section class="introductory">
 <h2>Scope</h2>
 
 <p>
-This is ...
+This document is aimed at assisting government agencies and their contractors, vendors as well as researchers, to publish high quality, consistent data sets using W3C standards to increase interoperability.
 </p>
 </section>
 
@@ -44,15 +44,22 @@
 In an era of reduced local, state and federal budgets, there is strong economic motivation to reduce waste and duplication in data management and integration. Linked Open Data is a viable approach to publishing governmental data to the public, but only if it adheres to some basic principles.
 </p>
 
-<p class='todo'>TODO: more motivation and SOTA</p>
-
+<h3>Motivation</h3>
+Th best practices provided here are provide a methodical approach for the creation, publication and dissemination of government Linked Data, including:
+<ul>
+	<li>Description of the full life cycle of a Government Linked Data project, starting with identification of suitable data sets, procurement, modeling, vocabulary selection, through publication and ongoing maintenance.</li>
+	<li>Definition of known, proven steps to create and maintain government data sets using Linked Data principles.</li>
+	<li>Guidance in explaining the value proposition for LOD to stakeholders, managers and executives.</li>
+	<li>Assist the Working Group in later stages of the Standards Process, in order to solicit feedback, use cases, etc.</li>
+</ul>
+<p class='todo'>QUESTION: would it make sense to base the above mentioned GLD life cycle on the general <a href="http://linked-data-life-cycles.info/">Linked Data life cycles</a>?</p>
 </section>
 
 
 <!--    PROCUREMENT   -->
 <section>
 <h3>Procurement</h3>
-<p class='responsible'>Katherine Goodier (L3 Communications)</p>
+<p class='responsible'>Katherine Goodman (L3 Communications)</p>
 <p>
 Specific products and services involved in governments publishing linked data will be defined, suitable for use during government procurement. Just as the <a href="http://www.w3.org/WAI/intro/wcag" title="WCAG Overview">Web Content Accessibility Guidelines</a> allow governments to easily specify what they mean when they contract for an accessible Website, these definitions will simplify contracting for data sites and applications.
 </p>
@@ -62,7 +69,7 @@
 <!--    VOCABULARY SELECTION   -->
 <section>
 <h3>Vocabulary Selection</h3>
-<p class='responsible'>Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), David Price (TopQuadrant)</p>
+<p class='responsible'>Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), David Price (TopQuadrant), Boris Villazon-Terrazas (UPM)</p>
 <p>
 The group will provide advice on how governments should select RDF vocabulary terms (URIs), including advice as to when they should mint their own. This advice will take into account issues of stability, security, and long-term maintenance commitment, as well as other factors that may arise during the group's work.
 </p>
@@ -72,7 +79,7 @@
 <!--    URI CONSTRUCTION   -->
 <section>
 <h3>URI Construction</h3>
-<p class='responsible'>Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI)</p>
+<p class='responsible'>Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI), Boris Villazon-Terrazas (UPM)</p>
 <p>
 This section specifies how to create good URIs for use in government linked data. Inputs include <a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a>, <a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF), and <a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk). Guidance will be produced not only for minting URIs for governmental entities, such as schools or agencies, but also for vocabularies, concepts, and datasets.
 </p>
@@ -122,7 +129,7 @@
 <p>
 This section provides a collection of advice on smaller, more specific issues, where known solutions exist to problems collected for the Community Directory. This part is going to be separated out as a Working Group Note, or website, rather than a Recommendation. It may, instead, become part of the Community Directory site.
 </p>
-<p class='todo'>TODO: decide how to proceed with this section; maybe intro here and then link to website?</p>
+<p class='todo'><a href="http://www.w3.org/2011/gld/track/issues/1" title="ISSUE-1: Where should the BP cookbook go? - Government Linked Data Working Group Tracker">ISSUE-1</a>: decide how to proceed with this section; maybe intro here and then link to website?</p>
 </section>
 
 

--- a/bp/respec-config.js	Thu Jul 21 17:50:07 2011 +0100
+++ b/bp/respec-config.js	Fri Jul 22 07:20:34 2011 +0100
@@ -1,7 +1,7 @@
 var respecConfig = {
     // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
     specStatus:           "ED",
-    publishDate:          "2011-07-21",
+    publishDate:          "2011-07-22",
     //copyrightStart:       "2010",
 
     // the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -32,8 +32,8 @@
     // editors, add as many as you like
     // only "name" is required
     editors:  [
-        { name: "Michael Hausenblas", url: "http://sw-app.org/mic.xhtml#i",
-          company: "DERI", companyURL: "http://www.deri.ie" }
+        { name: "Michael Hausenblas", url: "http://sw-app.org/mic.xhtml#i", company: "DERI", companyURL: "http://www.deri.ie" },
+		{ name: "Bernadette Hyland", url: "https://twitter.com/bernhyland",  company: "3 Round Stones", companyURL: "http://3roundstones.com/"}
     ],
 
     // authors, add as many as you like.