--- a/bp/index.html Mon Dec 16 20:47:55 2013 -0500
+++ b/bp/index.html Tue Dec 17 15:05:44 2013 -0500
@@ -158,6 +158,12 @@
authors: ["Boris Villazón-Terrazas", "et al."] ,
publisher: "Springer"
},
+ "PARCHER": {
+ title: "Study on Persistent URIs",
+ href: "http://philarcher.org/diary/2013/uripersistence/#recs",
+ authors: ["Phil Archer"] ,
+ },
+
"CSARVEN": {
title: "Towards Linked Statistical Data Analysis",
@@ -197,7 +203,7 @@
<section id="abstract">
<p>
-This document sets out a series of best practices designed to facilitate development and delivery of open government data as <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>. <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a> makes the World Wide Web into a global database, sometimes refered to as the "<a href="http://www.w3.org/TR/ld-glossary/#web-of-data">Web of Data</a>". Using <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Data Principles</a>, developers can query <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> from multiple sources at once and combine it without the need for a single common schema that all data shares. Prior to international data exchange standards for data on the Web, it was time consuming and difficult to build applications using traditional data management techniques. Using the Web of Data, developers can more easily integrate <a href="http://www.w3.org/TR/ld-glossary/#dataset-rdf">RDF datasets</a> to create useful Web applications. As more open government data is published on the Web, best practices are evolving too. The goal of this document is to compile the most relevant data management practices for the publication and use of of high quality data published by governments around the world as <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>. The following recommendations are offered to creators, maintainers and operators of Web sites.
+This document sets out a series of best practices designed to facilitate development and delivery of open government data as <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>. <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a> makes the World Wide Web into a global database, sometimes refered to as the "<a href="http://www.w3.org/TR/ld-glossary/#web-of-data">Web of Data</a>". Using <a href="http://www.w3.org/TR/ld-glossary/#linked-data-principles">Linked Data Principles</a>, developers can query <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a> from multiple sources at once and combine it without the need for a single common schema that all data shares. Prior to international data exchange standards for data on the Web, it was time consuming and difficult to build applications using traditional data management techniques. As more open government data is published on the Web, best practices are evolving too. The goal of this document is to compile the most relevant data management practices for the publication and use of of high quality data published by governments around the world as <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>. The following recommendations are offered to creators, maintainers and operators of Web sites.
</p>
<h2>Audience</h2>
@@ -216,9 +222,8 @@
<ul>
<li><a href="http://www.w3.org/TR/ld-glossary/#rdfa">RDFa</a>,</li>
<li><a href="http://www.w3.org/TR/ld-glossary/#json-ld">JSON-LD</a>,</li>
-<li><a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> , <a href="http://www.w3.org/TR/ld-glossary/#n-triples">N-Triples</a>, </li>
-<li><a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a>, and </li>
-<li><a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>. </li>
+<li><a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> , <a href="http://www.w3.org/TR/ld-glossary/#n-triples">N-Triples</a>, </li> and
+<li><a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a></li>
</ul>
@@ -258,7 +263,10 @@
<p class='stmt'><a href="#LICENSE">SPECIFY A LICENSE:</a> <br />Specify an appropriate open license with the published data.</p>
-<p class='stmt'><a href="#CONVERT">DATA CONVERSION:</a><br /> Convert data to a Linked Data representation, typically done by script or other automated processes.
+<p class='stmt'><a href="#CONVERT">DATA CONVERSION:</a><br /> Convert data to a Linked Data representation. This is typically done by script or other automated processes.
+</p>
+
+<p class='stmt'><a href="#PERSISTENCE">PERSISTENCE:</a><br /> Define a persistent URI policy and implementation plan to ensure the ongoing success and stability of publishing open government data as Linked Data.
</p>
<p class='stmt'><a href="#URIPRINCIPLES">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.
@@ -277,13 +285,10 @@
<p class='stmt'><a href="#DOMAIN">DOMAIN AND HOSTING:</a> <br />Deliver Linked Open Data on an authoritative domain.
</p>
-<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE:</a><br /> Announce the Linked Open Data on multiple channels and have a plan in place to support it over time.
+<p class='stmt'><a href="#ANNOUNCE">ANNOUNCE:</a><br /> Remember to announce new data sets and plan for regular updates and routine maintenance to realize the benefits of a sound open data policy.
</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>
@@ -293,7 +298,7 @@
<h2>Preparing to Publish Linked Open Data</h2>
<p>
-Preparation and setting expectations is crucial for any project's success. Prepare stakeholders with a discussion on the goals of Linked Data, as well as, the process of producing <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>. The concepts of data modeling will be familiar to information management professionals. The specifics and goals of Linked Open Data may be new to stakeholders who are used to traditional data management however, they are well-documented in W3C Recommendations, Notes and many peer reviewed publications [[WOOD2013]], [[howto-lodp]], [[BHYLAND2011]], [[BVILLAZON]]. Linked Data has entered the mainstream. It is used by governments large and small, the world's major search engines, international firms and agile startups.
+Preparation is crucial for success of an information management project. Providing stakeholders with the benefits of data sharing, as well as, the process of publishing and maintaining data sets for re-use useful. The concepts of data modeling will be familiar to information management professionals. The specifics and goals of Linked Open Data may be new to stakeholders who are used to traditional data management however, they are well-documented in W3C Recommendations, Notes and many peer reviewed publications [[WOOD2013]], [[howto-lodp]], [[BHYLAND2011]], [[BVILLAZON]]. Linked Data has entered the mainstream. It is used by governments large and small, the world's major search engines, international firms and agile startups.
</p>
<p>
@@ -382,29 +387,22 @@
<section id="LICENSE">
<h2>Specify an Appropriate License</h2>
-<p>
-Specify an appropriate open license with the published data. People will only reuse data when there is a clear, acceptable license associated with it. Governments typically define ownership of works produced by government employees or contractors in legislation.
+<p class="note">
+It is important to specify who owns data published on the Web and to explicitely connect that license with the data itself. Governmental authorities publishing open data are encouraged to review the relevant guidance for open licenses and copyright. Publishing Linked Open Data makes associating a license that travels with the data itself easy. Thus, people are more likely to reuse data when there is a clear, acceptable license associated with it.
</p>
<p>
-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.
+It is beyond the charter of this working group to describe or 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.
+<!-- NOTE TO FUTURE EDITORS: This was commented out as it was deemed too US centric.
+
+<p>
+The UK and many former Commonwealth countries maintain the concept of the Crown Copyright. 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.
</p>
+
+-->
+
</section>
@@ -420,16 +418,35 @@
<li><a href="http://www.w3.org/TR/ld-glossary/#rdfa">RDFa</a>,</li>
<li><a href="http://www.w3.org/TR/ld-glossary/#json-ld">JSON-LD</a>,</li>
<li><a href="http://www.w3.org/TR/ld-glossary/#turtle">Turtle</a> and <a href="http://www.w3.org/TR/ld-glossary/#n-triples">N-Triples</a>, </li>
-<li><a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a>, and </li>
-<li><a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>. </li>
+<li><a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a></li>
</ul>
</p>
<p>
Linked Data modelers and developers have certain reasons they prefer to use one RDF serialization over another. No one RDF serialization is better than the other. Benefits of using one over another include simplicity, ease of reading (for a human) and speed of processing.
</p>
+
+<p>
+As the name suggests, Linked Open Data means the data links 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 data from a government authority with DBpedia for example, 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>
+
</section>
+
+<!-- SOCIAL_CONTRACT -->
+<section id="SOCIAL-CONTRACT">
+<h2>Social Contract of a Linked Data Publisher</h2>
+
+<p>
+Government publishers of Linked Open Data are entering into a sort of "social contract" with users of their data. Publishers must recognize their responsibility in maintaining data once it is published. Key to the widespread use of the Web of Data is ensuring that the dataset(s) your organization publishes remains available where you say it will be and is maintained over time.
+
+<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 404s is for your organization to implement a persistence strategy. Below we provide an introduction to the best practice of defining a persistence strategy and implementation plan.
+</p>
+</section>
+
+
+
<!-- URI PRINCIPLES -->
<section id="URIPRINCIPLES">
<h2>URI Design Principles</h2>
@@ -472,18 +489,54 @@
<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>
+</section>
+
+
+
+<section id="URI-POLICY">
+<h2>URI Policy for Persistence</h2>
+
+<p>
+Defining and documenting a persistent URI policy and implementation plan is vital to the ongoing success and stability of publishing open government data.
</p>
-</h3>
+<p>
+The effect of changing or moving resources has the effect of breaking applications dependent upon it. Therefore, government authorities should define a persistence strategy and implementation plan to provide content using the same Web address, even though the resources in question may have moved. Persistent identifiers are used to retain addresses to information resources over the long term. Persistent identifiers are used to uniquely identify objects in the real world and concepts, in addition to information resources.
+</p>
+
+<p>
+The choice of a particular URI scheme provides no guarantee that those URIs will be persistent. URI persistence is a matter of policy and commitment on the part of the URI owner. 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>
+The <a href="http://en.wikipedia.org/wiki/Persistent_uniform_resource_locator"> PURL concept</a> allows for generalized URL curation of HTTP URIs on the World Wide Web. PURLs allow third party control over both URL resolution and resource metadata provision. A Persistent URL 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.
+</p>
+
+<p>
+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.
+</p>
+
+<p>
+The <a href="http://purlz.org"> Open Source PURLs Project</a> is used widely to run persistent identifier management sites. The Open Source PURLs Project is used by libraries, academic organizations, government agencies and non-government organizations around the world. For example, persistent URLs are used by the United Nations Food and Agriculture Organization (FAO) to provide URIs for major food crops. The National Center for Biomedical Ontology provides persistent URLs to unify and address the terminology used in many existing biomedical databases. The US Government Printing Office also uses persistent URLs to point to documents like the U.S. Budget that are deemed essential to a democratic, transparent government.
+</p>
+
+<p>
+Recently, a software project called <a href="http://w3id.org">Permanent Identifiers for the Web</a> emerged to provide a secure, permanent URL re-direction service for Web applications. The service operates in HTTPS-only mode to ensure end-to-end security. This means that it may be used for Linked Data applications that require high levels of security such as those found in the financial, medical, and public infrastructure sectors. A growing group of organizations that have pledged responsibility to ensure the operation of this website over time. Those interested in learning more are encouraged to contact the <a href="http://www.w3.org/community/perma-id/">W3C Permanent Identifier Community Group</a>.
+</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 identificationschemes 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>
+
</section>
<!-- URI CONSTRUCTION -->
<section id="HTTPURIS">
<h2>URI Construction</h2>
+
<p>
The following guidance is has been developed by organizations involved in URI strategy and implementation for government agencies:
<ul>
@@ -495,7 +548,7 @@
design considerations on how to URIs can be used to publish public sector reference data;</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/">10 rules for persistent URI</a> </li>
+ <li> <a href="http://philarcher.org/diary/2013/uripersistence/">Study on Persistent URIs</a> with identification of best practices and recommendations on the topic for the Member States and the European Commission</li>[[PARCHER]]
<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>
</ul>
@@ -513,44 +566,6 @@
</section>
-<section id="URI-POLICY">
-<h2>URI Policy for Persistence</h2>
-
-<p>Persistent identifiers are used to retain addresses to information resources over the long term. 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. The US Government Printing Office uses persistent identifiers to point to documents like the U.S. Budget that are deemed essential to a democratic, transparent government.
-</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.
-</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 identificationschemes 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>
-
-<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>
-
<section id="INTERNATIONAL">
<h2>Internationalized Resource Identifiers</h2>
@@ -608,7 +623,7 @@
</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>. CSARVENón-Capadisli propose in [[CSARVEN]] the RDF Data Cube Vocabulary makes it possible to discover and identify statistical data artifacts in a uniform way and presents a design and implementation approach using the Data Cube Vocabulary. 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.
+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 RDF Data Cube Vocabulary makes it possible to discover and identify statistical data artifacts in a uniform way.[[CSARVEN]] 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>
@@ -715,6 +730,25 @@
This section provides a set of informative considerations aimed at stateholder who need to create their own vocabularies. This section includes some items of the previous section because some recommendations for vocabulary selection also apply to vocabulary creation.
</p>
+<p>
+The following depicts the <a href="http://5stardata.info/">5-Star Scheme</a> for creating a vocabulary that is intended for widespread re-use:
+</p>
+
+<p class="highlight">☆ <b>Publish your vocabulary on the Web at a stable URI using an open license.</b>
+</p>
+
+<p class="highlight">☆☆ <b>Provide human-readable documentation and basic metadata such as creator, publisher, date of creation, last modification, version number.</b>
+</p>
+
+<p class="highlight">☆☆☆ <b>Provide labels and descriptions, if possible in several languages, to make your vocabulary usable in multiple linguistic scopes.</b>
+</p>
+
+<p class="highlight">☆☆☆☆ <b>Make your vocabulary available via its namespace URI, both as a formal file and human-readable documentation, using content negotiation.</b>
+</p>
+
+<p class="highlight">☆☆☆☆☆ <b>Link to other vocabularies by re-using elements rather than re-inventing.</b>
+</p>
+
<p class="highlight"><b>Define the URI of the vocabulary.</b><br />
The URI that identifies your vocabulary must be defined. This is strongly related to the Best Practices described in section URI Construction.<br /><br />
@@ -853,35 +887,6 @@
</section>
-
-<!-- Publish 5-Star Data -->
-<section id="5STAR">
-<h2>Publishing Data for Access and Reuse</h2>
-
-<p>While organizations around the globe are making very valuable steps in government transparency by publishing datasets in non-proprietary formats such as CSV and PDF, striving to publish authoritative data as <a href="http://www.w3.org/TR/ld-glossary/#5-star-linked-open-data">5 Star Linked Open Data</a> considerably helps developers combine datasets more accurately and quickly.
-</p>
-<p>
-As the name suggests, Linked Open Data means the data links 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>. This diagram of the <a href="http://5stardata.info/">5-Star Scheme</a> shows a pictorial image of the goals for structured data on the Web intended for widespread re-use:
-</p>
-
-<p class="highlight">☆ <b>Publish your vocabulary on the Web at a stable URI using an open license.</b>
-</p>
-
-<p class="highlight">☆☆ <b>Provide human-readable documentation and basic metadata such as creator, publisher, date of creation, last modification, version number.</b>
-</p>
-
-<p class="highlight">☆☆☆ <b>Provide labels and descriptions, if possible in several languages, to make your vocabulary usable in multiple linguistic scopes.</b>
-</p>
-
-<p class="highlight">☆☆☆☆ <b>Make your vocabulary available via its namespace URI, both as a formal file and human-readable documentation, using content negotiation.</b>
-</p>
-
-<p class="highlight">☆☆☆☆☆ <b>Link to other vocabularies by re-using elements rather than re-inventing.</b>
-</p>
-
-</section>
-
-
<!-- MACHINE ACCESSIBLE -->
<section id="MACHINE">
<h2>Machine Access to Data</h2>
@@ -924,39 +929,26 @@
<section id="ANNOUNCE">
<h2>Announce to the Public</h2>
-<p>
-Announce the Linked Open Data on multiple channels including mailing lists, blogs, newsletters and traditional fora. Be sure to have a plan in place to handle timely feedback. The public is looking at and counting on your open data, so ensure you have people in place to handle the customer service and technical support required to support the public audience.
-</p>
+<div class="note">
+The following checklist is intended to help organizations realize the benefits of publishing open government data, as well as, communicate to the public that you are serious about providing this data over time.
-The following is intended to help your organization announce useful new datasets and help fulfill the implicit social contract:
-</p>
-<div class="note">
<ul>
+<li>Use multiple channels including mailing lists, blogs and newsletters to announce a newly published data set;</l>
<li>Publish a description for each published dataset using [[vocab-dcat]] or [[void]] vocabulary;</li>
<li>Define the frequency of data updates (as metadata);</li>
<li>Associate an appropriate license;</li>
<li>Plan and implement a persistence strategy;</li>
<li>Ensure data is accurate to the greatest degree possible;</li>
-<li>Provide a form to give useful feedback. Forms help with structure;</li>
-<li>Publish an email address to report problematic data;</li>
-<li>Provide a contact email address (alias) to team members responsible for curating and publishing the data.</li>
+<li>Provide a form for people to report problematic data and give feedback;</li>
+<li>Provide a contact email address (alias) for those responsible for curating and publishing the data;</li>and
+<li>Ensure staff have the necessary training to respond in a timely manner to feedback.
</ul> </div>
+<!-- A request was made to include the CKAN DataHub however at the time of this WG Note's review, the site returned 503 - Service Unavailable, so it was (temporarily) omitted. http://datahub.io/
+
</section>
-<!-- SOCIAL_CONTRACT -->
-<section id="SOCIAL-CONTRACT">
-<h2>Social Contract of a Linked Data Publisher</h2>
-
-<p>
-Government publishers of Linked Open Data are entering into a sort of "social contract" with users of their data. Publishers must recognize their responsibility in maintaining data once it is published. Key to the widespread use of the Web of Data is ensuring that the dataset(s) your organization publishes remains available where you say it will be and is maintained over time.
-
-<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 404s is for your organization to implement a persistence strategy.
-</p>
-</section>
-
<!-- << STABILITY.overview -->
<section id="stability-prop">
@@ -1201,7 +1193,7 @@
<a href="http://nemo.inf.ufes.br/jpalmeida">João Paulo Almeida </a>, (Federal University of Espírito Santo, Brazil),
<a href="http://theodi.org/team/tom-heath">Tom Heath </a>, (Open Data Institute, UK),
<a href="http://lod-lam.net/summit/author/tombaker/">Thomas Baker </a>, (Dublin Core Metadata Initiative, US)
-<a href="http://csarven.ca/">Sarven Capadisli</a>, (UK)
+<a href="http://www.deri.ie/users/sarven-capadisli/">Sarven Capadisli</a>, (UK)
<a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Mondeca, France),
Michael Pendleton (U.S. Environmental Protection Agency, USA),
<a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088">Biplav Srivastava</a> (IBM India),