--- a/bp/index.html Thu Mar 07 02:04:22 2013 +0100
+++ b/bp/index.html Thu Mar 07 02:10:34 2013 +0100
@@ -121,10 +121,10 @@
<!-- Diagrams -->
<h3> Linked Open Data Lifecycle </h3>
-<p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p>
+<!-- <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p> -->
-<p class="todo"> To Review: Bernadette, Michael, Boris - Please review the brief descriptions for your lifecycle diagrams.
-</p>
+<!-- <p class="todo"> To Review: Bernadette, Michael, Boris - Please review the brief descriptions for your lifecycle diagrams.
+</p> -->
<ul>
<li>
@@ -227,8 +227,8 @@
<p class="todo"> To include: Phil suggests to include <a href="http://www.w3.org/QA/2012/07/conformance_for_vocabularies.html" target="_blank">Conformance for Vocabularies</a>.
</p>
-<p class="todo">Please Review: Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila-Suero (UPM)</p>
-<p>
+<!-- <p class="todo">Please Review: Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila-Suero (UPM)</p>
+<p> -->
Reuse standard, vetted vocabularies to encourage others to use your data. Guidance on finding standard, vetted vocabularies is described in the Vocabulary Discovery Checklist below.
</section>
@@ -398,8 +398,8 @@
<!-- << URI CONSTRUCTION -->
<section>
<h2>URI Construction</h2>
-<p class="todo">To Review: Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila (UPM), John Erickson (RPI), Bernadette Hyland (3 Round Stones)</p>
-<p>
+<!-- <p class="todo">To Review: Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila (UPM), John Erickson (RPI), Bernadette Hyland (3 Round Stones)</p>
+<p> -->
Guidance in this document is minting URIs for vocabularies, concepts, and datasets. This section specifies how to create good URIs for use in government linked data. Inputs include
<ul>
<li><a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a></li>
@@ -521,7 +521,7 @@
<section>
<h3>URI Policy for Persistence</h3>
-<p class="todo">To Review: Bernadette Hyland, John Erickson</p>
+<!-- <p class="todo">To Review: Bernadette Hyland, John Erickson</p> -->
<!-- Acknowledge D. Wood, "Reliable and Persistent Identification of Linked Data Elements" LED chapter, 2010 -->
@@ -582,7 +582,7 @@
<!-- SPECIFY LICENSE -->
<section>
<h2>Specifying an Appropriate License</h2>
-<p class='todo'>To Review: Bernadette Hyland</p>
+<!-- <p class='todo'>To Review: Bernadette Hyland</p> -->
<p>
It is best practice to explicitly attach a license statement to each data set. Governments typically define ownership of works produced by government employees or contractors in legislation. It is beyond the charter of this working group to describe and recommend appropriate licenses for Open Government content published as Linked Data, however there are useful Web sites that offer detailed guidance and licenses. One valuable resource is the <a href="http://creativecommons.org/">Creative Commons</a> website. Creative Commons develops, supports, and stewards legal and technical infrastructure for digital content publishing.
@@ -597,7 +597,7 @@
<section>
<h2>Security and Hosting</h2>
-<p class='todo'>To Review: Michael Pendleton (US EPA)</p>
+<!-- <p class='todo'>To Review: Michael Pendleton (US EPA)</p> -->
<p>Within government agencies, hosting linked data may require submission and review of a security plan to the authority's security team. While security plan specifics will vary widely based on a range of factors like hosting environment and software configuration, the process for developing and getting a security plan approved can be streamlined if the following guidelines and best practices are considered:</p>
@@ -626,7 +626,7 @@
<section>
<h2>Publishers' "Social Contract"</h2>
-<p class='todo'>To Review: Bernadette Hyland </p>
+<!-- <p class='todo'>To Review: Bernadette Hyland </p> -->
<p>
Publishers of Linked Data enter into an implicit social contract with users of their data. Publishers should recognize the responsibility to maintain data once it is published by a government authority. Ensure that the Linked Open Data set(s) your organization publishes remains available where you say it will be. Here is a summary of best practices that relate to the implicite "social contract". Additional informational details are included for reference.
@@ -702,7 +702,7 @@
<!-- VERSIONING -->
<section>
<h2>Versioning</h2>
-<p class="todo">To Review: John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Hadley Beeman (LinkedGov)</p>
+<!-- <p class="todo">To Review: John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Hadley Beeman (LinkedGov)</p> -->
<p>
This section specifies how to publish data which has multiple versions, including variations such as:
@@ -747,7 +747,7 @@
<!-- << STABILITY -->
<section>
<h2>Stability</h2>
-<p class="todo">To Review: Anne Washington (GMU), Ron Reck</p>
+<!-- <p class="todo">To Review: Anne Washington (GMU), Ron Reck</p> -->
<!-- << STABILITY.overview -->
<h3>Overview</h3>
@@ -828,7 +828,7 @@
<!-- SOURCE DATA -->
<section>
<h2>Source Data</h2>
-<p class='todo'>To Review: Michael Hausenblas (DERI), Spyros Kotoulas(IBM/SCTC), Biplav Srivastava (IBM)</p>
+<!-- <p class='todo'>To Review: Michael Hausenblas (DERI), Spyros Kotoulas(IBM/SCTC), Biplav Srivastava (IBM)</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.