--- a/bp/index.html Thu Dec 12 11:22:47 2013 +0100
+++ b/bp/index.html Thu Dec 12 13:23:39 2013 +0000
@@ -196,27 +196,61 @@
<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 <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. This document is unfinished and it is subject to change.
+This document sets out a series of best practices designed to facilitate
+development and delivery of open government data as Linked Data. The
+goal is to aid the publication of high quality <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data (LOD)</a>
+from government authorities, to compile the most relevant data management practices,
+to promote best practices for publishing Linked Open Data, and to warn against practices
+that are considered harmful. The following recommendations are offered to
+creators, maintainers and operators of Web sites publishing open government
+data.<del>This document is unfinished and it is subject to change.</del>
</p>
<h2>Audience</h2>
<p>
-Readers of this document are expected to be familiar with fundamental Web technologies such as <a href="http://www.w3.org/TR/ld-glossary/#hypertext-markup-language" target="blank">HTML</a>, <a href="http://www.w3.org/TR/ld-glossary/#uri" target="blank">URIs</a>, and <a href="http://www.w3.org/TR/ld-glossary/#hypertext-transfer-protocol" target="blank">HTTP</a>. The document is targeted at developers, government information management staff, website administrators.
+Readers of this document are expected to be familiar with fundamental Web technologies such
+as <a href="http://www.w3.org/TR/ld-glossary/#hypertext-markup-language">HTML</a>,
+<a href="http://www.w3.org/TR/ld-glossary/#uri">URIs</a>, and
+<a href="http://www.w3.org/TR/ld-glossary/#hypertext-transfer-protocol">HTTP</a>.
+The document is targeted at developers, government information management staff, Web site administrators.
</p>
<h2>Scope</h2>
<p>
-This document aims to facilitate the adoption of <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles" target="blank">Linked Open Data Principles</a> for publishing open government data on the Web. <a href="http://www.w3.org/TR/ld-glossary/#linked-data" target="blank">Linked Data</a> utilizes the Resource Description Framework [[!RDF-CONCEPTS]].
+<del>This document aims to facilitate the adoption of
+<a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Open Data Principles</a>
+for publishing open government data on the Web.
+<a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> utilizes
+the Resource Description Framework [[RDF-CONCEPTS]]. </del>
<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., <a href="http://www.w3.org/TR/ld-glossary/#rdf-xml" target="blank">RDF/XML</a>, <a href="http://www.w3.org/TR/ld-glossary/#n3" target="blank">N3</a>, <a href="http://www.w3.org/TR/ld-glossary/#turtle" target="blank">Turtle</a> and N-Triples) and <a href="http://www.w3.org/TR/ld-glossary/#http-uris" target="blank">HTTP URIs</a>. <a href="http://www.w3.org/TR/ld-glossary/#rdf" target="blank">RDF</a> and <a href="http://www.w3.org/TR/ld-glossary/#linked-data" target="blank">Linked Data</a> are not the same thing.
+<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 <a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a>
+(Resource Description Framework [[RDF-CONCEPTS]]).
+RDF can be written in a variety of syntaxes (e.g.
+<a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a>,
+<a href="http://www.w3.org/TR/ld-glossary/#n3">N3</a>,
+<a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> and N-Triples) and
+<a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>.
+<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 the same thing.
-Linked Data can be published by a 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 a person or organization behind a firewall or
+on the public Web. If Linked Data is published on the public Web, it is generally called Linked Open Data.
</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.
+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>
@@ -231,55 +265,91 @@
</p>
-->
-The following best practices are discussed in this document and listed here for convenience.
+<p>The following best practices are discussed in this document and listed here for convenience.</p>
-<!--drop this suggested by Dave R. <p class='stmt'><a href="#NOMINATE">NOMINATE A PILOT:</a> <br>Nominate a pilot project on Linked Open Data.
+<!--drop this suggested by Dave R. <p class='stmt'><a href="#NOMINATE">NOMINATE A PILOT:</a> <br />Nominate a pilot project on Linked Open Data.
</p> -->
-<p class='stmt'><a href="#WORKFLOW">CHOOSE A WORKFLOW:</a><br>Determine which workflow to use for your Linked Open Data use case.
+<p class='stmt'><a href="#WORKFLOW">CHOOSE A WORKFLOW:</a><br />Determine which workflow to use for your Linked Open Data use case.
</p>
-<p class='stmt'><a href="#SELECT">SELECT A DATA SET:</a> <br>Select a data set that provides benefit to others for re-use. Consider a data set that your organization collects unique information that when combined with other open data provides greater value. For example, publishing facilities that can then be linked with geographic information including postal codes is a popular example.
-</p>
-
-<p class='stmt'><a href="#PII">PERSONALLY IDENTIFIABLE DATA:</a><br> Do not Publish Personally Identifiable Information as Linked Open Data as it can potentially be misused. Examples of personally identifiable data include: individual names, national identification number, phone number and office extention, and drivers license number.
-</p>
-
-<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><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 <a href="http://www.w3.org/TR/ld-glossary/#vocabulary" target="blank">vocabularies</a> whenever possible.
+<p class='stmt'><a href="#SELECT">SELECT A DATASET:</a> <br />Select a dataset that provides
+benefit to others for re-use. Consider a dataset that is uniquely collected by your organization:
+information that when combined with other open data provides greater value. For example,
+publishing facilities that can then be linked with geographic information including post<del>al</del> codes is a popular example.
</p>
-<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 <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 <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 class='stmt'><a href="#PII">PERSONALLY IDENTIFIABLE DATA:</a><br /> Do not publish
+personally identifiable information as Linked Open Data as it can potentially be misused.
+Examples of personally identifiable data include: individual names, national
+identification numbers, phone numbers and office extensions, and driver's license numbers.
</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 <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data-cloud" target="blank">Linked Data Cloud</a>.
+<p class='stmt'><a href="#LICENSE">ASSOCIATE A LICENSE:</a> <br />Associate an appropriate open
+license with the published data. People will only reuse data when there is a clear, acceptable license associated with it.
</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).
+<p class='stmt'><a href="#MODEL">MODEL:</a> <br /><a href="http://www.w3.org/TR/ld-glossary/#modeling-process">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="#ANNOUNCE">ANNOUNCE:</a><br> Announce the Linked Open Data on multiple channels. Be sure to have a plan in place to handle timely feedback. Linked Open Data implies the public is looking at and using the data, so ensure you have people in place to handle the customer service and technical support required to support the global Web audience.
+<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">vocabularies</a> whenever possible.
</p>
-<p class='stmt'><a href="#NETWORK">NETWORK EFFECT:</a><br> Establish and manage the network effect by helping other data stewards. Support the use of Linked Open Data through guidance, pilot funding or technical assistance and know how.</p>
+<p class='stmt'><a href="#METADATA">BASIC METADATA:</a> <br />Always 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).
+</p>
-<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT:</a> <br>Publishing Linked Open Data on the Web implies a social contract. Associating a good open data license is necessary. Regular updates and maintenance is a requirement. A permanent identifier scheme is highly recommended. If authorities move or remove data that is published to the Web, third party applications or mashups can break which is clearly undesireable.
+<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 <a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>
+as names for your objects. Give careful consideration to the <a href="http://www.w3.org/TR/ld-glossary/#uri">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 that it provides
+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">RESTful API</a>,
+a <a href="http://www.w3.org/TR/ld-glossary/#sparql-endpoint">SPARQL endpoint</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 valuable, however,
+interlinked data is suddenly very valuable. There are many popular datasets, 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">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 dataset(s).
+</p>
+
+<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE:</a><br /> Announce the Linked Open Data on
+multiple channels. Be sure to have a plan in place to handle timely feedback. Linked Open Data implies
+the public is looking at and using the data, so ensure you have people in place
+to handle the customer service and technical support required to support the global Web audience.
+</p>
+
+<p class='stmt'><a href="#NETWORK">NETWORK EFFECT:</a><br /> Establish and manage the
+network effect by helping other data stewards. Support the use of Linked Open Data through guidance,
+pilot funding or technical assistance and know how.</p>
+
+<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT:</a> <br />Publishing Linked Open Data on the Web
+implies a social contract. Associating a good open data license is necessary. Regular updates and
+maintenance is a requirement. A permanent identifier scheme is highly recommended. If authorities move
+or remove data that is published to the Web, third party applications or mashups can break, which is clearly undesirable.
</p>
</section>
@@ -289,7 +359,15 @@
<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 (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.
+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.
@@ -297,7 +375,11 @@
<ul>
<li>
- <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>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 (W3C) which 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) Maintain.
</p>
</li>
@@ -308,7 +390,13 @@
<ul>
<li>
- <p>According to Hausenblas et al. [[HAUSENBLAS]] existing data management approaches assume control over schema, data and data generation, which is not the case in the Web because it is open, de-centralised environment. Based on their experience in Linked Data publishing and consumption over the past years, they have identify involved parties and fundamental phases, which provide for a multitude of so called Linked Data life cycles that consists in the following steps: (1) data awareness, (2) modeling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.
+ <p>According to Hausenblas et al. [[HAUSENBLAS]] existing data management approaches
+assume control over schema, data and data generation, which is not the case in the
+Web because it is open, de-centralized environment. Based on their experience in
+Linked Data publishing and consumption over the past years, they identify involved
+parties and fundamental phases, which provide for a multitude of so called
+Linked Data life cycles that consist of the following steps: (1) data awareness,
+(2) modeling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.
</p>
</li>
</ul>
@@ -316,8 +404,10 @@
<ul>
<li>
- <p>Villazón-Terrazas et al. propose in [[BVILLAZON]] a first step to formalize their experience gained in the development of government Linked Data, into a preliminary set of methodological guidelines for generating, publishing and exploiting Linked Government Data. Their life cycle consists of the following activities: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
-
+ <p>Villazón-Terrazas et al. propose in [[BVILLAZON]] a first step to formalize their
+experience gained in the development of government Linked Data, into a preliminary set
+of methodological guidelines for generating, publishing and exploiting Linked Government Data.
+Their life cycle consists of the following activities: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
</p>
</li>
</ul>
@@ -330,34 +420,50 @@
<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="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> [[!vocab-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.
+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">Web of data</a>.
+Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
</p>
<p>
-The <a href="http://www.w3.org/TR/vocab-dcat/" target="_blank">Data Catalog Vocabulary (DCAT)</a> [[!vocab-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.
+For example, organizational structures and activities are often described by government authorities.
+The <a href="http://www.w3.org/TR/vocab-org/">Organization Ontology</a> [[vocab-org]] supports the
+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 neighboring information such as organizational activities.
</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> [[vocab-cube]] 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.
+The <a href="http://www.w3.org/TR/vocab-dcat/">Data Catalog Vocabulary (DCAT)</a> [[vocab-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/">
+Data Cube Vocabulary</a> [[vocab-cube]] provides a means to do this using the
+<a href="http://www.w3.org/TR/ld-glossary/#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 datasets.
</p>
</section>
-<!--<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 id='conformance'>
+<section id='conformanceForVocabs'>
<h2>Conformance for Vocabularies</h2>
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>
-<li>all classes and properties defined in the vocabulary are used in a way consistent with the semantics declared in its specification;</li>
+<li>the classes and properties defined in the vocabulary are used in a way consistent with the semantics declared in its specification;</li>
<li> it does not use terms from other vocabularies instead of ones defined in the vocabulary that could reasonably be used.</li>
@@ -365,14 +471,14 @@
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 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:
<ul>
-<li> a minimum set of terms that must be used;</li>
-<li> classes and properties not covered in the vocabulary; </li>
-<li> controlled vocabularies or URI sets as acceptable values for properties.</li>
+<li>a minimum set of terms that must be used;</li>
+<li>classes and properties not covered in the vocabulary; </li>
+<li>controlled vocabularies or URI sets as acceptable values for properties.</li>
</ul>
</section>
@@ -382,35 +488,47 @@
<section id='LINK'>
<h2>Vocabulary Discovery Checklist</h2>
-<p>The following checklist is a guide to helping developers determine whether an existing vocabulary would be a reasonable candidate for use by a government authority.
+<p>The following checklist is a guide to helping developers determine whether an
+existing vocabulary would be a reasonable candidate for use by a government authority.
</p>
-<p class="highlight"><b>Specify the domain</b><br/>
-<i>What it means:</i> Identify the domain scope of the vocabulary <br/>
-<i>Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</i> </p>
+<p class="highlight"><b>Specify the domain</b><br />
+<i>What it means:</i> Identify the domain scope of the vocabulary <br />
+<i>Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organization.</i> </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. <br/><br/>
+<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 the
+searching process using a Semantic Web search engine. <br /><br />
<!-- 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.-->
<i>Examples: commune, county, feature. </i>
</p>
-<p class="highlight"><b>Searching for a vocabulary in one specific language</b><br/>
+<p class="highlight"><b>Searching for a vocabulary in one specific language</b><br />
<i>What it means:</i> Many of the available vocabularies are in English. You may be aware of having a vocabulary in your own language.
Consider this issue as it may restrict your search. Sometimes it might be useful to translate some of the keywords to English.
</p>
-<p class="highlight"><b>How to find vocabularies</b><br/>
- <i>What it means:</i>There are some specific search tools (<a href="http://ws.nju.edu.cn/falcons/" target="_blank">Falcons</a>, <a href="http://watson.kmi.open.ac.uk/WatsonWUI/" target="_blank">Watson</a>, <a href="http://sindice.com/" target="_blank">Sindice</a>, <a href="http://swse.deri.org/" target="_blank">Semantic Web Search Engine</a>, <a href="http://swoogle.umbc.edu/" target="_blank">Swoogle</a>, <a href="http://schemapedia.com/" target="_blank">Schemapedia</a>) that collect, analyse and index vocabularies and semantic data available online for efficient access.<br/><br/>. Others include <a href="http://labs.mondeca.com/dataset/lov/" target="_blank">LOV</a> directory, <a href="http://prefix.cc">Prefix.cc</a> , <a href="http://bioportal.bioontology.org/">Bioportal (biological domain)</a> and the <a href="https://joinup.ec.europa.eu/catalogue/repository" target="_blanl">EC's Joinup platform.</a>
- <i>Examples: It is possible to perform a search on a relevant term or category present in your data.</i>
+<p class="highlight"><b>How to find vocabularies</b><br />
+ <i>What it means:</i>There are some specific search tools (<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>,
+<a href="http://swoogle.umbc.edu/">Swoogle</a>, <a href="http://schemapedia.com/">Schemapedia</a>) that collect,
+analyze and index vocabularies and semantic data available online for efficient access.<br /><br />.
+Others include the <a href="http://lov.okfn.org/">LOV</a> directory,
+<a href="http://prefix.cc">Prefix.cc</a>,
+<a href="http://bioportal.bioontology.org/">Bioportal (biological domain)</a> and the European Commission's
+<a href="https://joinup.ec.europa.eu/catalogue/repository">Joinup platform.</a>
+ <i>Examples: These tools make it possible to perform a search on a relevant term or category present in your data.</i>
</p>
-<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/>
- One popular catalogue is the: <a href="http://thedatahub.org/" target="_blank">Data Hub</a> (former CKAN).
-
+<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 catalogs. Some of these catalogs provide samples
+of how the underlying data was modeled and how it was used for.<br /><br />
+ One popular catalogue is the: <a href="http://datahub.io/">Data Hub</a>.
</p>
</section>
@@ -422,54 +540,72 @@
<h2>Vocabulary Selection Criteria</h2>
<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/>
- <i>What it means:</i> A vocabulary MUST be documented. This includes the liberal use of labels and comments, as well as appropriate language tags. The publisher must provide human-readable pages that describe the vocabulary, along with its constituent classes and properties. Preferably, easily comprehensible use-cases should be defined and documented.
-</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 <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: Contributor </code><br/>
- <code>Definition: An entity responsible for making contributions to the resource </code><br/>
- <code>Comment: Examples of a Contributor include a person, an organization, or a service.</code><br/>
+<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 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>
- <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/>
- <i>What it means:</i> If the vocabulary is used by other authoritative Linked Open Data sets that is helpful. It is in re-use of vocabularies that we achieve the benefits of Linked Open Data. Selected vocabularies from third parties should be already in use by other data sets, as shows that they are already established in the LOD community, and thus better candidates for wider adoption and reuse. <br/><br/>
- For example: An analysis on the <a href="http://stats.lod2.eu/vocabularies" target="_blank">use of vocabularies</a> on the Linked Data cloud reveals that <a href="http://xmlns.com/foaf/0.1" target="_blank">FOAF</a> is reused by more than 55 other vocabularies.
+<p class="highlight"><b>Vocabularies MUST be documented</b><br />
+ <i>What it means:</i> A vocabulary MUST be documented. This includes
+the liberal use of labels and comments, as well as appropriate language tags. The
+publisher must provide human-readable pages that describe the vocabulary, along with
+its constituent classes and properties. Preferably, easily comprehensible use-cases should be defined and documented.
</p>
-<p class="highlight"><b>Vocabularies SHOULD be accessible for a long period</b><br/>
- <i>What it means:</i> The vocabulary selected should provide some guarantee of maintenance over a specified period, ideally indefinitely.
-</p>
-
-<p class="highlight"><b>Vocabularies SHOULD be published by a trusted group or organization</b><br/>
- <i>What it means:</i> Although anyone can create a vocabulary, it is always better to check if it is one person, group or authoritative organization that is responsible for publishing and maintaining the vocabulary.
+<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, the widely-used Dublin Core vocabulary (formally <code>DCMI Metadata Terms</code>)
+has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor">Contributor</a> which has a:<br />
+ <code>Label: Contributor </code><br />
+ <code>Definition: An entity responsible for making contributions to the resource </code><br />
+ <code>Comment: Examples of a Contributor include a person, an organization, or a service.</code><br />
</p>
-<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://lov.okfn.org/dataset/lov/details/vocabulary_geo.html" target="_blank">Geo W3C vocabulary</a> [[vocab-geo]] 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 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(s), e.g. Spanish and at least in English.
+ That is also very important as the documentation should be clear enough with
+appropriate tags 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">Contributor</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/>
- <i>What it means:</i> The publisher ideally will address compatibility of versions over time. Major changes to the vocabularies should be reflected on the documentation.
+<p class="highlight"><b>Vocabularies SHOULD be used by other datasets</b><br />
+ <i>What it means:</i> If the vocabulary is used by other authoritative Linked Open datasets that
+is helpful. It is in re-use of vocabularies that we achieve the benefits of Linked Open Data.
+Selected vocabularies from third parties should be already in use by other datasets, as this shows
+that they are already established in the LOD community, and thus better candidates for wider adoption and reuse. <br /><br />
+ For example: An analysis on the <a href="http://stats.lod2.eu/vocabularies">use of vocabularies</a> on
+the Linked Data cloud reveals that <a href="http://xmlns.com/foaf/0.1">FOAF</a> is reused by more than 55 other vocabularies.
</p>
+<p class="highlight"><b>Vocabularies SHOULD be accessible for a long period</b><br />
+ <i>What it means:</i> The vocabulary selected should provide some guarantee of maintenance over a specified
+period, ideally indefinitely.
+</p>
+
+<p class="highlight"><b>Vocabularies SHOULD be published by a trusted group or organization</b><br />
+ <i>What it means:</i> Although anyone can create a vocabulary, it is always better to check
+if it is one person, group or authoritative organization that is responsible for publishing and maintaining the vocabulary.
+</p>
+
+<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://lov.okfn.org/dataset/lov/details/vocabulary_geo.html">Geo W3C vocabulary</a> [[vocab-geo]]
+is one of the most used vocabularies for a 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 />
+ <i>What it means:</i> The publisher ideally will address compatibility of versions over time. Major
+changes to the vocabularies should be reflected in the documentation.
+</p>
</section>
<!-- << Vocabulary creation -->
@@ -478,52 +614,70 @@
<h2>Vocabulary Creation</h2>
-<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><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> ,
-<b>Accessible for a long period</b> ,
-<b>Link to other vocabularies by re-using elements rather than re-inventing</b> ,
+<b>self-descriptive </b>,
+<b>described in more than one language</b> (ideally),
+<b>accessible for a long period</b> ,
+<b>link to other vocabularies by re-using elements rather than re-inventing</b> ,
<b>on the Web at a stable URI using an open license </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/>
+<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 />
- For example: If we are minting new vocabulary terms from a particular government, we should define the URI of that particular vocabulary.
+ For example: If we are minting new vocabulary terms from a particular government, we
+should define the URI of that particular vocabulary.
</p>
-<p class="highlight"><b>URIs for properties with non-literal ranges</b><br/>
- <i>What it means:</i> Name all properties as verb senses, so that <a href="http://www.w3.org/TR/ld-glossary/#triple" target="blank">triples</a> may be actually read; e.g., <i>hasProperty</i> .
+<p class="highlight"><b>URIs for properties with non-literal ranges</b><br />
+ <i>What it means:</i> Name all properties as verb senses, so that
+<a href="http://www.w3.org/TR/ld-glossary/#triple">triples</a> may be actually read; e.g. <i>hasProperty</i> .
</p>
-<p class="highlight"><b>Vocabularies should be self-descriptive</b><br/>
+<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 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/>
+ 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, the widely-used Dublin Core vocabulary (formally <code>DCMI Metadata Terms</code>)
+has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor">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.</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"><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 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"><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/>
- <i>What it means:</i> It refers to the mechanism put in place by the publisher to always take care of backward compatibilities of the versions, the ways those changes affected the previous versions. Major changes of the vocabularies should be reflected on the documentation, in both machine or human-readable formats.
+<p class="highlight"><b>Vocabularies should provide a versioning policy</b><br />
+ <i>What it means:</i> It refers to the mechanism put in place by the publisher to always take
+care of backward compatibilities of the versions, the ways those changes affected the previous
+versions. Major changes of the vocabularies should be reflected on the documentation, in both machine or human-readable formats.
</p>
-<p class="highlight"><b>Vocabularies should provide documentation</b><br/>
- <i>What it means:</i> A vocabulary should be well-documented for machine readable (use of labels and comments; tags to language used). Also for human-readable, an extra documentation should be provided by the publisher to better understand the classes and properties, and if possible with some valuable use cases. <b>Provide human-readable documentation and basic metadata such as creator, publisher, date of creation, last modification, version number.</b>
+<p class="highlight"><b>Vocabularies should provide documentation</b><br />
+ <i>What it means:</i> A vocabulary should be well-documented for machine readable (use of labels and
+comments; tags to language used). Also for human-readable, an extra documentation should be provided by
+the publisher to better understand the classes and properties, and if possible with some
+valuable use cases. <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>Vocabulary should be published following available best practices</b><br/>
- <i>What it means:</i> <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, 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 class="highlight"><b>Vocabulary should be published following available best practices</b><br />
+ <i>What it means:</i> <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,
+it is recommended to follow available recipes for publishing RDF vocabularies e.g.
+<a href="http://www.w3.org/TR/swbp-vocab-pub/">Best Practice Recipes for Publishing RDF Vocabularies</a> [[bp-pub]].
</p>
</section>
@@ -531,10 +685,10 @@
<!-- Vocabulary Creation -->
<!--TODO: put this in other sections without mentioning 5-stars: recommendation of Sandro -->
-<!--<br/>
+<!--<br />
<b>Is your Linked Data Vocabulary 5-star?</b>
-<br/>
-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>. -->
+<br />
+Inspired by the 5-star linked data scale <a href="http://5stardata.info/">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">[[BV5STAR]]</a>. -->
<!--<p class="highlight">☆ <b>Publish your vocabulary on the Web at a stable URI using an open license.</b>
</p> -->
@@ -556,21 +710,39 @@
<section id="multilingual">
<h2>Multilingual Vocabularies</h2>
-<p class="highlight"><b>While designing a vocabulary, provide labels and descriptions if possible, in several languages, to make your vocabulary usable in multiple linguistic scopes.</b> </p>
+<p class="highlight"><b>While designing a vocabulary, provide labels and descriptions
+if possible, in several languages, to make your vocabulary usable in multiple linguistic scopes.</b> </p>
<p>
-This section provides some considerations when we are dealing with multilingualism in vocabularies. For more details on the multilingualism on the Web, see the <a href="http://www.w3.org/International/multilingualweb/lt/" target="_blank"> MultilingualWeb-LT Working Group</a> </p>
+This section provides some considerations when we are dealing with multilingualism
+in vocabularies. For more details on the multilingualism on the Web, see the
+<a href="http://www.w3.org/International/multilingualweb/lt/"> MultilingualWeb-LT Working Group</a> </p>
<p> We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
</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>
+ <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>
<!--remove this, suggested by Phil? 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 <code>ILI - inter-lingual-index-</code>, which consists of a set of concepts common to all categorizations).</li>
- <li>As a set of ontology + lexicon. This is an approach to 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 <a href="http://lexinfo.net/" target="_blank">lemon model</a>, an ontology of linguistic descriptions that is to be related with the concepts and properties in an ontology to provide lexical, terminological, morphosyntactic, 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> It could be also useful to use the <code>lexInfo</code> ontology available at <code>http://www.lexinfo.net/lmf#</code> where they provide stable resources for languages, such as <code>http://lexvo.org/id/iso639-3/eng </code> for English, or <code>http://lexvo.org/id/iso639-3/cmn</code> for Chinese Mandarin.
+ <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 <code>ILI - inter-lingual-index-</code>,
+which consists of a set of concepts common to all categorizations).</li>
+ <li>As a set of ontology + lexicon. This is an approach to 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 <a href="http://lexinfo.net/">lemon model</a>, an ontology of linguistic
+descriptions that is to be related with the concepts and properties in an ontology to provide
+lexical, terminological, morphosyntactic, 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> 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>
+<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>
@@ -581,28 +753,33 @@
<h2>Using SKOS to Create a Controlled Vocabulary</h2>
<div class='note'>
- [[SKOS-REFERENCE]] , which stands for Simple Knowledge Organization System, is a W3C standard, based on other Semantic Web standards (RDF and OWL), that provides a way to represent controlled vocabularies, taxonomies and thesauri. Specifically, SKOS itself is an OWL ontology and it can be written out in any RDF flavour.
+ SKOS, the Simple Knowledge Organization System [[SKOS-REFERENCE]], is a W3C standard,
+based on other Semantic Web standards (RDF and OWL), that provides a way to represent controlled
+vocabularies, taxonomies and thesauri. Specifically, SKOS itself is an OWL ontology and it can be written out in any RDF flavor.
</div>
-<p>The W3C SKOS standard defines a portable, flexible controlled vocabulary format that is increasingly popular, with the added benefit of a good entry-level step toward the use of Semantic Web technology. </p>
+<p>The W3C SKOS standard defines a portable, flexible controlled vocabulary format that is
+increasingly popular, with the added benefit of a good entry-level step toward the use of Semantic Web technology. </p>
<div class="highlight"> SKOS is appropriate in the following situations:
<ul>
<li>There is a need to publish a controlled list of terms or taxonomies having a special meaning for the domain.</li>
- <li> The complexity and formality of an OWL ontology is not appropriate (for example the terms are not themselves entities that will be richly described).</li>
+ <li> The complexity and formality of an OWL ontology is not appropriate (for
+example the terms are not themselves entities that will be richly described).</li>
</ul>
</div>
<div class="highlight"> In creating a SKOS vocabulary bear the following good practice in mind:
<li>Make a clear distinction between the collections of concepts (ConceptScheme) and the different individual concepts. </li>
- <li> Define when possible a different namespace for each <code>skos:ConceptScheme</code> </li>
- <li> Structure the concepts in the list using properties <code>skos:hasTopConcept</code>, <code>skos:broader</code>, <code>skos:narrower.</code> </li>
+ <li>Define when possible a different namespace for each <code>skos:ConceptScheme</code> </li>
+ <li>Structure the concepts in the list using properties <code>skos:hasTopConcept</code>, <code>skos:broader</code>, <code>skos:narrower.</code> </li>
<li>Consider defining a Class to represent all the skos:Concepts in your controlled list (this can facilitate declaration of properties that will use this list).</li>
- <li> Provide multilingual labels for the terms.</li>
+ <li>Provide multilingual labels for the terms.</li>
</ul>
</div>
-<p><i>Let's consider a list of equipments where the codes used are: A101="Police", A206="Post Office" and A504="Restaurant". With SKOS, we could define the following structure:</i></p>
+<p><i>Let's consider a list of equipment where the codes used are: A101="Police",
+A206="Post Office" and A504="Restaurant". With SKOS, we could define the following structure:</i></p>
<pre class="example">
@@ -629,67 +806,78 @@
rdfs:label "Type of Equipments"@en;
rdfs:label "Type d'equipements"@fr .
</pre>
-
-
</section>
<section id="howto">
<h2>Best Practice for choosing entity URIs</h2>
-<p class="informative"> <i>This is intended to be a best-practice guide for data publishers who map existing data to RDF. Assuming they have identified their entity types, and what attributes and relationships are in the data for each entity types, the question is what URIs to choose for the entities. The step-by-step guide should be followed for each entity type individually</i></p>
+<p class="informative"> <i>This is intended to be a best-practice guide for data publishers who
+map existing data to RDF. Assuming they have identified their entity types, and what
+attributes and relationships are in the data for each entity types, the question is what
+URIs to choose for the entities. The step-by-step guide should be followed for each entity type individually</i>.</p>
- <p class="highlight"><b>Scope note:</b> <br>
- This is only for choosing identifiers for existing data that is to be translated from a different format or storage technology to RDF. This isn't applicable for authoring fresh data.<br>
- <b>Assumption:</b> <br>
- The input data may change. Therefore, if there are no reliable identifiers/keys in the input, one may not be able to track identity over updates. For the same reason, creating synthetic keys in the conversion process is not possible -- if they're arbitrary, they won't survive inserts/deletes, and if they're based on the input (e.g., hashing some fields) then they won't survive updates to those fields.</p>
+ <p class="highlight"><b>Scope note:</b> <br />
+ This is only for choosing identifiers for existing data that is to be translated from a different format or
+storage technology to RDF. This isn't applicable for authoring fresh data.<br />
+ <b>Assumption:</b> <br />
+ The input data may change. Therefore, if there are no reliable identifiers/keys in the input, one may
+not be able to track identity over updates. For the same reason, creating synthetic keys in the
+conversion process is not possible — if they're arbitrary, they won't survive inserts/deletes,
+and if they're based on the input (e.g., hashing some fields) then they won't survive updates to those fields.</p>
<div class="note">
<ul >
- <li> If Unique Name Assumption doesn't hold for an ID, then don't rely on it too much. Example: Email addresses. A person can have multiple.</li>
- <li>Discuss "authority files", "master data", and how those should be RDFized first. Q: Does your organization or some other reputable body maintain master data or an authority file for the entity type? If so, is it RDFized? If not, can you get that RDFized first? Use their IDs if you can. Otherwise, <b>make your own and do a best-effort mapping.</b></li>
+ <li>If the Unique Name Assumption doesn't hold for an ID, then don't rely on it too much. Example: a person may have multiple email addresses.</li>
+ <li>Discuss "authority files", "master data", and how those should be RDFized first. Q: Does your
+organization or some other reputable body maintain master data or an authority file for the entity type? If
+so, is it RDFized? If not, can you get that RDFized first? Use their IDs if you can. Otherwise, <b>make
+your own and do a best-effort mapping.</b></li>
</ul>
-<b>Outcome options:</b> <br>
+<b>Outcome options:</b> <br />
<ol>
- <li> Mint your own URIs. Possibly link to existing URIs.</li>
- <li> Re-use existing URIs.</li>
- <li> Use blank nodes. Possibly link to existing URIs.</li>
- <li> Use literals.</li>
+ <li>Mint your own URIs. Possibly link to existing URIs.</li>
+ <li>Re-use existing URIs.</li>
+ <li>Use blank nodes. Possibly link to existing URIs.</li>
+ <li>Use literals.</li>
</ol>
</div>
-<p class="highlight"><b>Q: Is your goal to enrich an existing LOD dataset?</b> <br>
- That is, you want to provide users of an existing dataset with additional information about the entities described in that dataset? And use of your dataset on its own without that other dataset is not an important goal?<br>
-YQ: Can you map your entities to their URIs with very high reliability (by syntactic matching, manual verification, etc.)? <br>
- Y: Use their URIs directly.<br>
+<p class="highlight"><b>Q: Is your goal to enrich an existing LOD dataset?</b> <br />
+ That is, you want to provide users of an existing dataset with additional information
+about the entities described in that dataset? And use of your dataset on its own without
+that other dataset is not an important goal?<br />
+YQ: Can you map your entities to their URIs with very high reliability (by syntactic matching, manual verification, etc.)? <br />
+ Y: Use their URIs directly.<br />
N: Do a best-effort mapping from your entities to their URIs. Continue below regarding your URIs.
</p>
-<p class="highlight"><b>Q: Do the entities have existing unique, non-URI, IDs?</b> <br>
-YQ: Are they globally unique?<br>
- YQ: Is there an existing URI mapping for these IDs from a reliable party?<br>
- YQ: Do you have additional information about the entities beyond what they have?<br>
- Y: Mint your own URIs based on the existing ID, and map using a mapping property<br>
- N: Use their URIs directly.<br>
- N: Mint your own URI based on the existing ID by sticking it onto a unique base.<br>
-N: So you have only strings that are not guaranteed to be in a stable 1:1 correspondence with the entities. Use a blank node; make sure that there's a good skos:prefLabel, rdfs:label, dc:title, and other standard metadata properties.
+<p class="highlight"><b>Q: Do the entities have existing unique, non-URI, IDs?</b> <br />
+YQ: Are they globally unique?<br />
+ YQ: Is there an existing URI mapping for these IDs from a reliable party?<br />
+ YQ: Do you have additional information about the entities beyond what they have?<br />
+ Y: Mint your own URIs based on the existing ID, and map using a mapping property<br />
+ N: Use their URIs directly.<br />
+ N: Mint your own URI based on the existing ID by sticking it onto a unique base.<br />
+N: So you have only strings that are not guaranteed to be in a stable 1:1 correspondence with the entities. Use
+a blank node; make sure that there's a good skos:prefLabel, rdfs:label, dc:title, and other standard metadata properties.
</p>
-<p class="highlight"><b>Q: Can the entity be represented as one of the standard RDF datatypes (that is, it's a date, number, etc.)?</b> <br>
-YQ: Is the entity annotated with additional information beyond what the datatype represents?<br>
+<p class="highlight"><b>Q: Can the entity be represented as one of the standard RDF datatypes (that is, it's a date, number, etc.)?</b> <br />
+YQ: Is the entity annotated with additional information beyond what the datatype represents?<br />
N: Use a typed literal.
</p>
-<p class="highlight"><b>Q: Can you map to reliable remote URIs?</b> <br>
-Q: Do you have data about the entities beyond what's already available from the remote URIs?<br>
+<p class="highlight"><b>Q: Can you map to reliable remote URIs?</b> <br />
+Q: Do you have data about the entities beyond what's already available from the remote URIs?<br />
N: No? Then use the remote URIs.
</p>
-<p class="highlight"><b>Q: Data is on its own web page with permalink?</b> <br>
-Q: Can you deploy RDFa in the web page, or can you deploy Turtle via content negotiation on the same URI?<br>
+<p class="highlight"><b>Q: Data is on its own Web page with permalink?</b> <br />
+Q: Can you deploy RDFa in the Web page, or can you deploy Turtle via content negotiation on the same URI?<br />
YN: Use <code>permalink#{fragment}</code> pattern, where <code>{fragment}</code> might be "this", "id", "product", "user", etc.
</p>
@@ -700,55 +888,94 @@
<section id="HTTPURIS">
<h2>URI Construction</h2>
<!--<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:
+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 [[COOLURIS]]</li>
<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Designing URI</a> Sets for the UK Public Sector [[uk-govuri]]</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/" target="_blank">10 rules for persistence URI</a> </li>
- <li> <a href="http://www.w3.org/2013/04/odw/odw13_submission_14.pdf" target="_blank">Draft URI Strategy for the NL Public Sector</a> </li>
- <li> <a href="http://bit.ly/xJwA9g" target="_blank">Style Guidelines for Naming and Labelling Ontologies in the Multilingual Web</a> </li>
+ <li> <a href="http://philarcher.org/diary/2013/uripersistence/">10 rules for persistent URI</a> </li>
+ <li> <a href="http://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a> (PDF) </li>
+ <li> <a href="http://dcevents.dublincore.org/index.php/IntConf/dc-2011/paper/download/47/15">Style Guidelines for Naming and Labeling Ontologies in the Multilingual Web</a> (PDF)</li>
</ul>
<!--Removed suggestion of Boris
-<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to Cool URIs for the Semantic Web [[!COOL-SWURIS]] (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
+<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to Cool URIs for the Semantic Web [[COOL-SWURIS]] (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
</p> -->
<p>
-Many general-purpose guidelines exist for the URI designer to consider, including <a href="http://www.w3.org/TR/cooluris/" target="_blank">Cool URIs for the Semantic Web</a>, which provides guidance on how to use URIs to describe things that are not Web documents; <a href="http://www.cabinetoffice.gov.uk/resource-library/designing-uri-sets-uk-public-sector" target="_blank">Designing URI Sets for the UK Public Sector</a>, a document from the UK Cabinet offices that defines the design considerations on how to URIs can be used to publish public sector reference data; and (3) <a href="http://bit.ly/xJwA9g" target="_blank">Style Guidelines for Naming and Labelling Ontologies in the Multilingual Web</a> (PDF), which proposes guidelines for designing URIs in a multilingual scenario.
+Many general-purpose guidelines exist for the URI designer to consider, including
+<a href="http://www.w3.org/TR/cooluris/">Cool URIs for the Semantic Web</a>, which provides guidance on
+how to use URIs to describe things that are not Web documents;
+<a href="http://www.cabinetoffice.gov.uk/resource-library/designing-uri-sets-uk-public-sector">Designing URI
+Sets for the UK Public Sector</a>, a document from the UK Cabinet offices that defines the
+design considerations on how to URIs can be used to publish public sector reference data; and (3)
+<a href="http://dcevents.dublincore.org/index.php/IntConf/dc-2011/paper/download/47/15">Style
+Guidelines for Naming and Labeling Ontologies in the Multilingual Web</a> (PDF), which proposes
+guidelines for designing URIs in a multilingual scenario.
</p>
<h3>URI Design Principles</h3>
-<p>The Web makes use of the <a href="http://www.w3.org/TR/ld-glossary/#uri" target="blank">URI</a> (Uniform Resource Identifiers) as a single global identification system. The global scope of URIs promotes large-scale "network effects". Therefore, in order to benefit from the value of LD, government and governmental agencies need to identify their <a href="http://www.w3.org/TR/ld-glossary/#resource" target="blank">resources</a> using URIs. This section provides a set of general principles aimed at helping government stakeholders to define and manage URIs for their resources.</p>
+<p>The Web makes use of the <a href="http://www.w3.org/TR/ld-glossary/#uri">URI</a>
+as a single global identification system. The global scope of URIs promotes large-scale
+"network effects". Therefore, in order to benefit from the value of LD, government and governmental
+agencies need to identify their <a href="http://www.w3.org/TR/ld-glossary/#resource">resources</a> using
+URIs. This section provides a set of general principles aimed at helping government stakeholders
+to define and manage URIs for their resources.</p>
-<p class="highlight"><b>Use HTTP URIs</b><br>
-<i>What it means:</i> To benefit from and increase the value of the World Wide Web, governments and agencies SHOULD provide HTTP URIs as identifiers for their resources. There are many benefits to participating in the existing network of URIs, including linking, caching, and indexing by search engines. As stated in [[howto-lodp]], HTTP URIs enable people to "look-up" or "dereference" a URI in order to access a representation of the resource identified by that URI.
+<p class="highlight"><b>Use HTTP URIs</b><br />
+<i>What it means:</i> To benefit from and increase the value of the World Wide Web, governments and
+agencies SHOULD provide HTTP URIs as identifiers for their resources. There are many
+benefits to participating in the existing network of URIs, including linking, caching, and indexing
+by search engines. As stated in [[howto-lodp]], HTTP URIs enable people to "look-up" or
+"dereference" a URI in order to access a representation of the resource identified by that URI.
To benefit from and increase the value of the World Wide Web, data publishers SHOULD provide URIs as identifiers for their resources.
</p>
-<p class="highlight"><b>Provide at least one machine-readable representation of the resource identified by the URI</b><br>
-<i>What it means:</i> In order to enable HTTP URIs to be "dereferenced", data publishers have to set up the necessary infrastructure elements (e.g. TCP-based HTTP servers) to serve representations of the resources they want to make available (e.g. a human-readable 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>.
+<p class="highlight"><b>Provide at least one machine-readable representation of the resource identified by the URI</b><br />
+<i>What it means:</i> In order to enable HTTP URIs to be "dereferenced", data publishers have
+to set up the necessary infrastructure elements (e.g. TCP-based HTTP servers) to
+serve representations of the resources they want to make available (e.g. a human-readable
+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>.
</p>
-<p class="highlight"><b>A URI structure will not contain anything that could change</b><br>
-<i>What it means:</i> 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 [MDinURI] and <a href="http://www.w3.org/TR/cooluris/" target="_blank">Architecture of the World Wide Web: URI Opacity</a>.
+<p class="highlight"><b>A URI structure will not contain anything that could change</b><br />
+<i>What it means:</i> 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 [MDinURI] and
+<a href="http://www.w3.org/TR/webarch/#uri-opacity">Architecture of the World Wide Web: URI Opacity</a>.
</p>
-<p class="highlight"><b>URI Opacity</b><br>
-The Architecture of the World Wide Web [Jacobs], provides best practices for the treatment of URIs at the time they are resolved by a Web client:
+<p class="highlight"><b>URI Opacity</b><br />
+The Architecture of the World Wide Web [[webarch]], provides best practices for the treatment
+of URIs at the time they are resolved by a Web client:
<i>Agents making use of URIs SHOULD NOT attempt to infer properties of the referenced resource.</i>
-URIs SHOULD be constructed in accordance with the guidance provided in this document to ensure ease of use during development and proper consideration to the guidelines given herein. However, Web clients accessing such URIs SHOULD NOT parse or otherwise read into the meaning of URIs.
+URIs SHOULD be constructed in accordance with the guidance provided in this document
+to ensure ease of use during development and proper consideration to the guidelines given herein.
+However, Web clients accessing such URIs SHOULD NOT parse or otherwise read into the meaning of URIs.
</p>
-<p class="note"><b>W3C Technical Architecture Group (TAG)</b><br>
-The World Wide Web Consortium's (W3C) <a href="http://www.w3.org/2001/tag/" target="_blank">Technical Architecture Group (TAG)</a> is a special working group within the W3C, in charge of resolving issues involving general Web architecture. The group maintains a list of <a href="http://www.w3.org/2001/tag/#publications" target="_blank">publications</a> and findings, such as the architecture of the World Wide Web. [[!webarch]]</p>
+<p class="note"><b>W3C Technical Architecture Group (TAG)</b><br />
+The World Wide Web Consortium's (W3C's) <a href="http://www.w3.org/2001/tag/">Technical Architecture
+Group (TAG)</a> is a special working group within the W3C, in charge of resolving issues involving
+general Web architecture. The group maintains a list of <a href="http://www.w3.org/2001/tag/#publications">publications</a> and
+findings, such as the architecture of the World Wide Web. [[webarch]]</p>
-<p ><b>TAG advices on http issues</b><br>
-The TAG provides advice to the community that they may mint <a href="http://www.w3.org/TR/ld-glossary/#uniform-resource-identifier" target="_blank">http" URIs</a> for any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
+<p ><b>TAG advices on http issues</b><br />
+The TAG provides advice to the community that they may mint
+<a href="http://www.w3.org/TR/ld-glossary/#uniform-resource-identifier">HTTP URIs</a> for
+any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
<div class="highlight">
<ul>
@@ -760,7 +987,11 @@
</div>
<p>
- Linked Data and Semantic Web implementors have 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. Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [[Wood2010]]. Some issues remain unsettled and the TAG is most of the time involved to coordinate and make recommendations to implementors.
+ Linked Data and Semantic Web implementers have 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. Current implementations of
+the Persistent URL (PURL) server provide support for 303 URIs [[Wood2010]]. Some issues
+remain unsettled and the TAG is most of the time involved to coordinate and make recommendations to implementers.
</p>
</section>
@@ -770,7 +1001,7 @@
<section>
<h5>A Checklist for Constructing URIs</h5>
-<p>The following checklist is based in part on <a href="http://data.gov.uk/resources/uris" target="_blank">Creating URIs</a> (short; on the Web) and <a href="http://www.cabinetoffice.gov.uk/sites/default/files/resources/designing-URI-sets-uk-public-sector.pdf" target="_blank">Designing URI Sets for the UK Public Sector</a> (long; in PDF).
+<p>The following checklist is based in part on <a href="http://data.gov.uk/resources/uris">Creating URIs</a> (short; on the Web) and <a href="http://www.cabinetoffice.gov.uk/sites/default/files/resources/designing-URI-sets-uk-public-sector.pdf">Designing URI Sets for the UK Public Sector</a> (long; in PDF).
</p>
<ol type="1">
<li>
@@ -834,23 +1065,50 @@
<!-- Acknowledge D. Wood, "Reliable and Persistent Identification of Linked Data Elements" LED chapter, 2010 -->
-<p>Persistent identifiers are used by organizations interested in retaining addresses to information resources over the long term. Today, persistent identifiers are used to uniquely identify objects in the real world and concepts, in addition to information resources. For example, persistent identifiers have been created by the United Nations Food and Agriculture Organization (FAO) to provide URIs for major food crops. The National Center for Biomedical Ontology provides persistent identifiers to unify and address the terminology used in many existing biomedical databases.
+<p>Persistent identifiers are used by organizations interested in retaining addresses to information
+resources over the long term. Today, persistent identifiers are used to uniquely identify
+objects in the real world and concepts, in addition to information resources. For example, persistent
+identifiers have been created by the United Nations Food and Agriculture Organization (FAO) to
+provide URIs for major food crops. The National Center for Biomedical Ontology provides persistent identifiers
+to unify and address the terminology used in many existing biomedical databases.
</p>
<p>
-A Persistent URL (PURL) is an address on the World Wide Web that causes a redirection to another Web resource. If a Web resource changes location (and hence URL), a PURL pointing to it can be updated. A user of a PURL always uses the same Web address, even though the resource in question may have moved. PURLs may be used by publishers to manage their own information space or by Web users to manage theirs; a PURL service is independent of the publisher of information. PURL services thus allow the management of hyperlink integrity. Hyperlink integrity is a design trade-off of the World Wide Web, but may be partially restored by allowing resource users or third parties to influence where and how a URL resolves. A simple PURL works by responding to an HTTP GET request with a response
-of type 302 (“Found”). The response contains an HTTP “Location” header, the value of which is a URL that the client should subsequently retrieve via a new HTTP GET request.
+A Persistent URL (PURL) is an address on the World Wide Web that causes a redirection to another Web
+resource. If a Web resource changes location (and hence URL), a PURL pointing to it can be
+updated. A user of a PURL always uses the same Web address, even though the resource in question may
+have moved. PURLs may be used by publishers to manage their own information space or by Web users to
+manage theirs; a PURL service is independent of the publisher of information. PURL services thus allow the
+management of hyperlink integrity. Hyperlink integrity is a design trade-off of the World Wide Web,
+but may be partially restored by allowing resource users or third parties to influence where and how
+a URL resolves. A simple PURL works by responding to an HTTP GET request with a response
+of type 302 (“Found”). The response contains an HTTP “Location” header, the value of which is a
+URL that the client should subsequently retrieve via a new HTTP GET request.
</p>
<p>
-PURLs implement one form of persistent identifier for virtual resources. Other persistent identifier schemes include Digital Object Identifiers (DOIs), Life Sciences Identifiers (LSIDs) and INFO URIs. All persistent identification
-schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, <b>“the active involvement of information professionals in the management, including the preservation, of digital data for future use.”</b> [[yakel-07]] 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.
+PURLs implement one form of persistent identifier for virtual resources. Other persistent identifier
+schemes include Digital Object Identifiers (DOIs), Life Sciences Identifiers (LSIDs) and INFO URIs. All persistent identification
+schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation
+opportunities. Curation of virtual resources has been defined as, <b>“the active involvement
+of information professionals in the management, including the preservation, of digital data
+for future use.”</b> [[yakel-07]] 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.
+<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.
</p>
</section>
@@ -858,22 +1116,36 @@
<section id="HUMAN">
<h3>Internationalized Resource Identifiers</h3>
-<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, French, Chinese, etc.)</i></p>
+<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, French, Chinese, etc.)</i></p>
-<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>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 [[!RFC3986]]</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>
-<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>.
+<a href='http://www.w3.org/TR/ld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987">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 <a href="http://www.w3.org/TR/ld-glossary/#internet-engineering-task-force-ietf">IETF</a> in March 2003.
+<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain
+names was agreed by the <a href="http://www.w3.org/TR/ld-glossary/#internet-engineering-task-force-ietf">IETF</a> in March 2003.
</p>
-<p>Although there exist some standards focused on enabling the use of international characters in Web identifiers, government stakeholders need to take into account several issues before constructing such internationalized identifiers. This section is not meant to be exhaustive and we point the interested audience to <a href="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">An Introduction to Multilingual Web Addresses</a>, however some of the most relevant issues are following:
+<p>Although there exist some standards focused on enabling the use of international characters in Web
+identifiers, government stakeholders need to take into account several issues before constructing such internationalized identifiers.
+This section is not meant to be exhaustive and we point the interested audience to
+<a href="http://www.w3.org/International/articles/idn-and-iri/">An Introduction to Multilingual Web Addresses</a>,
+however some of the most relevant issues are following:
</p>
<ul>
@@ -895,11 +1167,26 @@
<!-- <p class='todo'>To Review: Bernadette Hyland</p> -->
<p>
-It is best practice to explicitly attach a license statement to each data set. Governments typically define ownership of works produced by government employees or contractors in legislation. It is beyond the charter of this working group to describe and recommend appropriate licenses for Open Government content published as Linked Data, however there are useful Web sites that offer detailed guidance and licenses. One valuable resource is the <a href="http://creativecommons.org/">Creative Commons</a> website. Creative Commons develops, supports, and stewards legal and technical infrastructure for digital content publishing.
+It is best practice to explicitly attach a license statement to each dataset. Governments typically
+define ownership of works produced by government employees or contractors in legislation. It is
+beyond the charter of this working group to describe and recommend appropriate licenses for
+Open Government content published as Linked Data, however there are useful Web sites that
+offer detailed guidance and licenses. One valuable resource is the <a href="http://creativecommons.org/">Creative
+Commons</a> Web site. Creative Commons develops, supports, and stewards legal
+and technical infrastructure for digital content publishing.
</p>
<p class="note">
-As an informative note, the UK and many former Commonwealth countries maintain the concept of the Crown Copyright. It is important to know who owns your data and to say so. The US Government designates information produced by civil servants as a U.S. Government Work, whereas contractors may produce works under a variety of licenses and copyright assignments. U.S. Government Works are not subject to copyright restrictions in the United States. It is critical for US government officials to know their rights and responsibilities under the Federal Acquisition Regulations (especially FAR Subpart 27.4, the Contract Clauses in 52.227-14, -17 and -20 and any agency-specific FAR Supplements) and copyright assignments if data is produced by a government contractor. It is recommended that governmental authorities publishing Linked Data review the relevant guidance for data published on the Web.
+As an informative note, the UK and many former Commonwealth countries maintain the concept of
+the Crown Copyright. It is important to know who owns your data and to say so. The US
+Government designates information produced by civil servants as a U.S. Government Work, whereas
+contractors may produce works under a variety of licenses and copyright assignments. U.S.
+Government Works are not subject to copyright restrictions in the United States. It
+is critical for US government officials to know their rights and responsibilities under the Federal
+Acquisition Regulations (especially FAR Subpart 27.4, the Contract Clauses in 52.227-14, -17 and -20 and
+any agency-specific FAR Supplements) and copyright assignments if data is produced by
+a government contractor. It is recommended that governmental authorities publishing
+Linked Data review the relevant guidance for data published on the Web.
</p>
</section>
@@ -910,11 +1197,18 @@
<!-- <p class='todo'>To drop must part of this section, Dave comments</p> -->
-<p>Within government agencies, hosting linked data may require submission and review of a security plan to the authority's security team. While security plan specifics will vary widely based on a range of factors like hosting environment and software configuration, the process for developing and getting a security plan approved can be streamlined if the appropriate advisors are involved early on in the process</p>
+<p>Within government agencies, hosting linked data may require submission and review
+of a security plan to the authority's security team. While security plan specifics will
+vary widely based on a range of factors like hosting environment and software
+configuration, the process for developing and getting a security plan approved can be
+streamlined if the appropriate advisors are involved early on in the process</p>
-
-
-<p>Security plans are typically comprised of a set of security controls, describing physical, procedural, technical and other processes and controls in a system which are in place to protect information access, availability and integrity, and for avoiding, counteracting and minimizing security risks. These are typically comprised of several layers, that can range from physical facility security, network and communications, to considerations of operating system, software, integration and many other elements. As such, there will typically be some common security controls which are inherited, and which may not be specific or unique to the linked data implementation, such as controls inherited from the hosting environment, whether cloud hosting provider, agency data center, et cetera. Additionally, some security controls will be inherited from the software vendors.</p>
+<p>Security plans are typically comprised of a set of security controls, describing physical, procedural,
+technical and other processes and controls in a system which are in place to protect
+information access, availability and integrity, and for avoiding, counteracting and minimizing security
+risks. These are typically comprised of several layers, that can range from physical
+facility security, network and communications, to considerations of operating system, software, integration
+and many other elements. As such, there will typically be some common security controls which are inherited, and which may not be specific or unique to the linked data implementation, such as controls inherited from the hosting environment, whether cloud hosting provider, agency data center, et cetera. Additionally, some security controls will be inherited from the software vendors.</p>
<p> Detailed considerations of security issues are beyond the scope of this document. </p>
@@ -931,21 +1225,30 @@
<!-- <p class='todo'>To Review: Bernadette Hyland </p> -->
<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.
+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 dataset(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>
<div class="note">
<ul class="highlight">
-+ Publish a description for each published data set using [[!vocab-dcat]] or [[void]] vocabulary;<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/>
+<li>Publish a description for each published dataset using [[vocab-dcat]] or [[void]] vocabulary;</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>
<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.
+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
+404s is for your organization to implement a persistence strategy.
</p>
</section>
@@ -957,26 +1260,29 @@
<!-- <p class='todo'>John Erickson (RPI)</p> -->
<p>
-Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The <code>PROV</code> Family of Documents [[!prov-o]] defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.
+Provenance is information about entities, activities, and people involved in producing a piece of
+data or thing, which can be used to form assessments about its quality, reliability or
+trustworthiness. The <code>PROV</code> Family of Documents [[prov-o]] defines a model,
+corresponding serializations and other supporting definitions to enable the inter-operable
+interchange of provenance information in heterogeneous environments such as the Web.
</p>
</section>
-
-
-
-
-
<!-- << STABILITY.overview -->
<section id="stability-prop">
<h3>Stability Properties</h3>
-<p>There are characteristics that influence the stability or longevity of useful <a href="http://www.w3.org/TR/ld-glossary/#open-government-data" target="blank">open government data</a>. Many of these properties are not unique to government <a href='http://www.w3.org/TR/ld-glossary/#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>
+<p>There are characteristics that influence the stability or longevity of useful
+<a href="http://www.w3.org/TR/ld-glossary/#open-government-data">open government data</a>. Many of
+these properties are not unique to government <a href='http://www.w3.org/TR/ld-glossary/#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>
+<li>Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward for a given dataset.</li>
<li>Plan for departmental names and organizations to change - discourage the use of embedding originating source as a component of the data file name and/or URI. This information can and should be included as metadata in the RDF itself.</li>
-<li>Basic metadata should accompany each data set including: correct MIME type, publishing organization and/or agency, creation date, modification date, version, contact email for the data steward(s).</li>
+<li>Basic metadata should accompany each dataset including: correct MIME type, publishing organization and/or agency, creation date, modification date, version, contact email for the data steward(s).</li>
</ul>
</section>
@@ -995,15 +1301,25 @@
<!-- ACK -->
<section class="appendix">
<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.
+ 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 - 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) , <a href="http://www.epimorphics.com" target="_blank">Dave Reynolds</a> and Phil Archer <a href="http://www.w3.org" target="_blank">(W3C / ERCIM)</a>.
+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">John Erickson</a> (Rensselaer Polytechnic Institute),
+<a href="http://3roundstones.com/about-us/leadership-team/david-wood/">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">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) ,
+<a href="http://www.epimorphics.com">Dave Reynolds</a> and
+Phil Archer <a href="http://www.w3.org/People/#phila">(W3C / ERCIM)</a>.
</p>
</section>
-
-
</body>
</html>