--- a/bp/index.html Thu Jan 26 11:23:32 2012 +0000
+++ b/bp/index.html Thu Jan 26 15:48:14 2012 +0000
@@ -13,16 +13,20 @@
</head>
<body>
+<p class="todo">Make sure all contributors are listed as Authors</p>
+
<section id="abstract">
<p>
This document provides best practices and guidance to create high quality, re-usable Linked Open Data (LOD).
</p>
</section>
-<section id='sotd'>
+<section id="sotd">
<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>
@@ -36,7 +40,7 @@
<h2>Introduction</h2>
<section>
-<h3>Overview</h3>
+<h3>Overview - Michael</h3>
<p>
<a href="http://www.w3.org/DesignIssues/LinkedData.html" title="Linked Data - Design Issues">Linked Data</a> addresses key requirements of open government by providing a family of international standards for the publication, dissemination and reuse of structured data. Further, Linked Data, unlike previous data formatting and publication approaches, provides a simple mechanism for combining data from multiple sources across the Web.
</p>
@@ -52,24 +56,20 @@
<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>? We start collecting the available <a href="http://www.w3.org/2011/gld/wiki/GLD_Life_cycle">GLD Life cycles</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>
</section>
<!-- PROCUREMENT -->
<section>
-<h3>Procurement</h3>
+<h3>Procurement - Boris</h3>
<p class='responsible'>George Thomas (Health & Human Services, US), Mike Pendleton (Environmental Protection Agency, US), John Sheridan (OPSI, UK)</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>
-<h4>Status</h4>
-<p>21-Dec-2011 - MikeP and George reaching out to John Sheridan to discuss over the last two weeks of December. Possible that John has already taken leave for the holidays. Needs to get jump started asap.
-</p>
-<p>23-Jan-2012 - Major revision by MikeP
-</p>
+
<p>
Linked Open Data (LOD) offers novel approaches for publishing and consuming data on the Web. This procurement overview and companion glossary is intended to help contract officers and their technical representatives understand LOD activities, and their associated products and services. It is hoped that this will aid government officials in procuring LOD related products and services.
</p>
@@ -120,6 +120,8 @@
</ol>
<h4>Procurement Checklist</h4>
+
+<p class="todo">Check if latest Wiki <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary#Best_Practices_for_Procurement">content</a> is here</p>
<p>
Credit: This section of Procurement Best Practices was taken from the <a href="http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook">Linked Data Cookbook</a>.
@@ -201,13 +203,58 @@
<!-- VOCABULARY SELECTION -->
<section>
-<h3>Vocabulary Selection</h3>
+<h3>Vocabulary Selection - Boris</h3>
<p class='responsible'>Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (UPM), George Thomas (Health & Human Services, US), John Erickson (RPI), Biplav Srivastava (IBM)</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>
-<b>Ghislain</b>
+<h4>Discovery</h4>
+<p>First phase is discovery, that is, the process of finding a vocabulary that can represent entities of a domain, for example, organisations or people.</p>
+
+<h5>Key terms</h5>
+<p>Identify key domain terms</p>
+
+<h5>Using Repositories</h5>
+<p>Search for key terms in vocabularies repositories</p>
+
+<h5>Using Catalogs</h5>
+<p>Search for datasets in data catalogues (CKAN, etc.) within the same domain. How do they model their data?</p>
+
+
+<h4>Vocabulary selection criteria checklist</h4>
+
+<p class='issue'>What other sections from the BP and/or other GLD documents can we re-use? See <a href="https://www.w3.org/2011/gld/track/issues/16">ISSUE-16</a></p>
+
+<ul>
+<li>Labels and comments</li>
+<li>Multilingualism</li>
+<li>Usage</li>
+<li>Maintenance</li>
+<li>Permanent URIs</li>
+<li>Change control</li>
+<li>Publisher</li>
+<li>Documentation</li>
+</ul>
+
+
+<!-- Editorial notes for creators/maintainers:
+
+Creation Namespace management
+stability (PURL)
+longevity (hit by bus)
+Available ontology development methodologies (Informative)
+Usage (instance-level, SPARQL, etc.)
+Versioning
+go back to creation
+Partial or full deprecation
+Cross-cutting issues: "Hit-by-bus" -->
+
+
+
+
+
+<!-- <b>Ghislain</b>
<p>One of the most challenging task when publishing data set is to have metadata describing the model used to capture it. The model or the ontology gives the semantic of each term used within the data set or in the LOD cloud when published. The importance of selecting the appropriate vocabulary is threefold:</p>
<ul>
<li>Ease the interoperability with existing vocabularies</li>
@@ -253,24 +300,26 @@
<li>Number of LD datasets using it?</li>
<li>We reuse the vocabulary by reusing directly its terms? or importing the whole vocabulary?</li>
<li>...</li>
-</ul>
+</ul> -->
</section>
<!-- URI CONSTRUCTION -->
<section>
-<h3>URI Construction</h3>
+<h3>URI Construction - Michael</h3>
<p class='responsible'>Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI), Boris Villazon-Terrazas (UPM), Daniel Vila (UPM), John Erickson (RPI), Martin Alvarez (CTIC), Cory Casanove (OMG)</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>
+
+<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/223_Best_Practices_URI_Construction">content</a>.</p>
</section>
<!-- VERSIONING -->
<section>
-<h3>Versioning</h3>
+<h3>Versioning - Boris</h3>
<p class='responsible'>John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Cory Casanave (OMG), Hadley Beeman (LinkedGov)</p>
<p>
This section specifies how to publish data which has multiple versions, including variations such as:
@@ -281,26 +330,34 @@
<li>retracting published data</li>
</ul>
</p>
+<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary#Versioning">content</a>.</p>
+
</section>
<!-- STABILITY -->
<section>
-<h3>Stability</h3>
+<h3>Stability - Michael</h3>
<p class='responsible'>Anne Washington (GMU), Ron Reck</p>
<p>
This section specifies how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary.
</p>
+
+<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/225_Best_Practices_for_Stability">content</a>.</p>
+
</section>
-<!-- LEGACY DATA -->
+<!-- SOURCE DATA -->
<section>
-<h3>Legacy Data</h3>
-<p class='responsible'>Michael Hausenblas (DERI), Biplav Srivastava (IBM)</p>
+<h3>Source Data - Michael</h3>
+<p class='responsible'>Michael Hausenblas (DERI), Spyros Kotoulas(IBM/SCTC), Biplav Srivastava (IBM)</p>
<p>
-This section contains advices concerning how to expose legacy data, data which is being maintained in pre-existing (non-linked-data) systems.
+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 class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/Best_Practices_Discussion_Summary#Source_Data">content</a> as well as Spyros' <a href="http://www.w3.org/2011/gld/wiki/images/0/08/LegacyData.pdf">slides</a> from the F2F2</p>
+
</section>
@@ -309,16 +366,15 @@
<h3>Cookbook</h3>
<p class='responsible'>Bernadette Hyland (3 Round Stones), Sarven Capadisli (DERI)</p>
<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.
+See <a href="http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook">Cookbook for Open Government Linked Data</a>.
</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>
<!-- Pragmatic Provenance -->
<section>
-<h3>Pragmatic Provenance</h3>
+<h3>Pragmatic Provenance - Boris</h3>
<p class='responsible'>John Erickson (RPI)</p>
-<p></p>
+<p class="todo">Integrate Wiki <a href="http://www.w3.org/2011/gld/wiki/228_Best_Practices_Pragmatic_Provenance">content</a>.
</section>
<!-- ACK -->
--- a/bp/respec-config.js Thu Jan 26 11:23:32 2012 +0000
+++ b/bp/respec-config.js Thu Jan 26 15:48:14 2012 +0000
@@ -1,7 +1,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
- publishDate: "2012-01-20",
+ publishDate: "2012-01-26",
//copyrightStart: "2010",
// the specification's short name, as in http://www.w3.org/TR/short-name/