--- a/bp/index.html Fri Dec 13 14:00:40 2013 -0500
+++ b/bp/index.html Fri Dec 13 18:21:34 2013 -0500
@@ -100,7 +100,7 @@
"WOOD2013": {
title: "Linked Data: Structured Data on the Web" ,
href: "http://www.manning.com/dwood/",
- authors: ["Wood, D.", "Zaidman, M.", "Ruth, L.", "Hausenblas, M."] ,
+ authors: ["Wood, D.", "Zaidman, M.", "Ruth, L."] ,
publisher: "Manning Publications Co, New York, 2013"
} ,
@@ -170,7 +170,15 @@
title: "Linked Data Life cycles",
href:"http://linked-data-life-cycles.info/",
authors: ["Michael Hausenblas", "Richard Cygankiak"],
- }
+ },
+
+ "GBRUMFIEL":
+ {
+ title: "The First Web Page, Amazingly, Is Lost",
+ href: "http://www.npr.org/2013/05/22/185788651/the-first-web-page-amazingly-is-lost",
+ authors: ["Geoff Brumfiel"],
+ publisher: "National Public Radio"
+ }
}
};
@@ -189,7 +197,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> (LOD). <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. 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.
</p>
<h2>Audience</h2>
@@ -233,57 +241,42 @@
<p>The following best practices are discussed in this document and listed here for convenience.</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>
+<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="#PERSONAL">PERSONAL IDENTIFIABLE DATA:</a><br /> Do not publish personally identifiable information as Linked Open Data as it can potentially be misused.</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="#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="#METADATA">BASIC METADATA:</a> <br />Always provide basic
-<a href="http://www.w3.org/TR/ld-glossary/#metadata">metadata</a>.
-</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="#INTERNATIONAL">USE INTERNATIONALIZED RESOURCE IDENTIFIERS:</a> <br />Provide internationalized Resource Identifiers 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 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>
-<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.
-</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="#CONVERT">DATA CONVERSION:</a><br /> Convert the sources data to a Linked Data
-representation.
+<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>
-<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 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>
-<p class='stmt'><a href="#HOST">DOMAIN:</a> <br />Deliver Linked Open Data on an authoritative domain.
+<p class='stmt'><a href="#STANDARD-VOCABULARIES">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="#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="#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>
+
+<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>
+
+<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>
<p class='stmt'><a href="#SOCIAL-CONTRACT">SOCIAL_CONTRACT:</a> <br />Publishing Linked Open Data on the Web
@@ -295,23 +288,21 @@
</section>
<!-- Diagrams -->
-<section id='WORKFLOW'>
-<h2> Linked Open Data Workflow </h2>
+<section id='PREPARE'>
+<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.
+</p>
<p>
-The process of publishing Government Linked Open Data (GLD) can be tracked in well-defined steps. The worklow for includes starting with identifying a useful dataset to publish through publication and ongoing maintenance.
-
-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 standard open Web formats. In essence, they capture the same tasks that are needed in
-the process, but provide different boundaries between these tasks. One workflow is not better than another, they are simply different ways to visualize the process.
+To help prepare stakeholders, we've included three life cycle models, however it is evident that they all share common (and sometimes overlapping) activities. For example, they all identify the need to specify, model and publish data in standard open Web formats. In essence, they capture the same tasks that are needed in the process, but provide different boundaries between these tasks. One workflow is not better than another, they are simply different ways to visualize a familiar information management process.
</p>
<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 (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>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>
@@ -322,13 +313,8 @@
<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-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>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>
@@ -336,10 +322,7 @@
<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>
@@ -347,7 +330,7 @@
</section>
-<!-- SELECT -->
+<!-- SELECT A DATASET -->
<section id="SELECT">
<h2>Select a Dataset</h2>
@@ -360,15 +343,6 @@
</p>
</section>
-<!-- SELECT -->
-<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>
<!-- DATA MODELING -->
<section id="MODEL">
@@ -383,100 +357,29 @@
</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>
+<!-- BASIC METADATA -->
+<section id="BASIC">
+<h2>Basic Metadata</h2>
<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>, and </li>
-<li><a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</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>
-</section>
-
-
-<!-- BASIC METADATA -->
-<section id="BASIC">
-<h2>Include Basic Metadata</h2>
-
-<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).
+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.
</p>
</section>
-<!-- Publish 5-Star Data -->
-<section id="5STAR">
-<h2>Publish 5 Star Linked Open Data</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> helps efforts for consistent re-use. Here is a diagram of the <a href="http://5stardata.info/">5-Star Scheme</a>, that is summarized as follows:
-</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-ACCESS">
-<h2>Machine Access to Data</h2>
+<!-- PII -->
+<section id="PERSONAL">
+<h2>Personal Identifiable Information</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:
+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>
-
-<ul>
-<li>A <a href="http://www.w3.org/TR/ld-glossary/#rest-api">RESTful API</a>, </li>
-<li>a <a href="http://www.w3.org/TR/ld-glossary/#sparql-endpoint">SPARQL endpoint</a>, and/or </li>
-<li>via file download.
-</ul>
-
-<p>
-SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. A family of standards of the World Wide Web Consortium. See also SPARQL 1.1 Overview [SPARQL-11].
-</p>
-<p>
-A SPARQL endpoint is a a service that accepts SPARQL queries and returns answers to them as SPARQL result sets. It is a best practice for datasets providers to give the URL of their SPARQL endpoint to allow access to their data programmatically or through a Web interface. A <a href="http://labs.mondeca.com/sparqlEndpointsStatus/">list of some SPARQL endpoints</a> may be found here.
-</p>
-
</section>
-
-
-<!-- ANNOUNCE -->
-<section id="LINKS">
-<h2>Announce to the Public</h2>
-
-<!-- NOTE TO EDITORS: (BOH) Link summary to right place -->
-</section>
-
-
-<!-- SPECIFY LICENSE -->
+<!-- SPECIFY A LICENSE -->
<section id="LICENSE">
-<h2>Specifying an Appropriate License</h2>
+<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.
@@ -504,52 +407,186 @@
</section>
-<!-- DOMAIN AND HOSTING -->
-<section id="HOST">
-
-<h2>Domain and Hosting</h2>
+<!-- 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>
-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 re-use of authoritative datasets.
+<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>, and </li>
+<li><a href="http://www.w3.org/TR/ld-glossary/#http-uris">HTTP URIs</a>. </li>
+</ul>
</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>
+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>
+</section>
+
+<!-- URI PRINCIPLES -->
+<section id="URIPRINCIPLES">
+<h2>URI Design Principles</h2>
+<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 />
+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 />
+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 />
+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 [[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>
+
+</h3>
+</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>
+ <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://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;</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://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a> (PDF) </li>
+</ul>
+</p>
+
+<p>
+General-purpose guidelines exist for the URI designer to consider, including
+<ul>
+ <li> <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; </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>
+</p>
+</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>
-<!-- SOCIAL_CONTRACT -->
-<section id="SOCIAL-CONTRAT">
-<h2>The Social Contract of a Linked Data Publisher</h2>
+<section id="INTERNATIONAL">
+<h2>Internationalized Resource Identifiers</h2>
-<p>
-A closing but important final word. Publishers of Linked Data enter into an implicit 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. The following is intended to help your organization fulfill its social contract by publishing Linked Data for others to re-use on the Web:
-</p>
-<div class="note">
-<ul class="highlight">
-<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
-404s is for your organization to implement a persistence strategy.
+<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>
-</section>
+<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><i>Internationalized Resource Identifiers use non-ASCII characters in URIs which is relevent to those organizations interested in minting URIs in languages including German, Dutch, Spanish, French and Chinese.</i></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 exhaustive and the editors 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>
+ <li><b>Domain Name lookup:</b> Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as <code>.cn, .jp, .kr </code>, etc., and global top level domains such as <code>.info, .org </code> and <code> .museum. </code>
+ </li>
+ <li><b>Domain names and phishing:</b> One of the problems associated with IDN support in browsers is that it can facilitate phishing through what are called 'homograph attacks'. Consequently, most browsers that support IDN also put in place some safeguards to protect users from such fraud.
+ </li>
+ <li><b>Encoding problems:</b> IRI provides a standard way for creating and handling international identifiers, however the support for IRIs among the various semantic Web technology stacks and libraries is not uniformly and may lead to difficulties for applications working with this kind of identifiers. A good reference on this subject can be found in [[i18n-web]] .
+ </li>
+</ul>
+
+<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>
+
+</section>
<!-- STANDARD VOCABS -->
-<section id="STANDARD-VOCABS">
+<section id="STANDARD-VOCABULARIES">
<h2>Standard Vocabularies</h2>
<p>
@@ -593,7 +630,6 @@
</section>
-
<!-- Vocabulary Checklist -->
<section id="vocab-checklist">
<h2>Vocabulary Checklist</h2>
@@ -815,6 +851,134 @@
</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>
+
+<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:
+</p>
+<ul>
+<li>A <a href="http://www.w3.org/TR/ld-glossary/#rest-api">RESTful API</a>, </li>
+<li>a <a href="http://www.w3.org/TR/ld-glossary/#sparql-endpoint">SPARQL endpoint</a>, and/or </li>
+<li>via file download.
+</ul>
+
+<p>
+SPARQL Protocol and RDF Query Language (SPARQL) defines a query language for RDF data, analogous to the Structured Query Language (SQL) for relational databases. A family of standards of the World Wide Web Consortium. See also SPARQL 1.1 Overview [SPARQL-11].
+</p>
+<p>
+A SPARQL endpoint is a a service that accepts SPARQL queries and returns answers to them as SPARQL result sets. It is a best practice for datasets providers to give the URL of their SPARQL endpoint to allow access to their data programmatically or through a Web interface. A <a href="http://labs.mondeca.com/sparqlEndpointsStatus/">list of some SPARQL endpoints</a> may be found here.
+</p>
+
+</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>
+
+<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>
+
+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>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>
+</ul> </div>
+
+</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">
+
+<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>
+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!
+</p>
+
+</section>
+
<!--
NOTE TO EDITORS: This was deemed too technical for a general Linked Data best practices guide but is left for your future consideration.
@@ -826,12 +990,10 @@
<ul>
<li>it is within the scope and objectives of the vocabulary;</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>
+</ul>
-<li> it does not use terms from other vocabularies instead of ones defined in the vocabulary that could reasonably be used.</li>
-
-</ul>
A conforming data interchange:
<ul>
<li>MAY include terms from other vocabularies;</li>
@@ -849,7 +1011,7 @@
-->
-<!-- NOTE TO EDITORS: These are useful notes that we didn't have time to properly edit in the December 2013 BP doc. Major editing is required.
+<!-- NOTE TO FUTURE EDITORS: The original editors didn't have time to properly edit in the Dec 2013 BP doc. Major editing is required.
<section id="howto">
<h2>Best Practice for choosing entity URIs</h2>
@@ -925,87 +1087,6 @@
</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>
- <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://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;</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://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a> (PDF) </li>
-</ul>
-</p>
-
-<p>
-General-purpose guidelines exist for the URI designer to consider, including
-<ul>
- <li> <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; </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>
-</p>
-</section>
-
-<!-- URI PRINCIPLES -->
-<section id="URIPRINCIPLES">
-<h2>URI Design Principles</h2>
-<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 />
-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 />
-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 />
-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 [[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>
-
-</h3>
-</section>
-
<!-- NOTE TO FUTURE EDITORS: We didn't have enough time to polish this and therefore chose to omit at this time. For your future consideration.
@@ -1069,101 +1150,9 @@
-->
-<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>
-
-<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>
-
-<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><i>Internationalized Resource Identifiers use non-ASCII characters in URIs which is relevent to those organizations interested in minting URIs in languages including German, Dutch, Spanish, French and Chinese.</i></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 exhaustive and the editors 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>
- <li><b>Domain Name lookup:</b> Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as <code>.cn, .jp, .kr </code>, etc., and global top level domains such as <code>.info, .org </code> and <code> .museum. </code>
- </li>
- <li><b>Domain names and phishing:</b> One of the problems associated with IDN support in browsers is that it can facilitate phishing through what are called 'homograph attacks'. Consequently, most browsers that support IDN also put in place some safeguards to protect users from such fraud.
- </li>
- <li><b>Encoding problems:</b> IRI provides a standard way for creating and handling international identifiers, however the support for IRIs among the various semantic Web technology stacks and libraries is not uniformly and may lead to difficulties for applications working with this kind of identifiers. A good reference on this subject can be found in [[i18n-web]] .
- </li>
-</ul>
-
-<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>
-
-</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">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 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 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>
-
<!--
-NOTE TO EDITORS: (Per Bernadette) I do not think discussion of the TAG belongs in a BP document.
+NOTE TO FUTURE EDITORS: (Per Bernadette) I don't think discussion of the TAG belongs in a BP document.
<p class="note"><b>W3C Technical Architecture Group (TAG)</b><br />
@@ -1207,7 +1196,9 @@
<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://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://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://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Mondeca, France),
Michael Pendleton (U.S. Environmental Protection Agency, USA),