--- a/bp/index.html Tue Mar 12 22:42:31 2013 -0400
+++ b/bp/index.html Wed Mar 13 01:20:11 2013 -0400
@@ -33,7 +33,8 @@
<section class="introductory">
<h2>Purpose of the Document</h2>
<p>
-This document sets out a series of best practices designed to facilitate development and delivery of Linked Open Data in both human and machine readable data formats. The recommendations are offered to creators, maintainers and operators of Web sites publishing government data.
+This document sets out a series of best practices designed to facilitate development and delivery of open government data as Linked Data.
+The following recommendations are offered to creators, maintainers and operators of Web sites publishing open government data.
</p>
<h2>Audience</h2>
@@ -46,24 +47,15 @@
This document aims to facilitate the adoption of a Linked Open Data approach to publishing open government data on the Web.
<p>
-Linked Data uses a family of international standards and best practices for the publication, dissemination and reuse of structured data. Linked Data, unlike previous data formatting and publication approaches, provides a simple mechanism for combining data from multiple sources across the Web. <a href="http://www.w3.org/DesignIssues/LinkedData.html" title="Linked Data - Design Issues">Linked Data</a> addresses many objectives of open government transparency initiatives through the use international Web standards for the publication, dissemination and reuse of structured data.
+Linked data refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of the RDF family of syntaxes (e.g., RDF/XML, N3, Turtle and N-Triples) and HTTP URIs. Linked Data can be published by an person or organization behind the firewall or on the public Web. If Linked Data is published on the public Web, it is generally called Linked Open Data.
</p>
<h2>Background</h2>
<p>
-In recent years, governments worldwide have mandated publication of open government content to the public Web for the purpose of facilitating open societies and to support governmental accountability and transparency initiatives. However, publication of unstructured data in HTML alone is insufficient. In order to realize the goals of open government initiatives, the re-use of government data requires that members of the public can find, visualize and programmatically absorb the data. Publishing government content as Linked Data is the means to achieve these worthy objectives.
+In recent years, governments worldwide have mandated publication of open government content to the public Web for the purpose of facilitating open societies and to support governmental accountability and transparency initiatives. In order to realize the goals of open government initiatives, the W3C Government Linked Data Working Group offers the following guidance to aid in the access and re-use of open government data. Linked Data provides a simple mechanism for combining data from multiple sources across the Web. <a href="http://www.w3.org/DesignIssues/LinkedData.html" title="Linked Data - Design Issues">Linked Data</a> addresses many objectives of open government transparency initiatives through the use international Web standards for the publication, dissemination and reuse of structured data.
</p>
-<!-- <p>
-In a nutshell, Linked Data is fundamentally about building a Web of Data, upon two simple concepts: (1) use RDF data model to publish structured data on the Web and (2) to set explicit RDF links between entities within different data sources.
-</p> -->
</section>
-<p class="todo"> To include: a proper introduction of what a link is the given context.
-</p>
-
-<p class="todo"> To include: a section on how to create data links (within an organization's dataset and, more importantly, to data from other sources).
-</p>
-
<!-- List of Best Practices -->
@@ -105,11 +97,11 @@
<!-- Diagrams -->
-<h3> Linked Open Data Lifecycle </h3>
+<h2> Linked Open Data Lifecycle </h2>
<!-- <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p> -->
-<!-- <p class="todo"> To Review: Bernadette, Michael, Boris - Please review the brief descriptions for your lifecycle diagrams.
-</p> -->
+<p class="todo"> (Editors) - Please provide a brief description of lifecycle diagrams.
+</p>
<ul>
<li>
@@ -122,7 +114,7 @@
<ul>
<li>
- <p>Hausenblas et al. propose Linked Data life cycles that consist in the following steps: (1) data awareness, (2) modelling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.</p>
+ <p>Hausenblas et al. propose Linked Data life cycles that consist in the following steps: (1) data awareness, (2) modeling, (3) publishing, (4) discovery, (5) integration, and (6) use cases.</p>
</li>
</ul>
<img src="img/GLF_Hausenblas.PNG" width="600"/>
@@ -137,99 +129,45 @@
</section>
-<!-- PROCUREMENT -->
+<!-- VOCABULARY SELECTION -->
<section>
-<h2>Procurement</h2>
+<h2>Vocabulary Selection</h2>
<p>
-This procurement overview and companion glossary is intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
-</p>
-
-<h3>Overview</h3>
-
-<p>
-The majority of structured data collected and curated by governments worldwide resides in relational data systems. The general activities associated with Linked Open Data development and maintenance include:
+There are several core W3C vocabularies that allow a developer to describe basic or more complex relationships as Linked Data. Standardized vocabularies should be reused as much as possible to facilitate inclusion and expansion of the <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#web-of-data'>Web of data</a>. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
</p>
-<ol type="1">
- <li>LOD Preparation<li>
- <p>Services : Services that support modeling relational or other data sources using HTTP URIs, developing scripts used to generate/create Linked Open Data.</p>
- <li>LOD Publishing</li>
- <p>Products: General categories include databases, visualization, application development platforms</p>
- <p>Services: These are services that support creation, interlinking and deployment of linked data (see also linked data preparation). Hosting data via graph database is an important component of Linked Open Data publishing. During preparation for publishing linked data, data and publishing infrastructure may be tested and debugged to ensure it adheres to linked data principles and best practices. (Source: Linked Data: Evolving the Web into a Global Data Space, Heath and Bizer, Morgan and Claypool, 2011, Section 5.4, p. 53)</p>
- </p>
- <li>LOD Discovery and Consumption</li>
- <p>Products: Linked Data Browsers allow users to navigate between data sources by following RDF links; Linked Data Search Engines crawl linked data by following RDF links, and provide query capabilities over aggregated data.</p>
- <p>Services: These are services that support describing, finding and using linked data on the Web. Publication of linked data contributes to a global data space often referred to as the Linked Open Data Cloud or ‘Web of Data.’ These are services that support the development of applications that use (i.e. consume) this ‘Web of Data.’</p>
- <li>Management Consulting and Strategic Planning</li>
- <p>Products: Not applicable</p>
- <p>Services: There are a broad range of management related services; examples include briefings intended for decisions makers to provide a general understanding of the technology, business case, ROI; strategic planning support (e.g. enterprise linked data, implementation of PURLs, etc.)</p>
- <li>Formal Education and Training</li>
- <p>Products :</p>
- <p>Services: Various private companies and universities offer training related to linked open data. These offerings vary widely. Trainings vary from high-level informational trainings intended to provide managers/decision makers with general understanding, to in-depth, hands-on instruction for the tech savvy on how to prepare, publish and consume linked data.</p>
-</ol>
-
-<h3>Procurement Checklist</h3>
+<p>
+For example, organizational structures and activities are often described by government authorities. The <a href='http://www.w3.org/TR/vocab-org/
+'>Organization Ontology</a> aims to support publishing of organizational information across a number of domains, as Linked Data. The Organizational Ontology is designed to allow domain-specific extensions to add classification of organizations and roles, as well as extensions to support neighbouring information such as organizational activities.
+</p>
-The following is an outline of questions a department/agency should consider reviewing as part of their decision to choose a service provider:
-<ul>
-<li>Is there a government approved contract vehicle to obtain this service or product?</li>
-
-<li>What is the vendor’s past performance with government agencies or authorities?</li>
-
-<li>Does the vendor have reference sites? Are they similar to what you are considering in production?</li>
-
-<li>Does the vendor provide training for the products or services?</li>
-
-<li>Is the documentation comprehensive and usable?</li>
+<p>
+The <a href='http://www.w3.org/TR/vocab-dcat/'>Data Catalog Vocabulary (DCAT)</a> is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.
+</p>
-<li>Is the software supported and under active development?</li>
-
-<li>Is there an interface to load data and “follow your nose” through a Web interface?</li>
-
-<li>Is the government data accessible for developers once it is published?</li>
+<p>
+Many government agencies publish statistical information on the public Web. The <a href="http://www.w3.org/TR/vocab-data-cube/">
+Data Cube Vocabulary</a> provides a means to do this using the <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#rdf'>Resource Description Framework (RDF)</a>. The model underpinning the Data Cube vocabulary is compatible with the cube model that underlies SDMX (Statistical Data and Metadata eXchange), an ISO standard for exchanging and sharing statistical data and metadata among organizations. The Data Cube vocabulary is a core foundation which supports extension vocabularies to enable publication of other aspects of statistical data flows or other multi-dimensional data sets.
+</p>
-<li>Can the data be queried programmatically via a SPARQL endpoint?</li>
-
-<li>What is the vendor’s Service Level Agreement?</li>
-
-<li>Is the vendor or provider an active contributor to Open Source Software, Standards groups, activities associated with data.gov and Linked Open Data projects at the enterprise and/or government level.</li>
-
-<li>Does the vendor adhere to the agency's published Open Source Policy, if one exists?</li>
-
-</ul>
+<p class="todo"> To include: Phil suggests to include <a href="http://www.w3.org/QA/2012/07/conformance_for_vocabularies.html" target="_blank">Conformance for Vocabularies</a>.
</p>
</section>
-<!-- VOCABULARY SELECTION -->
-<section>
-<h2>Vocabulary Selection</h2>
-
-<p class="todo"> To include: George suggests to include how to mint new terms and reusing available terms, and mention the "accidental subsumption".
-</p>
-
-<p class="todo"> To include: Phil suggests to include <a href="http://www.w3.org/QA/2012/07/conformance_for_vocabularies.html" target="_blank">Conformance for Vocabularies</a>.
-</p>
-
-<!-- <p class="todo">Please Review: Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila-Suero (UPM)</p>
-<p> -->
-<!-- Reuse standard, vetted vocabularies to encourage others to use your data. Guidance on finding standard, vetted vocabularies is described in the Vocabulary Discovery Checklist below. -->
-</section>
-
-
-<!-- Discovery checklist -->
+<!-- Discovery Checklist -->
<h3>Vocabulary Discovery Checklist</h3>
-<p>This checklist provides some considerations when trying to find out existing vocabularies that could best fit the needs of a government authority.
+<p>The following checklist is a guide to helping developers determine whether an existing vocabulary would be a reasonable candidate for use by a government authority.
</p>
<p class="highlight"><b>Specify the domain</b><br/>
<i>What it means:</i>
-Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation, etc. </p>
+Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</p>
<p class="highlight"><b>Identify relevant keywords in the dataset</b><br/>
- <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine. If you have raw data in csv, the columns of the tables can be used for the searching process. <br/><br/>
+ <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine. If you have raw data in <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#csv'>CSV</a>, the columns of the tables can be used for the searching process. <br/><br/>
Examples: commune, county, feature
</p>
@@ -249,6 +187,28 @@
</p>
+<!-- << is your linked data vocabulary 5 star? -->
+
+<h3>Is your linked data vocabulary 5-star?</h3>
+Inspired by the 5-star linked data scale <a href="http://5stardata.info/" target="_blank">REF3</a>, we provide some suggestions on how do you make a 5-star vocabulary <a href="http://blog.hubjects.com/2012/02/is-your-linked-data-vocabulary-5-star_9588.html" target="_blank">REF4</a>.
+
+<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>
+<!-- is your linked data vocabulary 5 star? >> -->
+
+
<!-- << Vocabulary Selection Criteria checklist -->
<h3>Vocabulary Selection Criteria</h3>
@@ -318,7 +278,7 @@
Partial or full deprecation
Cross-cutting issues: "Hit-by-bus" -->
-<p>There will be cases in which authorities will need to mint their own vocabulary terms. This section provides a set of considerations aimed at helping to government stakeholders to mint their own vocabulary terms. This section includes some items of the previous section because some recommendations for vocabulary selection also apply to vocabulary creation. Ensure new vocabularies you create are:
+<p>There will be cases in which authorities will need to mint their own vocabulary terms. This section provides a set of considerations aimed at helping to government stakeholders mint their own vocabulary terms. This section includes some items of the previous section because some recommendations for vocabulary selection also apply to vocabulary creation. Ensure new vocabularies you create are:
<li>Self-descriptive </li>
<li>Described in more than one language, ideally </li>
<li>Accessible for a long period</li>
@@ -377,37 +337,13 @@
<!-- Multilingualism in vocabs >> -->
-<!-- << is your linked data vocabulary 5 star? -->
-<h3>Is your linked data vocabulary 5-star?</h3>
-Inspired by the 5-star linked data scale <a href="http://5stardata.info/" target="_blank">REF3</a>, we provide some suggestions on how do you make a 5-star vocabulary <a href="http://blog.hubjects.com/2012/02/is-your-linked-data-vocabulary-5-star_9588.html" target="_blank">REF4</a>.
-
-<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>
-
-
-<!-- is your linked data vocabulary 5 star? >> -->
-
</section> <!-- VOCABULARY SELECTION >> -->
<!-- << URI CONSTRUCTION -->
<section>
<h2>URI Construction</h2>
-<!-- <p class="todo">To Review: Ghislain Atemezing (INSTITUT TELECOM), Boris Villazon-Terrazas (iSOCO), Daniel Vila (UPM), John Erickson (RPI), Bernadette Hyland (3 Round Stones)</p>
-<p> -->
-Guidance in this document is minting URIs for vocabularies, concepts, and datasets. This section specifies how to create good URIs for use in government linked data. Inputs include
+The following guidance is providing with respect to creating or sometimes called "minting" URIs for vocabularies, concepts, and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include
<ul>
<li><a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a></li>
<li><a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF)</li>
@@ -656,36 +592,67 @@
</section>
+
+<!-- PROCUREMENT -->
+<section>
+<h2>Procurement</h2>
+
+<p>
+This procurement checklist and <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
+</p>
+
+<h3>Overview</h3>
+
+<p>
+The majority of structured data collected and curated by governments worldwide resides in relational data systems. The general activities associated with Linked Open Data development and maintenance include:
+</p>
+
+<h3>Procurement Checklist</h3>
+
+The following is an outline of questions a department/agency should consider reviewing as part of their decision to choose a service provider:
+<ul>
+<li>Is there a government approved federal-wide or agency-specific contract vehicle to obtain this service or product?</li>
+
+<li>What is the vendor’s past performance with government agencies or authorities?</li>
+
+<li>Does the vendor have reference sites? Are they similar to what you are considering in production?</li>
+
+<li>Does the vendor provide training for the products or services?</li>
+
+<li>Is the documentation comprehensive and usable?</li>
+
+<li>Is the software supported and under active development?</li>
+
+<li>Is the government data accessible for developers once it is published?</li>
+
+<li>Can the data be queried programmatically, e.g., through an <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#api'>Application Programming Interface</a> (API), <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#sparql-endpoint'>SPARQL endpoint</a>, other mechanism?</li>
+
+<li>What is the vendor’s Service Level Agreement?</li>
+
+<li>Does the vendor adhere to the agency's published Open Source Policy, if one exists?</li>
+
+</ul>
+</p>
+</section>
+
+
<!-- Pragmatic Provenance -->
<!-- Note to Editors: This section is NOT part of our charter and should be folded into other section(s). -->
<section>
-<h2>Pragmatic Provenance</h2>
+<h2>Provenance</h2>
<!-- <p class='todo'>John Erickson (RPI)</p> -->
-<p>Provide best practice recommendations for stakeholders on documenting the provenance of their linked government data and how to interpret that data so that consumers know what they are looking at.</p>
-
-Provenance = the sources that establish a context for the production and/or use of an artifact. See <a href="http://www.w3.org/2011/prov/wiki/Main_Page" target="_blank">W3C Provenance working group</a></li>
-
-
-<h3>Background</h3>
-<p>In 1997 Tim Berners-Lee called for pervasive provenance on the Web:</p>
-<p class="highlight">
-<i>At the toolbar (menu, whatever) associated with a document there is a button marked "Oh, yeah?". You press it when you lose that feeling of trust. It says to the Web, 'so how do I know I can trust this information?'. The software then goes directly or indirectly back to metainformation about the document, which suggests a number of reasons.</i>
-</p>
-<p>W3C GLD therefore seeks to recommend practices that enable government providers to create the metadata necessary to answer their users' "oh yeah?" questions about the linked data they publish. Our recommendations may include processes as well as the application of specific vocabularies/ontologies.
+<p>
+Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The <a href="http://www.w3.org/TR/prov-overview/
+" target="_blank">PROV Family of Documents</a> defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.
</p>
-<h3>What do we mean by "Provenance?"</h3>
-<p>The W3C's Provenance Incubator Group (2010) <a href="http://www.w3.org/2005/Incubator/prov/XGR-prov-20101214/#What_is_provenance" target="_blank">provides</a> this simple definition of provenance:</p>
-<p class="highlight">Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource. Provenance provides a critical foundation for assessing authenticity, enabling trust, and allowing reproducibility. Provenance assertions are a form of contextual metadata and can themselves become important records with their own provenance.</p>
+<p>
+The W3C Government Linked Data Working Group offers the following best practices for government stakeholders to assist people using open government data available on the public Web.
+</p>
-<p>More recently the W3C Provenance WG (PROV-WG) defines "provenance" for their work:</p>
-<p class="highlight"><i>The <b>provenance</b> of digital objects represents their origins. The PROV Data Model (<a href="http://www.w3.org/TR/2012/WD-prov-primer-20120110/#bib-PROV-DM" target="_blank">PROV-DM</a>) is a proposed standard to represent provenance records, which contain assertions about the entities and activities involved in producing and delivering or otherwise influencing a given object. By knowing the provenance of an object, we can make determinations about how to use it. Provenance records can be used for many purposes, such as understanding how data was collected so it can be meaningfully used, determining ownership and rights over an object, making judgments about information to determine whether to trust it, verifying that the process and steps used to obtain a result complies with given requirements, and reproducing how something it was generated...As a standard for provenance, PROV-DM accommodates all those different uses of provenance. Different people may have different perspectives on provenance, and as a result different types of information might be captured in provenance records.</i></p>
-
-
-<h3>What do we mean by "Pragmatic Provenance"</h3>
-<p>The W3C Government Linked Data WG accepts PROV WG's definition of provenance but recognizes that PROV-DM is a powerful tool. W3C GLD WG seeks to provide best practice recommendations that will be useful to government data stakeholders, that make sense for GLD use cases and are easily adopted by practitioners.</p>
+<!-- todo: Talk to John Erickson to develop this more for possible inclusion
<p>W3C GLD could recommend a simple <b>provenance scoring system</b> for GLD analogous to TBL's 5 stars for linked data. Such a system might include:</p>
<ul>
<li><b>One star:</b> Using the basic <a href="http://bit.ly/imvRX1" target="_blank">W3C DCAT</a> for Linked Data at the catalogs and dataset level</li>
@@ -706,31 +673,20 @@
</ul>
<p>Possible organization of use cases (Adapted from <a href="http://bit.ly/wlKOEF" target="_blank">Trust and Linked Data</a>):</p>
+-->
+
</section> <!-- Pragmatic Provenance >> -->
<!-- VERSIONING -->
<section>
<h2>Versioning</h2>
-<!-- <p class="todo">To Review: John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Hadley Beeman (LinkedGov)</p> -->
-<p>
-This section specifies how to publish data which has multiple versions, including variations such as:
-<ul>
- <li>data covering different time periods</li>
- <li>corrected data about the same time period</li>
- <li>the same data published using different vocabularies, formats, and presentation styles</li>
- <li>retracting published data</li>
-</ul>
-</p>
-<p>The group will specify how to publish data which has multiple versions, including variations such as:</p>
-<ul>
- <li>data covering different time periods</li>
- <li>corrected data about the same time period</li>
- <li>the same data published using different vocabularies, formats, and presentation styles</li>
- <li>retracting published data</li>
-</ul>
+<p class="todo">(Editors) Propose that we remove Versioning because it has not been given sufficient attention by the WG to make a recommendation.</p>
+
+<!-- <p class="todo">To Review: John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Hadley Beeman (LinkedGov)</p> -->
+<!--
<p>
The Digital Library community has faced the problem of versions in digital repositories for more than a decade. One useful summary of thinking in this space can be found at the Version Identification Framework (VIF) Project site. See especially:
</p>
@@ -742,7 +698,7 @@
<p>The Resourcing IDentifier Interoperability for Repositories (RIDIR) project (2007-2008) considered in depth the relationship between identifiers and finding versions of objects. See RIDIR Final Report. In their words, RIDIR set out to investigate how the appropriate use of identifiers for digital objects might aid interoperability between repositories and to build a self-contained software demonstrator that would illustrate the findings. A number of related projects are listed at JISC's RIDIR information page.</p>
-<p>In addition, at TWC we have adopted an ad hoc approach to denoting versions of published linked data:</p>
+<p>In addition, at RPI we have adopted an ad hoc approach to denoting versions of published linked data:</p>
<ul>
<li>
The URI for the "abstract" dataset has no version information, e.g. http://logd.tw.rpi.edu/source/data-gov/dataset/1017
@@ -751,49 +707,24 @@
<li>The version indicator (e.g. "1st-anniversary") is arbitrary; a date code may be used. We sometimes use NON-ISO 8601 (e.g. "12-Jan-2012" to make it clear this is (in our case) not necessarily machine produced.</li>
</ul>
+-->
+
</section>
-<!-- << PROPOSE REMOVING STABILITY due to lack of input -->
<section>
-
<!-- << STABILITY.overview -->
<h3>Stability Properties</h3>
-<p><i>These are characteristics that influence the stability or longevity. Many of these properties are not unique to LOD, yet they influence data cost and therefore data value.</i></p>
-<ul>
- <li><b><u>Consistency.</u></b>Any design of a data format should recognize that change is necessary and will happen. Recognition that change is enviable while providing a mechanism for embracing modification increases continuity and longevity.
- The following types of changes can be anticipated. Therefore, data design should be made to accommodate them:
- <ol type="1">
- <li>The person who published the data changes jobs - For <u>Contact Consistency</u> - Any support contact information should be published using a data steward so that the inherent transition of responsibility does not introduce inconsistency to consumers.</li>
- <li>Departments, Agencies and Governments are reorganized - For <u>File Naming and Data Consistency</u> - Discourage the use of the originating source as component in the name of the data file, or the URIs it contains.The information can appropriately be contained within the file as metadata.</li>
- <li>IT infrastructure overhaul - <u>For File Naming Consistency</u> - Discourage the use of the server or system as component in the name of the data file.</li>
- <li>Merger/acquisition - For <u>Data Consistency</u> - Discourage the use of branding as it inherently and needlessly increases cost for new owners while providing no value at all to consumers.</li>
- <li>Primary stakeholder loses interest in the data - As above For <u>Data Consistency</u> - Discourage the use of branding as it inherently increase cost for new owners.</li>
- </ol>
- </li>
-<li><b><u>Organization.</u></b>The minimum metadata accompanying each data offering should include:
- <ol type="1">
- <li>Serialization type</li>
- <li>Publisher</li>
- <li>Creation Date</li>
- <li>Modification Date</li>
- <li>Version</li>
- <li>Email address for data steward</li>
- </ol>
-</li>
+<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government Linked Open Data, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
-<li>
-<b><u>Complexity.</u></b>All serializations are equal to a back-end system, therefore providers should serialize RDF in either
- <ul>
- <li>Turtle - The turtle serialization minimizes the disk space expenditure while also increasing human readability.</li>
- <li>NTriples - The NTriples serialization increases integrity in that re-ordering will have no effect on semantics, and damaged lines only effect the assertion on those lines. NTriples also increases flexibility because files can be split into smaller files as long as the division happen at the end of the line.</li>
- </ul>
-</li>
-
-Different serializations represent the same semantics but require varying amounts of characters (diskspace). While Turtle provides the most concise serialization and is arguably the easiest for humans to read. Turtle does not provide the integrity that NTriples does because NTriples can be reordered or split up based on size or line count without effecting the integrity of the dataset. In general NTriples will provide the greatest overall stability for LOD.
+<ul>
+<li>Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward for a given data set.</li>
+<li>Plan for departmental names and organizations to change - discourage the use of embedding originating source as a component of the data file name and/or URI. This information can and should be included as metadata in the RDF itself.</li>
+<li>Basic metadata should accompany each data set including: correct MIME type, publishing organization and/or agency, creation date, modification date, version, contact email for the data steward(s).</li>
+</ul>
</section>
@@ -801,14 +732,16 @@
<!-- SOURCE DATA -->
<section>
<h2>Source Data</h2>
-<!-- <p class='todo'>To Review: Michael Hausenblas (DERI), Spyros Kotoulas(IBM/SCTC), Biplav Srivastava (IBM)</p> -->
+
+<p class="todo"> (Biplav Srivastava/IBM) This is an important section but we're light on details (provide suggested approach, not a bunch of questions).
+</p>
<p>
This section contains advices concerning how to expose source data, data which is being maintained in pre-existing (non-linked-data) systems such as RDBs or spreadsheets.
</p>
-<p>In this section the group will produce specific advice concerning how to expose legacy data, data which is being maintained in pre-existing (non-linked-data) systems. Subject: Roadmap for cities to adopt open data</p>
+<!--
<p>Use case</p>
<p>Suppose a city is considering opening up its data. It has certain concerns:</p>
<ul>
@@ -826,46 +759,33 @@
<li>Can we provide a template implementation for the reference architecture?</li>
</ol>
</ul>
-<p>It is recommended that the publishing organization prepare a roadmap to address them for all stakeholders.</p>
-<br/>
-<p><b>Source Data publication check-list.</b> Before publishing your legacy data, be aware of the following elements of this list:</p>
-
-<p class="highlight"><b>Make sure the format of the data is not proprietary but rather standard formats e.g: csv, shp, kml, xml, DBMS, etc.</b><br/>
-</p>
+!-->
-<p class="highlight"><b>Provide access to the data: API, web page so that users can refer to consistently.</b> <br/>
-It is recommended to use the domain of your organization for trust.
+<h3>Source Data Publication Checklist</h3>
+
+<p class="todo"> (Biplav) - This seems redundant with other parts of the document. Should this be folded in above??
+
+<p class="highlight">Deliver open government data on authoritative domain to increase perceived trust.
</p>
-<p class="highlight"><b>Provide a small description of the data such as scope, content.</b> <br/>
-For tables, the names of the columns should be clear and self-descriptive if possible.<br/>
-In spreadsheet, avoid having many sheets in the same book.
-</p>
-
-<p class="highlight"><b>Provide the type of license to be used for accessing the data.</b><br/>
+<p class="highlight">Provide access to human and machine readable data via RESTful API, SPARQL endpoint or RDF download. <br/>
</p>
-
-<p class="highlight"><b>Check also the frequency of the publication and provide that information.</b><br/>
+<p class="highlight">Provide basic metadata, i.e., MIME type, publishing organization and/or agency, creation date, modification date, version, frequency of updates, contact email for the data steward(s).
</p>
-<p class="highlight"><b>Provide additional documents explaining the key concepts/terms of your data to avoid misinterpretation.</b><br/>
+<p class="highlight">Specify an appropriate license<br/>
</p>
-
-<p class="highlight"><b>Provide a contact address/email of the role responsible for the data for any further support.</b><br/>
-</p>
-
-<p class="highlight"><b>Be privacy aware when publishing data.</b><br/>
-Although any data that is published can be potentially misused later by an unknown party, the threat is balanced by benefits by privacy groups (including <a href="http://www.w3.org/Privacy/" target="_blank">W3C Privacy</a>) to provide recommendations. Follow them. Start by not revealing personally identifiable information without masking. Examples of such data are - individual names, national identification number, phone number, credit card number and driver license number.
+<p class="highlight">Do not Publish Personally Identifiable Information as Open Data on the Web</b><br/>
+Data on the public Web can be potentially misused, however the threat is balanced by benefits by privacy groups (including <a href="http://www.w3.org/Privacy/" target="_blank">W3C Privacy</a>) to provide recommendations. Examples of personally identifiable data are - individual names, national identification number, phone number, credit card number and driver license number.
</p>
</section>
-
<!-- REFERENCE: LINKED DATA COOKBOOK -->
<section>
<h2>References</h2>
@@ -880,15 +800,11 @@
<!-- ACK -->
<section class="appendix">
<h2>Acknowledgments</h2>
-<!-- <h3>Material Contributions</h3>
-
+ This document has been produced by the Government Linked Data Working Group, and its contents reflect extensive discussion within the Working Group as a whole.
<p>
-The editors gratefully acknowledge the many contributors to this Best Practices document including:
-Michael Pendleton (US EPA), John Erickson (RPI), Ghislain Atemezing (INSTITUT TELECOM), Daniel Vila (UPM), Martin Alvarez (CTIC), David Wood (3 Round Stones), ...
+The editors gratefully acknowledge the many contributors to this Best Practices document including: John Erickson (<a href="http://logd.tw.rpi.edu/">(Rensselaer Polytechnic Institute)</a>, David Wood <a href="http://3roundstones.com">(3 Round Stones)</a>, Bernard Vatant <a href="http://data.semanticweb.org/person/bernard-vatant/">(Semantic Web - Modeca)</a>, Michael Pendleton <a href="http://www.epa.gov/">(U.S. Environmental Protection Agency)</a>, Biplav Srivastava <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088">(IBM India)</a>, Daniel Vila <a href="http://www.oeg-upm.net">(Ontology Engineering Group)</a>, Martín Álvarez Espinar <a href="http://www.fundacionctic.org/">(CTIC-Centro Tecnológico)</a>, and Hadley Beeman <a href="http://linkedgov.org">(UK LinkedGov)</a>.
+
</p>
-<p>
-The editors are also very thankful for comments and suggestions ...
-</p>-->
</section>
</body>
</html>
--- a/bp/respec-config.js Tue Mar 12 22:42:31 2013 -0400
+++ b/bp/respec-config.js Wed Mar 13 01:20:11 2013 -0400
@@ -32,8 +32,9 @@
// editors, add as many as you like
// only "name" is required
editors: [
- { name: "Bernadette Hyland", url: "http://3roundstones.com/about-us/leadership-team/bernadette-hyland/", company: "3 Round Stones, Inc", companyURL: "http://3roundstones.com/"},
+ { name: "Bernadette Hyland", url: "http://3roundstones.com/about-us/leadership-team/bernadette-hyland/", company: "3 Round Stones, Inc.", companyURL: "http://3roundstones.com/"},
{ name: "Boris Villazón-Terrazas", url: "http://boris.villazon.terrazas.name", company: "iSOCO, Intelligent Software Components S.A.", companyURL: "http://www.isoco.com"},
+ { name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin/", company: "EURECOM", companyURL: "http://www.eurecom.fr/en"}
],
// authors, add as many as you like.
@@ -41,17 +42,7 @@
// only "name" is required. Same format as editors.
//authors: [],
- authors: [
- { name: "Bernadette Hyland", url: "http://3roundstones.com/about-us/leadership-team/bernadette-hyland/", company: "3 Round Stones, Inc", companyURL: "http://3roundstones.com/"},
- { name: "Boris Villazón-Terrazas", url: "http://boris.villazon.terrazas.name", company: "iSOCO, Intelligent Software Components S.A.", companyURL: "http://www.isoco.com"},
- { name: "Ghislain Atemezing", url: "http://www.eurecom.fr/~atemezin/", company: "EURECOM", companyURL: "http://www.eurecom.fr/en"},
- { name: "John Erickson", url: "http://logd.tw.rpi.edu/", company: "Rensselaer Polytechnic Institute", companyURL: "http://logd.tw.rpi.edu/"},
- { name: "Bernard Vatant", url: "http://data.semanticweb.org/person/bernard-vatant/", company: "Mondeca", companyURL: "http://www.mondeca.com"},
- { name: "Michael Pendleton", url: "http://www.epa.gov/", company: "U.S. Environmental Protection Agency", companyURL: "http://www.epa.gov"},
- { name: "Biplav Srivastava", url: "http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088", company: "IBM Corporation", companyURL: "http://www.ibm.com/in/en/"},
- { name: "Daniel Vila", url: "http://www.oeg-upm.net", company: "Ontology Engineering Group", companyURL: "http://www.oeg-upm.net"}
- ],
-
+
// name of the WG
wg: "Government Linked Data Working Group",