--- a/bp/index.html Thu Jun 06 09:46:15 2013 +0100
+++ b/bp/index.html Thu Jun 06 20:25:14 2013 +0200
@@ -13,7 +13,8 @@
<script type="text/javascript" src="respec-ref.js" class="remove"></script>
<script type="text/javascript" src="../respec/gld-bib.js" class="remove"></script>
<script type="text/javascript" src="respec-config.js" class="remove"></script>
- <script type="text/javascript" src="respec-contributor-hack.js" class="remove"></script>
+ <script type="text/javascript" src="respec-contributor-hack.js" class="remove"></script>
+
<link rel="stylesheet" type="text/css" href="local-style.css" />
</head>
<body>
@@ -47,7 +48,7 @@
<h2>Scope</h2>
<p>
-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).
+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.
@@ -121,7 +122,7 @@
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.
</p>
-<p class="todo"> (Editors) - Please provide a brief description of lifecycle diagrams.
+<p class="issue"> (Editors) - Please provide a brief description of lifecycle diagrams.
</p>
<ul>
@@ -142,7 +143,7 @@
<ul>
<li>
- <p>Villazón-terrazas et al. cpropose a Linked Data life cycle that consists of the following steps: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
+ <p>Villazón-terrazas et al. propose a Linked Data life cycle that consists of the following steps: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
</p>
</li>
</ul>
@@ -155,27 +156,28 @@
<h2>Vocabulary Selection</h2>
<p>
-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="https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#web-of-data">Web of data</a>. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
+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" target="_blank">Web of data</a>. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
</p>
<p>
-For example, organizational structures and activities are often described by government authorities. The <a href="http://www.w3.org/TR/vocab-org/" target="_blank">Organization Ontology</a> aims to support publishing of organizational information across a number of domains, as Linked Data. The Organizational Ontology is designed to allow domain-specific extensions to add classification of organizations and roles, as well as extensions to support neighbouring information such as organizational activities.
+For example, organizational structures and activities are often described by government authorities. The <a href="http://www.w3.org/TR/vocab-org/" target="_blank">Organization Ontology</a> [[ORG]] aims to support publishing of organizational information across a number of domains, as Linked Data. The Organizational Ontology is designed to allow domain-specific extensions to add classification of organizations and roles, as well as extensions to support neighbouring information such as organizational activities.
</p>
<p>
-The <a href="http://www.w3.org/TR/vocab-dcat/" target="_blank">Data Catalog Vocabulary (DCAT)</a> is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.
+The <a href="http://www.w3.org/TR/vocab-dcat/" target="_blank">Data Catalog Vocabulary (DCAT)</a> [[DCAT]] is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.
</p>
<p>
Many government agencies publish statistical information on the public Web. The <a href="http://www.w3.org/TR/vocab-data-cube/" target="_blank">
-Data Cube Vocabulary</a> provides a means to do this using the <a href="http://www.w3.org/TR/gld-glossary/index.html#rdf" target="_blank">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> [[QB]] provides a means to do this using the <a href="http://www.w3.org/TR/ld-glossary/#rdf" target="_blank">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>.
</p> -->
+<!-- section conformance -->
<section>
<h2>Conformance for Vocabularies</h2>
-A data interchange, however that interchange occurs, is conformant with a vocabulary if:
+A data interchange, however that interchange occurs, is <b>conformant</b> with a vocabulary if:
<ul>
<li>it is within the scope and objectives of the vocabulary;</li>
@@ -187,8 +189,8 @@
</ul>
A conforming data interchange:
<ul>
- <li>may include terms from other vocabularies;</li>
- <li> may use a non-empty subset of terms from the vocabulary.</li>
+ <li>MAY include terms from other vocabularies;</li>
+ <li> MAY use a non-empty subset of terms from the vocabulary.</li>
</ul>
A vocabulary profile is a specification that adds additional constraints
to it. Such additional constraints in a profile may include:
@@ -210,7 +212,7 @@
<p class="highlight"><b>Specify the domain</b><br/>
<i>What it means:</i>
-Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</p>
+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.
@@ -230,24 +232,30 @@
<p class="highlight"><b>Where to find existing vocabularies in datasets catalogues</b><br/>
<i>What it means:</i>Another way around is to perform search using the previously identified key terms in datasets catalogues. Some of these catalogues provide samples of how the underlying data was modelled and how it was used for.<br/><br/>
- Some existing catalogues are: <a href="http://thedatahub.org/" target="_blank">Data Hub</a> (former CKAN), <a href="http://labs.mondeca.com/dataset/lov/" target="_blank">LOV</a> directory, etc.
+ Some existing catalogues are: <a href="http://thedatahub.org/" target="_blank">Data Hub</a> (former CKAN), <a href="http://labs.mondeca.com/dataset/lov/" target="_blank">LOV</a> directory, <a href="http://prefix.cc">Prefix.cc</a> and <a href="http://bioportal.bioontology.org/">Bioportal</a>.
+
</p>
</section>
<!-- Discovery Checklist -->
<h2>Using SKOS to Create a Controlled Vocabulary</h2>
-<p class="todo"> (Editors) - Requested (12-Apr-2013, GLD WG F2F) - guidance on creating a simple controlled vocabulary using SKOS. Confirm this fits with the scope of BP document.
+<p class="issue"> (Editors) - Requested (12-Apr-2013, GLD WG F2F) - guidance on creating a simple controlled vocabulary using SKOS. Confirm this fits with the scope of BP document. <br/>
+ Some pointers: <br/>
+ + SKOS datasets: http://www.w3.org/2001/sw/wiki/SKOS/Datasets <br/>
+ + SKOS implementation records: http://www.w3.org/2006/07/SWD/SKOS/reference/20090315/implementation.html <br/>
+ + An introduction to SKOS: http://www.xml.com/pub/a/2005/06/22/skos.html
+
</p>
-<!-- << is your Linked Data Vocabulary 5 star? -->
+<!-- << is your Linked Data Vocabulary 5 star?
<p class="todo"> (Editors) - Update with attribution to Bernard Vatant's 5 Star Linked Data Vocabulary scheme (proposed).
</p>
-
+ -->
<section>
<h2>Is your Linked Data Vocabulary 5-star?</h2>
-Inspired by the 5-star linked data scale <a href="http://5stardata.info/" target="_blank">5-Star Scheme</a>, suggestions on creating a 5-star vocabulary <a href="http://blog.hubjects.com/2012/02/is-your-linked-data-vocabulary-5-star_9588.html" target="_blank">REF4</a>.
+Inspired by the 5-star linked data scale <a href="http://5stardata.info/" target="_blank">5-Star Scheme</a>, suggestions on creating a 5-star vocabulary <a href="http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html" target="_blank">[[BV5STAR]]</a>.
<p class="highlight">☆ <b>Publish your vocabulary on the Web at a stable URI using an open license.</b>
</p>
@@ -273,10 +281,10 @@
<section>
<h2>Vocabulary Selection Criteria</h2>
-This checklist aims to help in vocabulary selection, in summary:
-<li>Ensure vocabularies you use are published by a trusted group or organization</li>
-<li>Ensure vocabularies have permanent URIs</li>
-<li>Confirm the versioning policy </li>
+<p class="note"> This checklist aims to help in vocabulary selection, in summary: (1)-
+<b>Ensure vocabularies you use are published by a trusted group or organization</b>; (2)-
+<b>Ensure vocabularies have permanent URIs</b> and (3)
+<b>Confirm the versioning policy</b>.
</p>
<p class="highlight"><b>Vocabularies MUST be documented</b><br/>
@@ -286,18 +294,18 @@
<p class="highlight"><b>Vocabularies SHOULD be self-descriptive</b><br/>
<i>What it means:</i> Each property or term in a vocabulary should have a Label, Definition and Comment defined.
Self-describing data suggests that information about the encodings used for each representation is provided explicitly within the representation. The ability for Linked Data to describe itself, to place itself in context, contributes to the usefulness of the underlying data.<br/><br/>
-For example, popular vocabulary called DCMI Metadata Terms has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
- Label: Contributor<br/>
+For example, popular vocabulary called <code>DCMI Metadata Terms</code> has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
+ <code>Label: Contributorbr/>
Definition: An entity responsible for making contributions to the resource<br/>
- Comment: Examples of a Contributor include a person, an organization, or a service.<br/>
+ Comment: Examples of a Contributor include a person, an organization, or a service.<br/></code>
</p>
<p class="highlight"><b>Vocabularies SHOULD be described in more than one language</b><br/>
<i>What it means:</i> Multilingualism should be supported by the vocabulary, i.e., all the elements of the vocabulary should have labels, definitions and comments available in the government's official language, e.g., Spanish, and at least in English.
That is also very important as the documentation should be clear enough with appropriate tag for the language used for the comments or labels.<br/><br/>
For example, for the same term <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a></br>
- rdfs:label "Contributor"@en, "Colaborador"@es<br/>
- rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/>
+ <code>rdfs:label "Contributor"@en, "Colaborador"@es<br/>
+ rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/></code>
</p>
<p class="highlight"><b>Vocabularies SHOULD be used by other data sets</b><br/>
@@ -314,7 +322,7 @@
<p class="highlight"><b>Vocabularies SHOULD have persistent URLs</b><br/>
<i>What it means:</i> Persistent access to the server hosting the vocabulary, facilitating reusability is necessary.<br/><br/>
- Example: The <a href="http://www.w3.org/2003/01/geo/wgs84_pos#/" target="_blank">Geo W3C vocabulary</a> is one of the most used vocabulary for basic representation of geometry points (latitute/longitude) and has been around since 2009, always available at the same namespace.
+ Example: The <a href="http://lov.okfn.org/dataset/lov/details/vocabulary_geo.html" target="_blank">Geo W3C vocabulary</a>[[GEOW3C]] is one of the most used vocabulary for basic representation of geometry points (latitute/longitude) and has been around since 2009, always available at the same namespace.
</p>
<p class="highlight"><b>Vocabularies should provide a versioning policy</b><br/>
@@ -340,31 +348,35 @@
Partial or full deprecation
Cross-cutting issues: "Hit-by-bus" -->
-<p>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 because some recommendations for vocabulary selection also apply to vocabulary creation. Ensure new vocabularies you create are:
-<li>Self-descriptive </li>
-<li>Described in more than one language, ideally </li>
-<li>Accessible for a long period</li>
+<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 because some recommendations for vocabulary selection also apply to vocabulary creation.</i> </p>
+<p class="note"> Ensure new vocabularies you create are:
+<b>Self-descriptive </b>,
+<b>Described in more than one language, ideally </b> and
+<b>Accessible for a long period</b>
</p>
<p class="highlight"><b>Define the URI of the vocabulary.</b><br/>
- <i>What it means:</i> The URI that identifies your vocabulary must be defined. This is strongly related to the Best Practices described in section URI Construction.<br/><br/>
+ <i>What it means:</i> The URI that identifies your vocabulary must be defined. This is strongly related to the Best Practices described in section URI Construction.
+ <br/><br/>
+
For example: If we are minting new vocabulary terms from a particular government, we should define the URI of that particular vocabulary.
-</p>
+ </p>
+
<p class="highlight"><b>Vocabularies should be self-descriptive</b><br/>
<i>What it means:</i> Each property or term in a vocabulary should have a Label, Definition and Comment defined.
Self-describing data suggests that information about the encodings used for each representation is provided explicitly within the representation. The ability for Linked Data to describe itself, to place itself in context, contributes to the usefulness of the underlying data.<br/><br/>
-For example, popular vocabulary called DCMI Metadata Terms has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
- Label: Contributor<br/>
+For example, popular vocabulary called DCMI Metadata has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
+ <code>Label: Contributor <br/>
Definition: An entity responsible for making contributions to the resource<br/>
- Comment: Examples of a Contributor include a person, an organization, or a service.<br/>
+ Comment: Examples of a Contributor include a person, an organization, or a service.</code>
</p>
<p class="highlight"><b>Vocabularies should be described in more than one language</b><br/>
<i>What it means:</i> Multilingualism should be supported by the vocabulary, i.e., all the elements of the vocabulary should have labels, definitions and comments available in the government's official language, e.g., Spanish, and at least in English. That is also very important as the documentation should be clear enough with appropriate tag for the language used for the comments or labels.<br/><br/>
-For example, for the same term <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a></br>
- rdfs:label "Contributor"@en, "Colaborador"@es<br/>
- rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/>
+For example, for the same term <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank"><code>Contributor</code></a></br>
+ <code>rdfs:label "Contributor"@en, "Colaborador"@es<br/>
+ rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/></code>
</p>
<p class="highlight"><b>Vocabularies should provide a versioning policy</b><br/>
@@ -376,7 +388,7 @@
</p>
<p class="highlight"><b>Vocabulary should be published following available best practices</b><br/>
- <i>What it means:</i> One of the goals is to contribute to the community by sharing the new vocabulary. To this end, it is recommended to follow available recipes for publishing RDF vocabularies, e.g., <a href="http://www.w3.org/TR/swbp-vocab-pub/" target="_blank">Best Practice Recipes for Publishing RDF Vocabularies</a>.
+ <i>What it means:</i> One of the goals is to contribute to the community by sharing the new vocabulary. To this end, it is recommended to follow available recipes for publishing RDF vocabularies e.g., <a href="http://www.w3.org/TR/swbp-vocab-pub/" target="_blank">Best Practice Recipes for Publishing RDF Vocabularies</a>[[BP-PUB]].
</p>
<!-- Vocabulary Creation -->
@@ -384,33 +396,33 @@
<!-- TODO -->
-<p class="todo">Add references to Felix Sasaka's work on multilingual Web and new W3C WG
+<p class="todo">Add references to Felix Sasaka's work on multilingual Web and new W3C WG</p>
-<section>
+<section id="multilingual" class="informative">
<h2>Multilingual Vocabularies</h2>
<p>
-This section provides some considerations when we are dealing with multilingualism in vocabularies. We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
+This section provides some considerations when we are dealing with multilingualism in vocabularies.</p>
+<p> We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
</p>
<ul>
- <li>As a set of rdfs:label in which the language has been restricted (@en, @fr...). Currently, this is the most commonly used approach. It is also a best practice to always include an rdfs:label for which the language tag in not indicated. This term corresponds to the "default" language of the vocabulary</li>
- <li>As skos:prefLabel (or skosxl:Label), in which the language has also been restricted.</li>
+ <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. It is also a best practice to always include an <code>rdfs:label</code> for which the language tag in not indicated. This term corresponds to the <b>"default"</b>language of the vocabulary</li>
+ <li>As <code>skos:prefLabel</code> (or <code>skosxl:Label</code>), in which the language has also been restricted.</li>
<li>As a set of monolingual ontologies (ontologies in which labels are expressed in one natural language) in the same domain mapped or aligned to each other (see the example of EuroWordNet, in which wordnets in different natural languages are mapped to each other through the so-called ILI - inter-lingual-index-, which consists of a set of concepts common to all categorizations).</li>
- <li>As a set of ontology + lexicon. This represents the latest trend in the representation of linguistic (multilingual) information associated to ontologies. The idea is that the ontology is associated to an external ontology of linguistic descriptions. One of the best exponents in this case is the lemon model <a href="http://tia2011.crim.fr/Workshop-Proceedings/pdf/TIAW15.pdf" target="_blank">REF1</a>, <a href="http://lexinfo.net/" target="_blank">REF2</a>, an ontology of linguistic descriptions that is to be related with the concepts and properties in an ontology to provide lexical, terminological, morphosintactic, etc., information. One of the main advantages of 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>As a set of ontology + lexicon. This represents the latest trend in the representation of linguistic (multilingual) information associated to ontologies. The idea is that the ontology is associated to an external ontology of linguistic descriptions. One of the best exponents in this case is the lemon model <a href="http://tia2011.crim.fr/Workshop-Proceedings/pdf/TIAW15.pdf" target="_blank">[[TIAM]]</a>, <a href="http://lexinfo.net/" target="_blank">[[LEXINFO]]</a>, an ontology of linguistic descriptions that is to be related with the concepts and properties in an ontology to provide lexical, terminological, morphosintactic, etc., information. One of the main advantages of 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>
</ul>
-The current trend is to follow the first approach, i.e., to use rdfs:label and rdfs:comment for each term in the vocabulary.
+<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>
</section>
<!-- Multilingualism in vocabs >> -->
-<section>
-</section> <!-- VOCABULARY SELECTION >> -->
<!-- << URI CONSTRUCTION -->
-<section>
+<section class="informative">
<h2>URI Construction</h2>
-The following guidance is provided with the intention to address URI minting, i.e., URI creation for vocabularies, concepts and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include
+<p class="issue"> The editors will rephrase better this content and may extend it </p>
+The following guidance is provided with the intention to address URI minting, i.e., URI creation for vocabularies, concepts and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include:
<ul>
<li>Cool URIs for the Semantic Web [[!COOL-SWURIS]]</li>
<li><a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF)</li>
@@ -449,19 +461,22 @@
</p>
<p class="highlight"><b>Compliance with http-range-14</b><br>
-The World Wide Web Consortium's (W3C) Technical Architecture Group (TAG) attempted to settle a long standing debate about the use of URL resolution on 15 June 2005. Specifically, they decided:
+The World Wide Web Consortium's (W3C) Technical Architecture Group (TAG) attempted to settle a long standing debate about the use of URL resolution on 15 June 2005. Specifically, they decided: <p class="todo"> Statement not finished </p>
+</p>
-The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity:
-<ul>
+<p class="note"><b>TAG advices on http issues</b><br>
+The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
+<pre class="example">
<li> If an "http" resource responds to a GET request with a 2xx response, then the resource identified by that URI is an information resource;</li>
<li> If an "http" resource responds to a GET request with a 303 (See Other) response, then the resource identified by that URI could be any resource;</li>
<li> If an "http" resource responds to a GET request with a 4xx (error) response, then the nature of the resource is unknown.
</li>
</ul>
+
+ </pre>
-
-The practical implication of http-range-14 for Linked Data and Semantic Web implementors is the requirement to return an HTTP 303 (See Other) response when resolving HTTP URI identifiers for conceptual or physical resources (that is, for resources whose canonical content is non-informational in nature, c.f. [Wood2007]). Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [Wood2010]. Although the issue remains unsettled, and occasional attempts have been (and probably will be) made to revisit the TAG’s decision, however compliance with the http-range-14 decision until such time as it may be updated is recommended.
+The practical implication of http-range-14 for Linked Data and Semantic Web implementors is the requirement to return an HTTP 303 (See Other) response when resolving HTTP URI identifiers for conceptual or physical resources (that is, for resources whose canonical content is non-informational in nature, c.f. [[Wood2007]]). Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [[Wood2010]]. Although the issue remains unsettled, and occasional attempts have been (and probably will be) made to revisit the TAG’s decision, however compliance with the http-range-14 decision until such time as it may be updated is recommended.
</p>
</section>
@@ -568,7 +583,7 @@
</p>
<p>
-<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 used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
+<a href='http://www.w3.org/TR/ld-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 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.
@@ -641,16 +656,16 @@
<p>
Publishers of Linked Data enter into an implicit social contract with users of their data. Publishers should recognize the responsibility to maintain data once it is published by a government authority. Ensure that the Linked Open Data set(s) your organization publishes remains available where you say it will be. Here is a summary of best practices that relate to the implicit "social contract". Additional informational details are included for reference.
</p>
-
-<ul>
-<li>Publish a VoID description for each published data set;</li>
-<li>Associate metadata on the frequency of data updates;</li>
-<li>Associate a government appropriate license with all content your agency publishes if you wish to encourage re-use;</li>
-<li>Plan and implement a persistence strategy;</li>
-<li>Ensure data is accurate to the greatest degree possible;</li>
-<li>Publish an email address to report problematic data;</li>
-<li>Ensure the contact person or team responds to enquires via email or telephone, if necessary.</li>
-</ul>
+<div class="note">
+<ul class="highlight">
++ Publish a [[VoID]] description for each published data set;<br/>
++ Associate metadata on the frequency of data updates;<br/>
++ Associate a government appropriate license with all content your agency publishes if you wish to encourage re-use;<br/>
++ Plan and implement a persistence strategy;<br/>
++ Ensure data is accurate to the greatest degree possible;<br/>
++ Publish an email address to report problematic data;<br/>
++ Ensure the contact person or team responds to enquires via email or telephone, if necessary.<br/>
+</ul> </div>
<p>
Giving due consideration to your organization's URI strategy should be one of the first activities your team undertakes as they prepare a Linked Open Data strategy. Authoritative data requires the permanence and resolution of HTTP URIs. If publishers move or remove data that was published to the Web, third party applications or mashups may break. This is considered rude for obvious reasons and is the basis for the Linked Data "social contract." A good way to prevent causing HTTP 404's is for your organization to implement a persistence strategy.
@@ -664,7 +679,7 @@
<h2>Procurement</h2>
<p>
-This procurement checklist and <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
+This procurement checklist and <a href='http://www.w3.org/TR/lg-glossary'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
</p>
<h3>Overview</h3>
@@ -691,7 +706,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='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>Can the data be queried programmatically, e.g., through an <a href='http://www.w3.org/TR/ld-glossary/#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>
@@ -822,7 +837,7 @@
<h2>Acknowledgments</h2>
This document has been produced by the Government Linked Data Working Group, and its contents reflect extensive discussion within the Working Group as a whole.
<p>
-The editors gratefully acknowledge the many contributors to this Best Practices document including: <a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR), <a href="http://logd.tw.rpi.edu/person/john_erickson" target="_blank">John Erickson</a> (Rensselaer Polytechnic Institute), <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> (3 Round Stones), <a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Semantic Web - Modeca), Michael Pendleton (U.S. Environmental Protection Agency), <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088" target="_blank">Biplav Srivastava</a> (IBM India), <a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group), Martín Álvarez Espinar (CTIC-Centro Tecnológico), and <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov).
+The editors gratefully acknowledge the many contributors to this Best Practices document including: <a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR), <a href="http://logd.tw.rpi.edu/person/john_erickson" target="_blank">John Erickson</a> (Rensselaer Polytechnic Institute), <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> (3 Round Stones), <a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Semantic Web - Mondeca), Michael Pendleton (U.S. Environmental Protection Agency), <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088" target="_blank">Biplav Srivastava</a> (IBM India), <a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group), Martín Álvarez Espinar (CTIC-Centro Tecnológico), and <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov).
</p>
</section>