--- a/bp/index.html Sat Dec 21 21:59:11 2013 -0500
+++ b/bp/index.html Sat Dec 21 22:07:21 2013 -0500
@@ -1,6 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.1//EN"
- "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd">
+<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Best Practices for Publishing Linked Data</title>
@@ -13,7 +11,7 @@
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "LC",
+ specStatus: "WG-NOTE",
copyrightStart: "2012",
//lcEnd: "2013-12-20",
@@ -21,12 +19,14 @@
shortName: "bp",
//subtitle: "",
// if you wish the publication date to be other than today, set this
- publishDate: "2013-12-19",
+ publishDate: "2013-12-21",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- //previousPublishDate: "2013-06-25",
- //previousMaturity: "CR",
+ // @@ JUST FOR TESTING - REMOVE THESE!
+ previousPublishDate: "2013-06-25",
+ previousMaturity: "FPWD",
+
//previousDiffURI: "http://dvcs.w3.org/hg/gld/bp/",
//diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
@@ -121,7 +121,7 @@
"yakel-07": {
title: "Digital curation" ,
- href: "DOI: 10.1108/10650750710831466",
+ href: "http://dx.doi.org/10.1108/10650750710831466",
authors: ["Elizabeth Yakel"] ,
publisher: "CLC Systems & Services, Vol. 23 Iss: 4, pp.335 - 340 (2007)"
},
@@ -208,7 +208,6 @@
<!--Any further W3C Working Group may update this document. -->
<section id="sotd">
- <p>This document is unfinished and is subject to change. </p>
</section>
<!-- INTRODUCTION -->
@@ -218,6 +217,9 @@
This document sets out a series of best practices designed to facilitate development and delivery of open government data as <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>. <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a> makes the World Wide Web into a global database, sometimes refered to as the "<a href="http://www.w3.org/TR/ld-glossary/#web-of-data">Web of Data</a>". Using <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Data Principles</a>, developers can query <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> from multiple sources at once and combine it without the need for a single common schema that all data shares. Prior to international data exchange standards for data on the Web, it was time consuming and difficult to build applications using traditional data management techniques. As more open government data is published on the Web, best practices are evolving too. The goal of this document is to compile the most relevant data management practices for the publication and use of of high quality data published by governments around the world as <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>.
</p>
+</section>
+
+
<h2>Audience</h2>
<p>
Readers of this document are expected to be familiar with fundamental Web technologies such
@@ -232,13 +234,13 @@
<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 the <a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a> (Resource Description Framework) family of standards for data interchange [[RDF-CONCEPTS]] and <a href="http://www.w3.org/TR/ld-glossary/#sparql">SPARQL</a> for query. <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 synonyms. Linked Data however could not exist without the consistent underlying data model that we call RDF [[RDF-CONCEPTS]]. Understanding the basics of RDF is helpful in leveraging <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a>.
</p>
+
<h2>Background</h2>
<p>
In recent years, governments worldwide have mandated publication of open government content to the public Web for the purpose of facilitating open societies and to support governmental accountability and transparency initiatives. In order to realize the goals of open government initiatives, the W3C Government Linked Data Working Group offers the following guidance to aid in the access and re-use of open
government data. Linked Data provides a simple mechanism for combining data from multiple
sources across the Web. <a href="http://www.w3.org/DesignIssues/LinkedData.html" title="Linked Data - Design Issues">Linked Data</a> addresses many objectives of open government transparency initiatives through the use international Web standards for the publication, dissemination and reuse of structured data.
</p>
-</section>
<!-- List of Best Practices -->
@@ -277,9 +279,6 @@
<p class='stmt'><a href="#SOCIAL-CONTRACT">STEP #10 RECOGNIZE THE SOCIAL CONTRACT:</a><br /> Recognize your responsibility in maintaining data once it is published. Ensure that the dataset(s) remain available where your organization says it will be and is maintained over time.
</p>
-
-</p>
-
</section>
<!-- Diagrams -->
@@ -304,7 +303,7 @@
</ul>
<div id="centerImg">
</div>
-<img src="img/GLF_Hyland.PNG" width="550"/>
+<img src="img/GLF_Hyland.PNG" width="550" alt="Diagram showing six stages in sequence: Identify, Model, Name, Describe, Convert, Publish; and a backward arrow: Maintain"/>
<ul>
<li>
@@ -313,7 +312,7 @@
</p>
</li>
</ul>
-<img src="img/GLF_Hausenblas.PNG" width="600"/>
+<img src="img/GLF_Hausenblas.PNG" width="600" alt="Diagram showing six stages: data awareness, data modelling, publishing, discovery, integration, use cases"/>
<ul>
<li>
@@ -321,7 +320,7 @@
</p>
</li>
</ul>
-<img src="img/GLF_Villazon-terrazas.PNG" width="600" />
+<img src="img/GLF_Villazon-terrazas.PNG" width="600" alt="Diagram showing five stages in a loop: Specify, Model, Generate, Publish, Exploit, then back to Specify" />
</section>
@@ -355,7 +354,7 @@
<h3>Understanding the Differences</h3>
<p>
-Linked Data modeling involves data going from one model to another. For example, modeling may involve converting a tabular representation of the data to a graph-based representation. Often extracts from relational databases are modeled and converted to Linked Data to more rapidly integrate datasets from different authorities or with other open source datasets. During the data modeling process, stakeholders are encouraged to describe how objects are related. The subject matter expert is recording how various objects are related, using standard vocabularies wherever possible. Best practices for using <a href="#VOCABULARIES">standard vocabularies<a/> are detailed later in this document. In Linked Data, the data schema is represented with the data itself. This mechanism of self-describing data contrasts with the relational approach where external documents (e.g., data dictionaries) and diagrams (e.g., entity relationship diagrams, logical schemas) describe the data.
+Linked Data modeling involves data going from one model to another. For example, modeling may involve converting a tabular representation of the data to a graph-based representation. Often extracts from relational databases are modeled and converted to Linked Data to more rapidly integrate datasets from different authorities or with other open source datasets. During the data modeling process, stakeholders are encouraged to describe how objects are related. The subject matter expert is recording how various objects are related, using standard vocabularies wherever possible. Best practices for using <a href="#VOCABULARIES">standard vocabularies</a> are detailed later in this document. In Linked Data, the data schema is represented with the data itself. This mechanism of self-describing data contrasts with the relational approach where external documents (e.g., data dictionaries) and diagrams (e.g., entity relationship diagrams, logical schemas) describe the data.
</p>
<p>
@@ -409,13 +408,13 @@
HTML representation or a machine-readable Turtle). A publisher may supply zero or
more representations of the resource identified by that URI. However, there is a clear
benefit to data users in providing at least one machine-readable representation. More information
-about serving different representations of a resource can be found in [[COOLURIS]]</a>.
+about serving different representations of a resource can be found in [[COOLURIS]].
</p>
<p class="highlight"><b>A URI structure will not contain anything that could change</b><br />
It is good practice that URIs do not contain anything that could easily change or that is expected to change like session tokens or other state information. URIs should be stable and reliable in order to maximize the possibilities of reuse that Linked Data brings to users. There must be a balance between making URIs
readable and keeping them more stable by removing descriptive information that will likely
-change. For more information on this see <a href="http://www.w3.org/TR/webarch/#uri-persistence">Architecture of the World Wide Web: URI Persistence</a>.
+change. For more information on this see <a href="http://www.w3.org/TR/webarch/#URI-persistence">Architecture of the World Wide Web: URI Persistence</a>.
</p>
<p class="highlight"><b>URI Opacity</b><br />
@@ -477,7 +476,7 @@
design considerations on how to URIs can be used to publish public sector reference data;</li>
<!--<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li> -->
- <li> <a href="http://philarcher.org/diary/2013/uripersistence/">Study on Persistent URIs</a> with identification of best practices and recommendations on the topic for the Member States and the European Commission</li>[[PURI]]
+ <li> <a href="http://philarcher.org/diary/2013/uripersistence/">Study on Persistent URIs</a> with identification of best practices and recommendations on the topic for the Member States and the European Commission [[PURI]]</li>
<li> <a href="http://www.pilod.nl/wiki/Bestand:D1-2013-09-19_Towards_a_NL_URI_Strategy.pdf">Towards a <abbr title="Netherlands">NL</abbr> URI Strategy</a> </li>
</ul>
@@ -496,7 +495,7 @@
<h3>Internationalized Resource Identifiers</h3>
-<p>Stakeholders who are planning to create URIs using characters that go beyond the subset defined in [[RFC3986]]</a> are encouraged to reference <a href='http://www.w3.org/TR/ld-glossary/index.html#iri'>IRI</a>s. Defined in (<a href="http://tools.ietf.org/html/rfc3987">RFC 3987</a>), IRI is a protocol element that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore used to mint identifiers that use a wider set of characters than the one defined in [[RFC3986]]</a>.
+<p>Stakeholders who are planning to create URIs using characters that go beyond the subset defined in [[RFC3986]] are encouraged to reference <a href='http://www.w3.org/TR/ld-glossary/#iri'>IRI</a>s. Defined in (<a href="http://tools.ietf.org/html/rfc3987">RFC 3987</a>), IRI is a protocol element that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore used to mint identifiers that use a wider set of characters than the one defined in [[RFC3986]].
</p>
<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain
@@ -555,6 +554,7 @@
<h3>How to Find Existing Vocabularies</h3>
+<p>
There are search tools that collect, analyze and index vocabularies and semantic data available online for efficient access. Search tools that use structured data represented as Linked Data include: (<a href="http://ws.nju.edu.cn/falcons/">Falcons</a>,
<a href="http://watson.kmi.open.ac.uk/WatsonWUI/">Watson</a>,
<a href="http://sindice.com/">Sindice</a>, <a href="http://swse.deri.org/">Semantic Web Search Engine</a>,
@@ -584,13 +584,12 @@
It is best practice to use or extend an existing vocabulary before creating a new vocabulary.
</p>
-<p>A basic vocabulary checklist:
+<p>A basic vocabulary checklist:</p>
<ul>
<li>ensure vocabularies you use are published by a trusted group or organization;</li>
<li>ensure vocabularies have permanent URIs; and </li>
<li>confirm the versioning policy.</li>
</ul>
-</p>
<p class="highlight"><b>Vocabularies MUST be documented</b><br />
@@ -760,7 +759,7 @@
<p class="highlight"><b>If designing a vocabulary, provide labels and descriptions if possible, in several languages, to make the vocabulary usable by a global audience.</b> </p>
-<p class="highlight"><b>Multilingual vocabularies may be found in the following formats</b> <br />
+<p class="highlight"><b>Multilingual vocabularies may be found in the following formats</b></p>
<ul>
<li>As a set of <code>rdfs:label</code> in which the language has been restricted (@en, @fr...). Currently, this is the most commonly used approach. </li>
@@ -782,8 +781,6 @@
<li>A list of codes and their corresponding URIs for the representation of language names is published and maintained by the official registration authority of ISO639-2, the US Library of Congress. [[ISO-639-1]], [[ISO-639-2]]</li>
-</p>
-
<!-- 19-Dec-2013 - Removed Lexvo.org reference in favor of reference to an authoritative list of URIs for languages maintained by the official registration authority of ISO639-2, the US Library of Congress. This is the same reference used in the DCAT Vocabulary.
<li> It could be also useful to use the <a href="http://www.lexinfo.net/lmf#">lexInfo</a> ontology where they provide stable resources for languages, such as <a href="http://lexvo.org/id/iso639-3/eng"><code>http://lexvo.org/id/iso639-3/eng</code></a> for English, or <a href="http://lexvo.org/id/iso639-3/cmn"><code>http://lexvo.org/id/iso639-3/cmn</code></a> for Chinese Mandarin. </li>
@@ -842,7 +839,7 @@
<li>Direct URI resolution ("follow your nose"), </li>
<li>a <a href="http://www.w3.org/TR/ld-glossary/#rest-api">RESTful API</a>, </li>
<li>a <a href="http://www.w3.org/TR/ld-glossary/#sparql-endpoint">SPARQL endpoint</a>, and/or </li>
-<li>via file download.
+<li>via file download.</li>
</ul>
</div>
</p>
@@ -872,18 +869,18 @@
The following checklist is intended to help organizations realize the benefits of publishing open government data, as well as, communicate to the public that you are serious about providing this data over time.
<ul>
-<li>Use multiple channels including mailing lists, blogs and newsletters to announce a newly published data set;</l>
+<li>Use multiple channels including mailing lists, blogs and newsletters to announce a newly published data set;</li>
<li>Publish a description for each published dataset using [[vocab-dcat]] or [[void]] vocabulary;</li>
<li>Define the frequency of data updates (as metadata);</li>
<li>Associate an appropriate license;</li>
<li>Plan and implement a persistence strategy;</li>
<li>Ensure data is accurate to the greatest degree possible;</li>
<li>Provide a form for people to report problematic data and give feedback;</li>
-<li>Provide a contact email address (alias) for those responsible for curating and publishing the data;</li>and
-<li>Ensure staff have the necessary training to respond in a timely manner to feedback.
+<li>Provide a contact email address (alias) for those responsible for curating and publishing the data; and</li>
+<li>Ensure staff have the necessary training to respond in a timely manner to feedback.</li>
</ul>
+</p>
</div>
-</p>
</section>
@@ -1142,7 +1139,7 @@
<a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088">Biplav Srivastava</a> (IBM India),
<a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group, Universidad Politécnica de Madrid, UPM, Spain), Martín Álvarez Espinar (CTIC-Centro Tecnológico, Spain),
<a href="http://www.about.me/david_wood/">David Wood</a> (3 Round Stones, USA),
-<a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR, USA), and
+<a href="http://mhausenblas.info/">Michael Hausenblas</a> (MapR, USA), and
our working group co-chair, <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov, UK). Please accept our apologies in advance if we've inadvertantly omitted your name as many people provided valuable feedback and were instrumental in the production of this best practices publication.
</p>
<p>