--- a/bp/index.html Fri Dec 06 09:42:31 2013 +0100
+++ b/bp/index.html Fri Dec 06 10:13:45 2013 +0100
@@ -138,12 +138,18 @@
href: "http://download.e-bookshelf.de/download/0000/0067/81/L-G-0000006781-0002335618.pdf",
authors: ["David Wood"] ,
publisher: "Springer New York"
- }
+ },
+ "BHYLAND2011":{
+ title: "The Joy of Data - A Cookbook for Publishing Linked Government Data on the Web",
+ href: "http://dx.doi.org/10.1007/978-1-4614-1767-5_1",
+ authors: ["Bernadette Hyland", "David Wood"],
+ publisher: "Springer"
+ }
}
-
-
+
+
};
</script>
@@ -176,7 +182,7 @@
<section id="abstract">
<!--<h2>Purpose of the Document</h2> -->
<p>
-This document sets out a series of best practices designed to facilitate development and delivery of open government data as Linked Data. The goal of this document is to aid the publication of high quality Linked Open Data (LOD) from government authorities. This document aims to compile the most relevant data management practices, promoting best practices for publishing Linked Open Data and warns 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. 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" target="blank">Linked Open Data (LOD)</a> from government authorities. This document aims to compile the most relevant data management practices, promoting best practices for publishing Linked Open Data and warns against practices that are considered harmful. The following recommendations are offered to creators, maintainers and operators of Web sites publishing open government data.
</p>
<h2>Audience</h2>
@@ -227,28 +233,28 @@
<p class='stmt'><a href="#LICENSE">ASSOCIATE A LICENSE:</a> <br>Associate an appropriate open license with which to publish the data. People will only reuse data when there is a clear, acceptable license assocated with the data.
</p>
-<p class='stmt'><a href="#MODEL">MODEL:</a> <br>Model the data in an application-independent way. This means that if the data was originally organized for a specific application, you're likely to remove irrelevant content. In many cases, denormalizing the data may be necessary and is appropriate.
+<p class='stmt'><a href="#MODEL">MODEL:</a> <br><a href="http://www.w3.org/TR/ld-glossary/#modeling-process" target="blank">Model</a> the data in an application-independent way. This means that if the data was originally organized for a specific application, you're likely to remove irrelevant content. In many cases, denormalizing the data may be necessary and is appropriate.
</p>
-<p class='stmt'><a href="#STANDARD-VOCABULARIES">STANDARD_VOCABULARIES:</a> <br>Describe objects with standard vocabularies whenever possible.
+<p class='stmt'><a href="#STANDARD-VOCABULARIES">STANDARD_VOCABULARIES:</a> <br>Describe objects with standard <a href="http://www.w3.org/TR/ld-glossary/#vocabulary" target="blank">vocabularies</a> whenever possible.
</p>
-<p class='stmt'><a href="#METADATA">BASIC METADATA:</a> <br>Always provide basic metadata, including MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s).
+<p class='stmt'><a href="#METADATA">BASIC METADATA:</a> <br>Always provide basic <a href="http://www.w3.org/TR/ld-glossary/#metadata" target="blank">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).
</p>
<p class='stmt'><a href="#HUMAN">HUMAN READABLE:</a> <br>Provide human readable descriptions with your Linked Data.
</p>
-<p class='stmt'><a href="#HTTPURIS">HTTP URIs:</a><br> Create HTTP URIs as names for your objects. Give careful consideration to the URI naming strategy. Consider how the data will change over time and name as necessary.
+<p class='stmt'><a href="#HTTPURIS">HTTP URIs:</a><br> Create <a href="http://www.w3.org/TR/ld-glossary/#http-uris" target="blank">HTTP URIs</a> as names for your objects. Give careful consideration to the <a href="http://www.w3.org/TR/ld-glossary/#uri" target="blank">URI</a> naming strategy. Consider how the data will change over time and name as necessary.
</p>
-<p class='stmt'><a href="#MACHINE">MACHINE ACCESSIBLE:</a><br>A major benefit of Linked Data is providing access to data for machines. Machines can use a variety of methods to read data including, but not limited to: a RESTful API, SPARQL endpoints or download.
+<p class='stmt'><a href="#MACHINE">MACHINE ACCESSIBLE:</a><br>A major benefit of Linked Data is providing access to data for machines. Machines can use a variety of methods to read data including, but not limited to: a <a href="http://www.w3.org/TR/ld-glossary/#rest-api" target="blank">RESTful API</a>, <a href="http://www.w3.org/TR/ld-glossary/#sparql-endpoint" target="blank">SPARQL endpoints</a> or download.
</p>
<p class='stmt'><a href="#SERIALIZATION">DATA CONVERSION:</a><br> Convert the sources data to a Linked Data representation. This will typically mean mapping the source data to a set of RDF statements about entities described by the data. These statements can then be serialized into a range of RDF serializations including Turtle, N-Triples, JSON-LD, (X)HTML with embedded RDFa and RDF/XML.
</p>
-<p class='stmt'><a href="#LINK">LINKS ARE KEY:</a> <br>As the name suggests, Linked Open Data means the data is linked to other stuff. Data in isolation is rarely valauble, however, interlinked data is suddenly very valuable. There are many popular data sets, such as DBpedia that provide valuable data, including photos and geographic information. Being able to connect Linked Open Data from a government authority with DBpedia is quick way to show the value of adding content to the Linked Data Cloud.
+<p class='stmt'><a href="#LINK">LINKS ARE KEY:</a> <br>As the name suggests, Linked Open Data means the data is linked to other stuff. Data in isolation is rarely valauble, however, interlinked data is suddenly very valuable. There are many popular data sets, such as DBpedia that provide valuable data, including photos and geographic information. Being able to connect Linked Open Data from a government authority with DBpedia is quick way to show the value of adding content to the <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data-cloud" target="blank">Linked Data Cloud</a>.
</p>
<p class='stmt'><a href="#HOST">DOMAIN:</a> <br>Deliver Linked Open Data on an authoritative domain. Using an authoritative domain increases the perception of trusted content. Authoritative data that is regularly updated on a government domain is critical to uptake and reuse of the data set(s).
@@ -269,7 +275,7 @@
<h2> Linked Open Data Lifecycle </h2>
<!-- <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>
-The process of publishing Government Linked Open Data should be comprised of tractable and manageable steps, forming a life cycle in the same way Software Engineering uses life cycles in development projects. A GLD life cycle should cover all steps from identifying appropriate datasets to actually publishing and maintaining them. In the following paragraph three different life cycle models are presented, however it is evident that they all share common (and sometimes overlapping) characteristics in their constituents. For example, they all identify the need to specify, model and publish data in acceptable LOD formats. In essence, they capture the same tasks that are needed in the process, but provide different boundaries between these tasks.
+The process of publishing Government Linked Open Data (GLD) should be comprised of tractable and manageable steps, forming a life cycle in the same way Software Engineering uses life cycles in development projects. A GLD life cycle should cover all steps from identifying appropriate datasets to actually publishing and maintaining them. In the following paragraph three different life cycle models are presented, however it is evident that they all share common (and sometimes overlapping) characteristics in their constituents. For example, they all identify the need to specify, model and publish data in acceptable LOD formats. In essence, they capture the same tasks that are needed in the process, but provide different boundaries between these tasks.
</p>
<!--<p class="issue"> (Editors) - Please provide a brief description of lifecycle diagrams.
@@ -277,7 +283,7 @@
<ul>
<li>
- <p>Hyland et al. [BHYLAND] provide a six-step “cookbook” to model, create, publish, and announce government linked data. They highlight the role of the World Wide Web Consortium who is currently driving specifications and best practices for the publication of governmental data. Hyland et al. lifecycle consists of the following activities: (1) Identify, (2) Model, (3) Name, (4) Describe, (5) Convert, (6) Publish, and (7) Mantain.
+ <p>Hyland et al. [BHYLAND2011] provide a six-step “cookbook” to model, create, publish, and announce government linked data. They highlight the role of the World Wide Web Consortium who is currently driving specifications and best practices for the publication of governmental data. Hyland et al. lifecycle consists of the following activities: (1) Identify, (2) Model, (3) Name, (4) Describe, (5) Convert, (6) Publish, and (7) Mantain.
</p>
</li>