--- a/bp/index.html Wed Dec 18 09:12:10 2013 -0500
+++ b/bp/index.html Thu Dec 19 13:25:10 2013 -0500
@@ -13,7 +13,7 @@
<script class='remove'>
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "LC",
copyrightStart: "2012",
//lcEnd: "2013-12-19",
@@ -21,7 +21,7 @@
shortName: "bp",
//subtitle: "",
// if you wish the publication date to be other than today, set this
- publishDate: "2013-12-18",
+ publishDate: "2013-12-19",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
@@ -184,7 +184,22 @@
href: "http://www.npr.org/2013/05/22/185788651/the-first-web-page-amazingly-is-lost",
authors: ["Geoff Brumfiel"],
publisher: "National Public Radio"
- }
+ },
+ "ISO-639-1":
+ {
+ title: "ISO 639-1: Codes for the Representation of Names of Languages - Part 1: Two letter codes for languages",
+ href: "http://id.loc.gov/vocabulary/iso639-1.html",
+ authors: ["U.S. Library of Congress"],
+ publisher: "International Standards Organization (ISO)"
+ },
+ "ISO-639-2":
+ {
+ title: "ISO 639-2: Codes for the Representation of Names of Languages - Part 2: Alpha-3 Code for the Names of Lanuguages",
+ href: "http://id.loc.gov/vocabulary/iso639-2.html",
+ authors: ["U.S. Library of Congress"],
+ publisher: "International Standards Organization (ISO)"
+ }
+
}
};
@@ -203,7 +218,7 @@
<section id="abstract">
<p>
-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>. The following recommendations are offered to creators, maintainers and operators of Web sites.
+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>
<h2>Audience</h2>
@@ -223,11 +238,7 @@
<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
+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>
@@ -337,21 +348,28 @@
<h2>Model the Data</h2>
<p class="note">
-It is not within scope of this document to expand on the process of Linked Open Data modeling however, we highlight how Linked Data modeling differs from the traditional relational data modeling approach.
+It is not within scope of this document to expand on the process of Linked Open Data modeling however, we highlight how Linked Data differs from the traditional relational data modeling approach.
+</p>
+
+<h3>Participants in the Modeling Process</h3>
+<p>
+The modeling process for Linked Data requires participants who represent a range of concerns including the existing data workflow and policies. It is helpful to include one or more individuals who are familiar with the existing dataset(s) which is in many cases is some form of data extract from one or more systems. This person is typically a relational database administrator (DBA) or responsible for the program and/or application. Ideally, a Linked Data subject matter expert will facilitate the Linked Data modeling process, helping to make <i>implicit</i> relationships <i>explicit</i> using Linked Data principles.
+</p>
+
+<h3>The Differences</h3>
+
+<p>
+Generally, all data modeling requires an understanding of the category of database being used, for example relational or NoSQL. RDF databases are one of the many types of NoSQL databases and the only type based on an international family of standards.[[DWOOD2013]] Linked Data uses RDF as its data model because RDF is the international standard for representing data on the Web. It is built on well-established and widely deployed standards including <a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>. Thus, one important difference between relational databases versus Linked Data is in the use of international standards for data interchange (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">, <a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> and <a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a>) and <a href="http://www.w3.org/TR/ld-glossary/#sparql">SPARQL</a> for query.
</p>
<p>
-During the data modeling phase, at least one individual familiar with the logical model and the schema of the dataset should be involved. Typically, this person is a database administrator or application developer very familiar with the meaning of the data. Additionally, including a Linked Data subject matter expert will assist in the modeling process.
-</p>
-
-</P
-The Linked Data modeling process differs from some other information management approaches by requiring the data modeler to represent data objects and how they are related. Linked Data modeling strives to produce a data representation that is application independent wherever possible. Over the last decade, publication strategies become more abstracted. Linked Data takes this abstraction slightly further by representing things and how they are related. Additional resources on data modeling are available on the Web and in publications.
+An additional difference is the requirement to define the context or semantic meaning of the data using <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Data Principles</a>. During the Linked Data modeling process, stakeholders specify how objects are related to each other. These relationships or context will then be "packaged" with the data itself. Linked Data modeling contrasts with relational modeling where external documents describe the data schema and visual diagrams describe the logical model. By packaging data and its context together, data is transformed into immediately useful information and is more readily accessible and available for reuse by others.
</p>
<h3> Provide Basic Metadata </h3>
<p>
-When modeling Linked Data, it is a best practice to provide basic <a href="http://www.w3.org/TR/ld-glossary/#metadata">metadata</a>, including MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s). In subsequent sections, further guidance on the use of vocabularies, as well as a vocabulary "checklist" are provided as further informative guidance as they play a key role in the Linked Data modeling process to encourage reuse.
+When modeling Linked Data<a href="http://www.w3.org/TR/ld-glossary/#metadata">metadata</a>, it is a best practice to include the MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, and contact email address, if this information is available and appropriate to the data. In subsequent sections we outline guidance for the use of vocabularies, as well as, a vocabulary "checklist" to assist in the modeling process.
</p>
</section>
@@ -655,27 +673,9 @@
<h3>Vocabulary Creation</h3>
<p>
-This section provides a set of informative considerations aimed at stakeholders who must develop their own vocabularies.
+This section provides a set of informative considerations aimed at stakeholders who decide they must develop their own vocabularies.
</p>
-<p>
-The following depicts the <a href="http://5stardata.info/">5-Star Scheme</a> for creating a vocabulary that is intended for widespread re-use:
-</p>
-
-<p class="highlight">☆ <b>Publish your vocabulary on the Web at a stable URI using an open license.</b>
-</p>
-
-<p class="highlight">☆☆ <b>Provide human-readable documentation and basic metadata such as creator, publisher, date of creation, last modification, version number.</b>
-</p>
-
-<p class="highlight">☆☆☆ <b>Provide labels and descriptions, if possible in several languages, to make your vocabulary usable in multiple linguistic scopes.</b>
-</p>
-
-<p class="highlight">☆☆☆☆ <b>Make your vocabulary available via its namespace URI, both as a formal file and human-readable documentation, using content negotiation.</b>
-</p>
-
-<p class="highlight">☆☆☆☆☆ <b>Link to other vocabularies by re-using elements rather than re-inventing.</b>
-</p>
<p class="highlight"><b>Define the URI of the vocabulary.</b><br />
@@ -727,7 +727,7 @@
creator, publisher, date of creation, last modification, version number.</b>
</p>
-<p class="highlight"><b>Vocabulary should be published following available best practices</b><br />
+<p class="highlight"><b>Vocabularies should be published following available best practices</b><br />
<b>Publish your vocabulary on the Web at a stable URI using an open license.</b>. One
of the goals is to contribute to the community by sharing the new vocabulary. To this end,
@@ -801,10 +801,17 @@
this approach is that semantics and linguistic information are kept separated. One can link several
lemon models in different natural languages to the same ontology.</li>
- <li> It could be also useful to use the <a href="http://www.lexinfo.net/lmf#">lexInfo</a> ontology
+ <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. [[ISO639-1]], [[ISO639-2]]</li>
+
+<!-- 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>
+-->
+
</ul>
<p class="note">The current trend is to follow the first approach, i.e. to use at least a <code>rdfs:label</code> and <code>rdfs:comment</code> for each term in the vocabulary.</p>
@@ -847,16 +854,17 @@
A major benefit of Linked Data is that it provides access to data for machines. Machines can use a variety of methods to read data including, but not limited to:
</p>
<ul>
-<li>A <a href="http://www.w3.org/TR/ld-glossary/#rest-api">RESTful API</a>, </li>
+<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.
</ul>
<p>
-SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. A family of standards of the World Wide Web Consortium. See also SPARQL 1.1 Overview [SPARQL-11].
+The SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. SPARQL is to RDF data what SQL is to a relational database. For more information, see the SPARQL 1.1 Overview [SPARQL-11].
</p>
<p>
-A SPARQL endpoint is a a service that accepts SPARQL queries and returns answers to them as SPARQL result sets. It is a best practice for datasets providers to give the URL of their SPARQL endpoint to allow access to their data programmatically or through a Web interface. A <a href="http://sparqles.okfn.org/">list of some SPARQL endpoints</a> may be found here.
+A SPARQL endpoint is a a service that accepts SPARQL queries and returns answers to them as SPARQL result sets. It is a best practice for datasets providers to give the URL of their SPARQL endpoint to allow access to their data programmatically or through a Web interface. A <a href="http://sparqles.okfn.org/">list of SPARQL endpoints</a> monitoring the availability, performance, interoperability and discoverability of SPARQL Endpoints is published by the Open Knowledge Foundation.
</p>
</section>
@@ -896,7 +904,7 @@
<h2>Social Contract of a Linked Data Publisher</h2>
<p>
-Government publishers of Linked Open Data are entering into a sort of "social contract" with users of their data. Publishers must recognize their responsibility in maintaining data once it is published. Key to the widespread use of the Web of Data is ensuring that the dataset(s) your organization publishes remains available where you say it will be and is maintained over time.
+Government publishers of Linked Open Data are entering into a sort of "social contract" with users of their data. Publishers must recognize their responsibility in maintaining data once it is published. Key to both access and reuse is ensuring that the dataset(s) your organization publishes remains available where you say it will be and is maintained over time.
</p>
<p>
@@ -1134,7 +1142,7 @@
The editors wish to gratefully acknowledge the considerable contributions to the Linked Data Best Practices document by the following people:
<a href="http://www.epimorphics.com">Dave Reynolds</a>, (Epimorphics,UK),
<a href="http://www.w3.org/People/#phila">Phil Archer</a>, (W3C / ERCIM, UK),
-<a href="http://www.linkedin.com/in/makxdekkers">Makx Deckers</a>, (Independent Consultant, Spain),
+<a href="http://www.linkedin.com/in/makxdekkers">Makx Dekkers</a>, (Independent Consultant, Spain),
<a href="http://logd.tw.rpi.edu/person/john_erickson">John Erickson</a> (Rensselaer Polytechnic Institute, USA),
<a href="http://nemo.inf.ufes.br/jpalmeida">João Paulo Almeida </a>, (Federal University of Espírito Santo, Brazil),
<a href="http://theodi.org/team/tom-heath">Tom Heath </a>, (Open Data Institute, UK),