--- a/bp/index.html Tue Dec 17 15:05:44 2013 -0500
+++ b/bp/index.html Tue Dec 17 18:05:12 2013 -0500
@@ -217,14 +217,8 @@
<h2>Scope</h2>
<p>
-<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 the <a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a> (Resource Description Framework) family of standards for data interchange [[RDF-CONCEPTS]] and <a href="http://www.w3.org/TR/ld-glossary/#sparql">SPARQL</a> for query. <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 synonyms. Linked Data however could not exist without the consistent underlying data model that we call RDF [[RDF-CONCEPTS]]. Understanding the basics of RDF is helpful to leverage the usefulness of <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a>. </p>
-<p> Linked Data can be written in a variety of syntaxes including: </p>
-<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> and
-<li><a href="http://www.w3.org/TR/ld-glossary/#rdf-xml">RDF/XML</a></li>
-</ul>
+<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 the <a href="http://www.w3.org/TR/ld-glossary/#rdf">RDF</a> (Resource Description Framework) family of standards for data interchange [[RDF-CONCEPTS]] and <a href="http://www.w3.org/TR/ld-glossary/#sparql">SPARQL</a> for query. <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 synonyms. Linked Data however could not exist without the consistent underlying data model that we call RDF [[RDF-CONCEPTS]]. Understanding the basics of RDF will be helpful in leveraging <a href="http://www.w3.org/TR/ld-glossary/#linked-data">Linked Data</a>.
+</p>
<h2>Background</h2>
@@ -243,49 +237,38 @@
<!-- List of Best Practices -->
<section id='sumbp'>
-<h2>Summary of Best Practices</h2>
+<b>Summary of Best Practices</b>
<p>The following best practices are discussed in this document and listed here for convenience.</p>
-<p class='stmt'><a href="#PREPARE">PREPARE:</a><br />Prepare stakeholders by explaining the high level workflow or process involved in publishing and using <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>.
-</p>
-
-<p class='stmt'><a href="#SELECT">SELECT A DATASET:</a><br /> Select a dataset that provides benefit to others for re-use.
-</p>
-
-<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.</p>
-
-<p class='stmt'><a href="#BASIC">BASIC METADATA:</a> <br />Always provide basic <a href="http://www.w3.org/TR/ld-glossary/#metadata">metadata</a>.
+<p class='stmt'><a href="#PREPARE">STEP #1 PREPARE STAKEHOLDERS:</a><br /> Prepare stakeholders by explaining the process of creating and maintaining <a href="http://www.w3.org/TR/ld-glossary/#linked-open-data">Linked Open Data</a>.
</p>
-<p class='stmt'><a href="#PERSONAL">PERSONAL IDENTIFIABLE DATA:</a><br /> Do not publish personal identifiable information as Linked Open Data as it can potentially be misused.</p>
-
-<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. This is typically done by script or other automated processes.
+<p class='stmt'><a href="#SELECT">STEP #2 SELECT A DATASET:</a><br /> Select a dataset that provides benefit to others for re-use.
</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 class='stmt'><a href="#MODEL">STEP #3 MODEL THE DATA:</a> <br /><a href="http://www.w3.org/TR/ld-glossary/#modeling-process">Modeling Linked Data</a> involves representing data objects and how they are related in an application-independent way.
</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.
+<p class='stmt'><a href="#LICENSE">STEP #4 SPECIFY A LICENSE:</a> <br />Specify an appropriate open license with the published data.</p>
+
+<p class='stmt'><a href="#HTTP-URIS">STEP #5 GOOD URIs FOR LINKED DATA:</a><br /> The core of Linked Data is a well-considered URI naming strategy and implementation plan, based on <a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>. Consideration for naming objects, multilingual support, and how the data will change over time and a persistence strategy is the foundation of publishing useful Linked Data that encourages reuse.
</p>
-<p class='stmt'><a href="#STANDARD-VOCABULARIES">STANDARD_VOCABULARIES:</a> <br />Describe objects with previously defined
+<p class='stmt'><a href="#VOCABULARIES">STEP #6 USE STANDARD VOCABULARIES:</a> <br />Describe objects with previously defined
standard <a href="http://www.w3.org/TR/ld-glossary/#vocabulary">vocabularies</a> whenever possible. Extend standard vocabularies where necessary. Create vocabularies when required following best practices wherever possible.
</p>
-<p class='stmt'><a href="#5STAR">PUBLISH DATA FOR ACCESS AND REUSE:</a> <br /> Select, model and publish dataset(s) with links to other interesting data thereby making it immediately more useful.
+<p class='stmt'><a href="#CONVERT">STEP #7 CONVERT DATA:</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="#MACHINE">MACHINE ACCESSIBLE:</a><br /> Provide various ways for search engines and other automated processes to access data using standard Web mechanisms.
+<p class='stmt'><a href="#MACHINE">STEP #8 PROVIDE MACHINE ACCESS TO DATA:</a><br /> Provide various ways for search engines and other automated processes to access data using standard Web mechanisms.
</p>
-<p class='stmt'><a href="#DOMAIN">DOMAIN AND HOSTING:</a> <br />Deliver Linked Open Data on an authoritative domain.
+<p class='stmt'><a href="#ANNOUNCE">STEP #9 ANNOUNCE NEW DATA SETS:</a><br /> Remember to announce new data sets on an authoritative domain. Importantly, remember that as a Linked Open Data publisher, an implicit social contract is formed. Plan in advance to perform routine maintenance and provide timely responses to feedback from data consumers.
</p>
-<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 class='stmt'><a href="#SOCIAL-CONTRACT">STEP #10 RECOGNIZE THE SOCIAL CONTRACT:</a><br /> Recognize your responsibility in maintaining data once it is published. Ensure that the dataset(s) remain available where your organization says it will be and is maintained over time.
</p>
@@ -295,7 +278,7 @@
<!-- Diagrams -->
<section id='PREPARE'>
-<h2>Preparing to Publish Linked Open Data</h2>
+<h2>Prepare Stakeholders</h2>
<p>
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.
@@ -350,22 +333,23 @@
</section>
-<!-- DATA MODELING -->
+<!-- MODEL THE DATA -->
<section id="MODEL">
-<h2>Data Modeling</h2>
+<h2>Model the Data</h2>
-<p>
-Modeling Linked Data requires representation of data objects and how they are related in an application-independent way. For example, if the data was originally organized for a specific application, Linked Data modeling may involve removing government program or agency-related content. When modeling Linked Data, one is representing things and how they are related, typically for public consumption. Denormalizing data may be necessary and is appropriate when modeling Linked Data. Linked Data can and is used within government agencies to improve data integration for related or complementary information.
+<p class="note">
+It is not within scope of this document to expand on the process of Linked Open Data modeling, rather we introduce how Linked Data modeling differs from the more familiar relational data modeling approach, as well as involving stakeholders.
</p>
-<p> The process of data modeling should involve someone who is intimately familiar with the representation of data using open Web standards. Familiarity with standard vocabularies will both expedite the modeling process and help produce data that can be more readily linked to other data sets.
+<p>
+During the data modeling phase, stakeholders should include at least one individual familiar with the logical model and schema of the existing dataset, e.g., a database administrator. Including a subject manager expert on Linked Data principles will assist in the quality of the output and efficiency in the publication process.
</p>
-</section>
+</P
+The Linked Data modeling process involves representation of data objects and how they are related in an application-independent way. For example, traditionally data has been organized for a specific purpose. Over the last decade, more abstracted publication strategies have evolved with the Web to provide data independent of the application. Linked Data takes this abstraction slightly further by representing things and how they are related.
+</p>
-<!-- BASIC METADATA -->
-<section id="BASIC">
-<h2>Basic Metadata</h2>
+<h3> Provide Basic Metadata </h3>
<p>
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). In the following section, guidance on the use of existing standard vocabularies, extending a standard vocabulary and creating a new vocabulary are provided as informative guidance.
@@ -373,15 +357,6 @@
</section>
-<!-- PII -->
-<section id="PERSONAL">
-<h2>Personal Identifiable Information</h2>
-
-<p>
-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, driver's license numbers, salaries and tax return information. Exceptions to this practice may include public information required by law, such as individual names, office extensions, salaries and tax information, for some public officials.
-</p>
-</section>
<!-- SPECIFY A LICENSE -->
<section id="LICENSE">
@@ -406,50 +381,12 @@
</section>
-<!-- CONVERT DATA TO LINKED DATA -->
-<section id="CONVERT">
-<h2>Convert Data to Linked Data</h2>
-<p>
-Convert the sources data to a Linked Data representation. This involves a data modeling step, followed by consensus that the object and relationships correctly reflect the dataset(s). The next step involves mapping the source data into a set of RDF statements via a script. When we convert data, we are serializing the data into RDF statements. RDF can be converted into a range of RDF serializations that include:
-</p>
-
-<p>
-<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> 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></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>
+<!-- URI DESIGN AND NAMING -->
+<section id="HTTP-URIS">
-<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>
+<h2>The Role of "Good URIs" for Linked Data</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>
+<h3>URI Design Principles</h3>
<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
@@ -484,19 +421,15 @@
</p>
<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:
+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.
</p>
-</section>
-
-<section id="URI-POLICY">
-<h2>URI Policy for Persistence</h2>
+<h3>URI Policy for Persistence</h3>
<p>
Defining and documenting a persistent URI policy and implementation plan is vital to the ongoing success and stability of publishing open government data.
@@ -530,12 +463,10 @@
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>
+
+<h3>URI Construction</h3>
<p>
The following guidance is has been developed by organizations involved in URI strategy and implementation for government agencies:
@@ -563,11 +494,9 @@
<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>
</p>
-</section>
-<section id="INTERNATIONAL">
-<h2>Internationalized Resource Identifiers</h2>
+<h3>Internationalized Resource Identifiers</h3>
<p>Stakeholders who are planning to create URIs using characters that go beyond the subset defined in [[RFC3986]]</a> are encouraged to reference <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 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>
@@ -595,14 +524,13 @@
<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>
+alphabet, European numerals and a small number of symbols.</p>
</section>
<!-- STANDARD VOCABS -->
-<section id="STANDARD-VOCABULARIES">
+<section id="VOCABULARIES">
<h2>Standard Vocabularies</h2>
<p>
@@ -647,15 +575,15 @@
<!-- Vocabulary Checklist -->
-<section id="vocab-checklist">
-<h2>Vocabulary Checklist</h2>
+
+<h3>Vocabulary Checklist</h3>
<p class="note">
It is best practice to use or extend an existing vocabulary before creating a new vocabulary. This
section provides a set of considerations aimed at helping stakeholders review a vocabulary to evaluate its usefulness.
</p>
-<p>Some basics:
+<p>A basic vocabulary checklist:
<b>ensure vocabularies you use are published by a trusted group or organization;</b>
<b>ensure vocabularies have permanent URIs; and </b>
<b>confirm the versioning policy</b>.
@@ -718,16 +646,13 @@
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 -->
-<section id="VOCAB-CREATION">
-<h2>Vocabulary Creation</h2>
+<h3>Vocabulary Creation</h3>
-<p class="note">
-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>
+This section provides a set of informative considerations aimed at stakeholders who must develop their own vocabularies.
</p>
<p>
@@ -811,8 +736,7 @@
<!-- Using SKOS to create a controlled vocabulary -->
-<section id='skos'>
-<h2>Using SKOS to Create a Controlled Vocabulary</h2>
+<h3>Using SKOS to Create a Controlled Vocabulary</h3>
<div class='note'>
SKOS, the Simple Knowledge Organization System [[SKOS-REFERENCE]], is a W3C standard,
@@ -839,11 +763,9 @@
<li>Provide multilingual labels for the terms.</li>
</ul>
</div>
-</section>
-<section id="multilingual">
-<h2>Multilingual Vocabularies</h2>
+<h3>Multilingual Vocabularies</h3>
<p>
This section is not comprehensive however, is intended to mention some of the issues identified by the Working Group and some of the work performed by others in relation to publishing Linked Data in multiple languages. 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>
@@ -887,9 +809,36 @@
</section>
+<!-- CONVERT DATA TO LINKED DATA -->
+<section id="CONVERT">
+<h2>Convert Data to Linked Data</h2>
+<p>
+Now with the ground work in place, the next step is to actually convert a dataset into a Linked Data representation. There is more than one way to convert data including scripts, declarative mapping languages, languages that perform query translation rather then data translation (e.g. R2RML). Regardless of which approach is used, data conversion involves mapping the source data into a set of RDF statements. As data is converted, data is serialized into RDF statements. RDF can be converted into a range of RDF serializations that include:
+</p>
+
+<p>
+<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> 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></li>
+</ul>
+</p>
+
+<div class="note">
+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>
+
+
<!-- MACHINE ACCESSIBLE -->
<section id="MACHINE">
-<h2>Machine Access to Data</h2>
+<h2>Provide Machine Access to Data</h2>
<p>
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:
@@ -910,26 +859,17 @@
</section>
-<!-- DOMAIN AND HOSTING -->
-<section id="DOMAIN">
-
-<h2>Domain and Hosting</h2>
-
-<p>
-Publish 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 re-use of authoritative datasets.
-</p>
-
-<p>It is not within scope of this document to expand on hosting Linked Open Data however, data hosting is a vital part of the publication process. Hosting Linked Open Data may require involvement with agency system security staff and require planning that often takes considerable time and experise for compliance, so involve stakeholders early and schedule accordingly.
-</p>
-
-</section>
-
-
<!-- ANNOUNCE -->
<section id="ANNOUNCE">
<h2>Announce to the Public</h2>
-<div class="note">
+<p class="note">It is not within scope of this document to discuss domain name issues and data hosting however, it is a vital part of the publication process. Hosting Linked Open Data may require involvement with agency system security staff and require planning that often takes considerable time and experise for compliance, so involve stakeholders early and schedule accordingly.
+</p>
+
+<p>Now you're ready to point people to authoritative open government data. Be sure the datasets are available via 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 re-use of authoritative datasets.
+</p>
+
+<p>
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.
<ul>
@@ -943,32 +883,34 @@
<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/
+</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>
+
+<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>
-<!-- << STABILITY.overview -->
-<section id="stability-prop">
+<!-- NOTE TO FUTURE EDITORS: We wanted to include the CKAN DataHub http://datahub.io/ however at the time of this WG Note's review, the site returned 503 - Service Unavailable, so it was (temporarily) omitted. Please consider adding a link to this useful service once it is confirmed operational again.
+-->
<h3>Stability Properties</h3>
-<p> It is beyond the scope of this document to comprehensively treat issues related to data stability over time on the Web. However, it should be noted that many of the best practices for Linked Data have been advised by over four decades of enterprise information management strategy and practice. In the last twenty years, experts and researchers on the cutting edge of artificial intelligence, computational linguistics, computer science, philosophy and mathematics have worked collaboratively on the concepts, technnologies, and importantly international standards that make the Web the largest information system known to humankind.
-</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 authorities should contemplate in their published data strategy include:
-</p>
-
-<ul>
-<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>Always provide 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>
+<p class="note"> It is beyond the scope of this document to comprehensively treat issues related to data stability over time on the Web. Mention is included such that readers may consider data stability in the context of a given agency and region.
+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. </p>
<p>
-The W3C will celebrate its 20th anniversary and the Web turns 25 years old in 2014. Perhaps surprisingly, the first Web page cannot be found. A team at CERN is looking into restoring it, however at the time of the writing of this document, it has not yet been found.[[GBRUMFIEL]] Thus, the Government Linked Data Working Group wished to reference the importance of <i>data stability</i> as the vast majority of government data is quickly available <i>only</i> in digital form. As stewards and supporters of open government data, it is encumbant upon us all to pursue the methods and tools to support responsible data stability on the Web over time. Thanks for your interest in this topic and please join us in helping evolve the Web of Data into the 21st Century and beyond!
+As a final note related to the importance of stability. The W3C prepares to celebrate its 20th anniversary and the Web turns 25 years old in 2014. Perhaps surprisingly, the first Web page cannot be found. A team at CERN is looking into restoring it, however at the time of the writing of this document, it has not yet been found.[[GBRUMFIEL]] Thus, the Government Linked Data Working Group wished to reference the importance of <i>data stability</i> as the vast majority of government data is quickly available <i>only</i> in digital form. As stewards and supporters of open government data, it is encumbant upon us all to pursue the methods and tools to support responsible data stability on the Web over time. Thanks for your interest in this topic and please join us in helping evolve the Web of Data into the 21st Century and beyond!
</p>
</section>
@@ -1186,9 +1128,10 @@
<h2>Acknowledgments</h2>
<p>
-The editors wish to gratefully acknowledge the considerable contributions to the Linked Data Best Practices document by the following people: <a href="http://www.about.me/david_wood/">David Wood</a> (3 Round Stones, USA),
+The editors wish to gratefully acknowledge the considerable contributions to the Linked Data Best Practices document by the following people:
<a href="http://www.epimorphics.com">Dave Reynolds</a>, (Epimorphics,UK),
<a href="http://www.w3.org/People/#phila">Phil Archer</a>, (W3C / ERCIM, UK),
+<a href="http://www.linkedin.com/in/makxdekkers">Makx Deckers</a>, (Independent Consultant, Spain),
<a href="http://logd.tw.rpi.edu/person/john_erickson">John Erickson</a> (Rensselaer Polytechnic Institute, USA),
<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),
@@ -1197,10 +1140,10 @@
<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),
-<a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group, Universidad Politécnica de Madrid, UPM, Spain),
-Martín Álvarez Espinar (CTIC-Centro Tecnológico, Spain),
+<a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group, Universidad Politécnica de Madrid, UPM, Spain), Martín Álvarez Espinar (CTIC-Centro Tecnológico, Spain),
+<a href="http://www.about.me/david_wood/">David Wood</a> (3 Round Stones, USA),
<a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR, USA), and
-<a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov, UK). Please accept our apologies if we've inadvertantly omitted your name from this list as many people were absolutely instrumental in the production of this international publication.
+our working group co-chair, <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov, UK). Please accept our apologies in advance if we've inadvertantly omitted your name as many people provided valuable feedback and were instrumental in the production of this best practices publication.
</p>
<p>
Thank you, grazie, gracias, obrigado, merci, धन्यवाद.