--- a/bp/index.html Fri Mar 15 10:05:14 2013 +0100
+++ b/bp/index.html Sun Mar 17 14:41:29 2013 +0100
@@ -20,7 +20,7 @@
<section id="abstract">
<p>
-This document provides best practices for creating, publishing and announcing open government content as Linked Data. Guidance on the life cycle of a Linked Data project, beginning with identification of suitable data sets, vocabulary selection, URI naming conventions through publication of data sets is included. 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.
+This document provides best practices for creating, publishing and announcing open government content as Linked Data. Guidance on the life cycle of a Linked Data project, beginning with identification of suitable data sets, vocabulary selection, URI naming conventions through publication of data sets is included. The goal of this document is to aid the publication of high quality <a href='http://www.w3.org/TR/gld-glossary/index.html#linked-open-data'>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.
</p>
</section>
@@ -46,9 +46,9 @@
This document aims to facilitate the adoption of Linked Open Data Principles for publishing open government data on the Web. Linked Data utilizes the Resource Description Framework (RDF)
<p>
-Linked Data 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 RDF family of syntaxes (e.g., RDF/XML, N3, Turtle and N-Triples) and HTTP URIs. RDF and Linked Data are not the same thing.
+<a href='http://www.w3.org/TR/gld-glossary/index.html#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 RDF family of syntaxes (e.g., RDF/XML, N3, Turtle and N-Triples) and HTTP URIs. RDF and Linked Data are not the same thing.
-Linked Data can be published by an person or organization behind the firewall or on the public Web. If Linked Data is published on the public Web, it is generally called Linked Open Data.
+Linked Data can be published by an person or organization behind the firewall or on the public Web. If Linked Data is published on the public Web, it is generally called <a href='http://www.w3.org/TR/gld-glossary/index.html#linked-open-data'>Linked Open Data</a>.
</p>
<h2>Background</h2>
@@ -149,7 +149,7 @@
<p>
Many government agencies publish statistical information on the public Web. The <a href="http://www.w3.org/TR/vocab-data-cube/">
-Data Cube Vocabulary</a> provides a means to do this using the <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#rdf'>Resource Description Framework (RDF)</a>. The model underpinning the Data Cube vocabulary is compatible with the cube model that underlies SDMX (Statistical Data and Metadata eXchange), an ISO standard for exchanging and sharing statistical data and metadata among organizations. The Data Cube vocabulary is a core foundation which supports extension vocabularies to enable publication of other aspects of statistical data flows or other multi-dimensional data sets.
+Data Cube Vocabulary</a> provides a means to do this using the <a href='http://www.w3.org/TR/gld-glossary/index.html#rdf'>Resource Description Framework (RDF)</a>. The model underpinning the Data Cube vocabulary is compatible with the cube model that underlies SDMX (Statistical Data and Metadata eXchange), an ISO standard for exchanging and sharing statistical data and metadata among organizations. The Data Cube vocabulary is a core foundation which supports extension vocabularies to enable publication of other aspects of statistical data flows or other multi-dimensional data sets.
</p>
<p class="todo"> To include: Phil suggests to include <a href="http://www.w3.org/QA/2012/07/conformance_for_vocabularies.html" target="_blank">Conformance for Vocabularies</a>.
@@ -168,7 +168,7 @@
Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</p>
<p class="highlight"><b>Identify relevant keywords in the dataset</b><br/>
- <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine. If you have raw data in <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#csv'>CSV</a>, the columns of the tables can be used for the searching process. <br/><br/>
+ <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine. If you have raw data in <a href='http://www.w3.org/TR/gld-glossary/#csv'>CSV</a>, the columns of the tables can be used for the searching process. <br/><br/>
Examples: commune, county, feature
</p>
@@ -482,7 +482,7 @@
schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, “the active involvement of information professionals in the management, including the preservation, of digital data for future use.” [Yakel, E (2007)] For a persistent identification scheme to provide a curation opportunity for a virtual resource, it must allow real-time resolution of that resource and also allow real-time administration of the identifier.
</p>
-<p>URI persistence is a matter of policy and commitment on the part of the URI owner. The choice of a particular URI scheme provides no guarantee that those URIs will be persistent or that they will not be persistent. HTTP [RFC2616] has been designed to help manage URI persistence. For example, HTTP redirection (using the 3xx response codes) permits servers to tell an agent that further action needs to be taken by the agent in order to fulfill the request (for example, a new URI is associated with the resource).
+<p>URI persistence is a matter of policy and commitment on the part of the URI owner. The choice of a particular URI scheme provides no guarantee that those URIs will be persistent or that they will not be persistent. HTTP [[RFC2616]] has been designed to help manage URI persistence. For example, HTTP redirection (using the 3xx response codes) permits servers to tell an agent that further action needs to be taken by the agent in order to fulfill the request (for example, a new URI is associated with the resource).
</p>
<p>In addition, content negotiation also promotes consistency, as a site manager is not required to define new URIs when adding support for a new format specification. Protocols that do not support content negotiation (such as FTP) require a new identifier when a new data format is introduced. Improper use of content negotiation can lead to inconsistent representations.
@@ -495,14 +495,14 @@
<p><i>This section on Internationalized Resource Identifiers focuses on using non-ASCII characters in URIs and provides guidelines for those interested in minting URIs in their own languages (German, Dutch, Spanish, Chinese, etc.)</i></p>
-<p>The URI syntax defined in <a href="http://tools.ietf.org/html/rfc3986" target="_blank">RFC 3986</a> STD 66 (Uniform Resource Identifier (URI): Generic Syntax) restricts URIs to a small number of characters: basically, just upper and lower case letters of the English alphabet, European numerals and a small number of symbols. There is now a growing need to enable use of characters from any language in URIs.
+<p>The URI syntax defined in [[!RFC3986]]</a> STD 66 (Uniform Resource Identifier (URI): Generic Syntax) restricts URIs to a small number of characters: basically, just upper and lower case letters of the English alphabet, European numerals and a small number of symbols. There is now a growing need to enable use of characters from any language in URIs.
</p>
-<p>The purpose of this section is to provide guidance to government stakeholders who are planning to create URIs using characters that go beyond the subset defined in <a href="http://tools.ietf.org/html/rfc3986" target="_blank">RFC 3986</a>.
+<p>The purpose of this section is to provide guidance to government stakeholders who are planning to create URIs using characters that go beyond the subset defined in [[!RFC3986]]</a>.
</p>
<p>
-IRI (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new 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 be used to mint identifiers that use a wider set of characters than the one defined in <a href="http://tools.ietf.org/html/rfc3986" target="_blank">RFC 3986</a>.
+<a href='http://www.w3.org/TR/gld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new 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 be used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
</p>
<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the IETF in March 2003.
@@ -626,7 +626,7 @@
<li>Is the government data accessible for developers once it is published?</li>
-<li>Can the data be queried programmatically, e.g., through an <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#api'>Application Programming Interface</a> (API), <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#sparql-endpoint'>SPARQL endpoint</a>, other mechanism?</li>
+<li>Can the data be queried programmatically, e.g., through an <a href='http://www.w3.org/TR/gld-glossary/index.html#api'>Application Programming Interface</a> (API), <a href='http://www.w3.org/TR/gld-glossary/index.html#sparql-endpoint'>SPARQL endpoint</a>, other mechanism?</li>
<li>What is the vendor’s Service Level Agreement?</li>
@@ -719,7 +719,7 @@
<h3>Stability Properties</h3>
-<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government Linked Open Data, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
+<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government <a href='http://www.w3.org/TR/gld-glossary/index.html#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
<ul>
<li>Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward for a given data set.</li>
--- a/bp/respec-ref.js Fri Mar 15 10:05:14 2013 +0100
+++ b/bp/respec-ref.js Sun Mar 17 14:41:29 2013 +0100
@@ -9,7 +9,8 @@
berjon.biblio["VOID-GUIDE"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: http://www.w3.org/TR/void/";
berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
- berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html."
+ berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: http://www.w3.org/Protocols/rfc2616/rfc2616.html.";
+ berjon.biblio["RFC3986"] = "<cite><a href=\"http://tools.ietf.org/html/rfc3986\">Uniform Resource Identifier (URI): Generic Syntax</a></cite>, Berners-Lee, et al. January 2005. Internet RFC 3986. URL: <a href=\"http://tools.ietf.org/html/rfc3986\">http://tools.ietf.org/html/rfc3986</a>.";
// process the document before anything else is done
var refs = document.querySelectorAll('adef') ;
@@ -124,4 +125,4 @@
p.replaceChild(sp, item) ;
}
}
- } ;
\ No newline at end of file
+ } ;