This document provides best practices and guidance to create high quality, re-usable Linked Open Data (LOD).

This document is work in progress. You might also want to check the accompanying Wiki page of the GLD Working Group for ongoing discussions.

Scope

This document is aimed at assisting government agencies and their contractors, vendors as well as researchers, to publish high quality, consistent data sets using W3C standards to increase interoperability.

Introduction

Overview

Linked Data addresses key requirements of open government by providing a family of international standards for the publication, dissemination and reuse of structured data. Further, Linked Data, unlike previous data formatting and publication approaches, provides a simple mechanism for combining data from multiple sources across the Web.

In an era of reduced local, state and federal budgets, there is strong economic motivation to reduce waste and duplication in data management and integration. Linked Open Data is a viable approach to publishing governmental data to the public, but only if it adheres to some basic principles.

Motivation

Th best practices provided here are provide a methodical approach for the creation, publication and dissemination of government Linked Data, including:

QUESTION: would it make sense to base the above mentioned GLD life cycle on the general Linked Data life cycles?

Procurement

TBD

Specific products and services involved in governments publishing linked data will be defined, suitable for use during government procurement. Just as the Web Content Accessibility Guidelines allow governments to easily specify what they mean when they contract for an accessible Website, these definitions will simplify contracting for data sites and applications.

Vocabulary Selection

Michael Hausenblas (DERI), Ghislain Atemezing (INSTITUT TELECOM), David Price (TopQuadrant), Boris Villazon-Terrazas (UPM)

The group will provide advice on how governments should select RDF vocabulary terms (URIs), including advice as to when they should mint their own. This advice will take into account issues of stability, security, and long-term maintenance commitment, as well as other factors that may arise during the group's work.

URI Construction

Ghislain Atemezing (INSTITUT TELECOM), Michael Hausenblas (DERI), Boris Villazon-Terrazas (UPM), John Erickson (RPI)

This section specifies how to create good URIs for use in government linked data. Inputs include Cool URIs for the Semantic Web, Designing URI Sets for the UK Public Sector (PDF), and Creating URIs (data.gov.uk). Guidance will be produced not only for minting URIs for governmental entities, such as schools or agencies, but also for vocabularies, concepts, and datasets.

Versioning

Dean Allemang (TopQuadrant), Cory Casanave (OMG), Hadley Beeman (LinkedGov)

This section specifies how to publish data which has multiple versions, including variations such as:

Stability

TBD

This section specifies how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary.

Legacy Data

David Price (TopQuadrant), Michael Hausenblas (DERI)

This section contains advices concerning how to expose legacy data, data which is being maintained in pre-existing (non-linked-data) systems.

Cookbook

Bernadette Hyland (3 Round Stones)

This section provides a collection of advice on smaller, more specific issues, where known solutions exist to problems collected for the Community Directory. This part is going to be separated out as a Working Group Note, or website, rather than a Recommendation. It may, instead, become part of the Community Directory site.

ISSUE-1: decide how to proceed with this section; maybe intro here and then link to website?

Acknowledgments

The editors are very thankful for comments and suggestions ...