--- a/bp/index.html Thu Dec 12 11:02:17 2013 -0500
+++ b/bp/index.html Thu Dec 12 13:47:01 2013 -0500
@@ -15,7 +15,7 @@
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
copyrightStart: "2012",
- //lcEnd: "2013-04-08",
+ //lcEnd: "2013-12-19",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "bp",
@@ -45,9 +45,16 @@
// editors, add as many as you like
// only "name" is required
editors: [
- { name: "Bernadette Hyland", company: "3 Round Stones", companyURL: "http://3roundstones.com/" },
- {name: "Ghislain Auguste Atemezing", company: "Eurecom", companyURL: "http://www.eurecom.fr"},
- {name: "Boris Villazon-terrazas", company: "iSOCO", companyURL: "http://www.isoco.com"}
+ { name: "Bernadette Hyland",
+ url: "http://www.about.me/bernadettehyland/",
+ company: "3 Round Stones, Inc.", companyURL: "http://3roundstones.com/"},
+ { name: "Ghislain Atemezing",
+ url: "http://www.eurecom.fr/~atemezin/",
+ company: "EURECOM", companyURL: "http://www.eurecom.fr/en"},
+ { name: "Boris Villazón-Terrazas",
+ url: "http://boris.villazon.terrazas.name",
+ company: "iSOCO, Intelligent Software Components S.A.",
+ companyURL: "http://www.isoco.com"}
],
// authors, add as many as you like.
@@ -175,14 +182,14 @@
<!--Any further W3C Working Group may update this document. -->
<section id="sotd">
- <p>This document is unfinished and it is subject to change. </p>
+ <p>This document is unfinished and is subject to change. </p>
</section>
<!-- INTRODUCTION -->
<section id="abstract">
<p>
-This document sets out a series of best practices designed to facilitate development and delivery of open government data as Linked Data. <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Open Data Principles</a> are used to publish high quality, heterogeneous datasets in a distributed manner. The goal of this document is to aid the publication of high quality <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data (LOD)</a> from government authorities, to compile the most relevant data management practices, to promote best practices for publishing Linked Open Data, and to warn against practices that are considered harmful. The following recommendations are offered to creators, maintainers and operators of Web sites publishing open government data.
+This document sets out a series of best practices designed to facilitate development and delivery of open government data as Linked Data. <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Data Principles</a> are used to publish high quality, heterogeneous datasets in a distributed manner. The goal of this document is to aid the publication of high quality <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data (LOD)</a> from government authorities, to compile the most relevant data management practices, to promote best practices for publishing Linked Open Data, and to warn against practices that are considered harmful. Linked Data can be published by a person or organization behind a firewall or on the public Web. If Linked Data is published on the public Web, it is generally called Linked Open Data. The following recommendations are offered to creators, maintainers and operators of Web sites interested in Linked Data.
</p>
<h2>Audience</h2>
@@ -191,21 +198,20 @@
as <a href="http://www.w3.org/TR/ld-glossary/#hypertext-markup-language">HTML</a>,
<a href="http://www.w3.org/TR/ld-glossary/#uri">URIs</a>, and
<a href="http://www.w3.org/TR/ld-glossary/#hypertext-transfer-protocol">HTTP</a>.
-The document is targeted at developers, government information management staff, Web site administrators.
+The document is targeted at developers, government information management staff, and Web site administrators.
</p>
<h2>Scope</h2>
<p>
-<a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of <a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a>
-(Resource Description Framework [[RDF-CONCEPTS]]). RDF can be written in a variety of syntaxes (e.g.
+<a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of <a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a> (Resource Description Framework) [[RDF-CONCEPTS]]. RDF can be written in a variety of syntaxes (e.g.
+<a href="http://www.w3.org/TR/ld-glossary/#rdfa">RDFa</a>,
+<a href="http://www.w3.org/TR/ld-glossary/#json-ld">JSON-LD</a>,
+<a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> and N-Triples),
<a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a>,
-<a href="http://www.w3.org/TR/ld-glossary/#n3">N3</a>,
-<a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> and N-Triples) and
-<a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>.
+and <a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>.
+
<a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a> and
-<a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> are not the same thing.
-
-Linked Data can be published by a person or organization behind a firewall or on the public Web. If Linked Data is published on the public Web, it is generally called Linked Open Data.
+<a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> are not synonyms. Linked Data however could not exist without a consistent underlying data model which is RDF.[RDF-CONCEPTS]. Understanding the basics of RDF is necessary to leverage <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a>.
</p>
<h2>Background</h2>
@@ -231,11 +237,10 @@
<p class='stmt'><a href="#WORKFLOW">CHOOSE A WORKFLOW:</a><br />Determine which workflow to use for your Linked Open Data use case.
</p>
-<p class='stmt'><a href="#SELECT">SELECT A DATASET:</a><br /> Select a dataset that provides benefit to others for re-use. Consider a dataset that is uniquely collected by your organization: information that when combined with other open data provides greater value. For example, publishing facilities that can then be linked with geographic information including post codes is a popular example.
+<p class='stmt'><a href="#SELECT">SELECT A DATASET:</a><br /> Select a dataset that provides benefit to others for re-use.
</p>
-<p class='stmt'><a href="#PERSONAL">PERSONALLY IDENTIFIABLE DATA:</a><br /> Do not publish personally identifiable information as Linked Open Data as it can potentially be misused. Examples of personally identifiable data include: individual names, national identification numbers, phone numbers and office extensions, driver's license numbers, salaries and tax return information. Exceptions to this may include publically identifiable information required by law, such as for some public officials. Some countries
-</p>
+<p class='stmt'><a href="#PERSONAL">PERSONALLY IDENTIFIABLE DATA:</a><br /> Do not publish personally identifiable information as Linked Open Data as it can potentially be misused.</p>
<p class='stmt'><a href="#LICENSE">ASSOCIATE A LICENSE:</a> <br />Associate an appropriate open
license with the published data. People will only reuse data when there is a clear, acceptable license associated with it.
@@ -361,15 +366,42 @@
<img src="img/GLF_Villazon-terrazas.PNG" width="600" />
</section>
+<!-- SELECT -->
+<section id="SELECT">
+<h2>Select a Dataset</h2>
+
+<p>
+Consider publishing a dataset that is uniquely collected by your organization. Ideally, this information when combined with other open data provides greater value. Government agencies are in a unique position to collect and curate valuable datasets. Since there is effort and cost associated with modeling, publishing and maintaining any data set as a public service, selection of high value data sets may be guided re-use potential and popularity, among other factors. Data about geographic features, human health, legislation, population and demographics, and the environmental data are just some of the popular open government data sets that have been published as Linked Open Data.
+</p>
+
+<p>
+For example, publishing regulated facilities that can then be linked with latitude and longitude allows the facilities to be plotted on a map. That data can then be extended using post codes allowing people to search via post code what facilities are near them on a map view. Facilities data published as extensible Linked Data allows Web developers to rapidly build Web interfaces that are both useful to machines and humans.
+</p>
+
+
+<!-- SELECT -->
+<section id="PERSONAL">
+<h2>Personally Identifiable Information</h2>
+
+<p>
+Do not publish personally identifiable information as Linked Open Data as it can potentially be misused.
+Examples of personally identifiable data include: individual names, national identification numbers, phone numbers and office extensions, driver's license numbers, salaries and tax return information. Exceptions to this practice may include public information required by law, such as individual names, office extensions, salaries and tax information, for some public officials.
+</p>
+
+
<!-- DATA MODELING -->
<section id="MODEL">
<h2>Data Modeling</h2>
<p>
-Modeling Linked Data requires representation of data objects and how they are related in an application-independent way. For example, if the data was originally organized for a specific application, Linked Data modeling may involve removing government program or agency-related content. When modeling Linked Data, we are representing facts and how they are for more general purpose consumption by the public. In many cases, denormalizing the data may be necessary and is appropriate. [[WOOD2013]]
+Modeling Linked Data requires representation of data objects and how they are related in an application-independent way. For example, if the data was originally organized for a specific application, Linked Data modeling may involve removing government program or agency-related content. When modeling Linked Data, one is representing things and how they are related, typically for public consumption. Denormalizing data may be necessary and is appropriate when modeling Linked Data. Linked Data can and is used within government agencies to improve data integration for related or complementary information.
+</p>
+
+<p> The process of data modeling should involve someone who is intimately familiar with the representation of data using open Web standards. Familiarity with standard vocabularies will both expedite the modeling process and help produce data that can be more readily linked to other data sets.
</p>
</section>
+
<!-- VOCABULARY SELECTION -->
<section id="STANDARD-VOCABULARIES">
<h2>Vocabulary Selection</h2>
@@ -378,6 +410,7 @@
There are several core W3C vocabularies that allow a developer to describe basic or more
complex relationships as Linked Data. Standardized vocabularies should be reused as much
as possible to facilitate inclusion and expansion of the <a href="http://www.w3.org/TR/ld-glossary/#web-of-data">Web of data</a>.
+
Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
</p>
@@ -554,7 +587,6 @@
<section id="MODEL">
<h2>Vocabulary Creation</h2>
-
<p><i>There will be cases in which authorities will need to mint their own vocabulary terms. This
section provides a set of considerations aimed at helping to government stakeholders mint
their own vocabulary terms. This section includes some items of the previous section
@@ -647,8 +679,6 @@
</p> -->
-
-
<section id="multilingual">
<h2>Multilingual Vocabularies</h2>
<p class="highlight"><b>While designing a vocabulary, provide labels and descriptions