GLD Work Items

From Semantic Web Standards
Revision as of 20:03, 18 November 2010 by Sandro (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This is discussion draft, especially for eGov IG @ TPAC 2010. Meeting Notes.

Please add constructively to this document. For an example of how it might look when more complete, see RDF Core Work Items. (Don't worry about the formatting yet.)

__NUMBEREDHEADINGS__

1 Background

The following work items have been proposed or suggested as possibly in-scope for a proposed Government Linked Data (GLD) Working Group. This is a discussion document, for gathering feedback. Almost certainly, some of these items will not be in-scope for the Working Group.

The group is expected to begin meeting around April 1 and be chartered for two years. To reduce travel, face-to-face meetings might be done with split video-conferencing, where people gather in multiple locations (such as Brussels and Washington, D.C.) which are connected by a high-quality video link.

2 Deployment Assistance Work Items

These items are relatively non-technical in nature and are aimed at generally making it easy to deploy GLD solutions.

2.1 Procurement Definitions

Produce documents which make it much simpler for governments to specify linked data products and services they wish to purchase. This may be in the form of W3C Recommendations which procurement documents may reference, saying (essentially), "We want one of these."

2.2 License Framework

Gather examples and experiences about licenses for GLD, toward building a framework from which suitable licenses can be constructed (perhaps like Creative Commons).

2.3 Community Survey

Produce a self-sustaining database of GLD vendors (including contract programmers), GLD deployments (users), and communities focused on government data and linked data.

2.4 Cookbook or Storybook

Gather a collection of problems faced in deploying GLD, along with stories about solutions which have been attempted (whether or not they were deemed to be successful).

2.5 Outreach

The WG will be mindful of the need to explain and promote its work to governments and government agencies around the world. Although not a specific task of the WG itself, outreach is a critical aspect of the broader task of making government data more open and more usable by more applications. Such outreach work must take note of differing political agendas.

2.6 Legacy Data

Access in the Linked Data world to data in other forms

3 Liaison Work Items / Dependencies

Work with other W3C groups to help ensure they develop suitable technologies.

3.1 Provenance

Ensure GLD use cases are addressed by Provenance WG (if it materializes).

3.2 Named Graphs in RDF Core

Ensure GLD uses cases are address by RDF Core's named graph solution (if it materializes).

3.3 Points of Interest (POI) WG

Ensure that gov't use cases are addressed.

3.4 Identity and Authentication

Ensure that W3C Workshops/WGs on identity are informed of GLD use cases

4 Vocabulary Development Work Items

For each item, develop a document which lists recommended RDF vocabulary terms, with high-quality human documentation and ontologies, if not already provided by other sources.

Note that this means terms do not need to be reinvented. In some cases, the group may succeed by simply agreeing to recommend some existing vocabulary, or certain terms from some existing vocabulary.

4.1 Metadata for Data Catalogs

eg dcat.

cf ckan

4.2 Organizational Information

4.3 People

cf foaf, vcard, ...

4.4 Statistical/Data Cube Datasets

4.5 Data Quality, Timeliness, Status

4.6 Assumptions/Basis/Comparability of Data

4.7 Describing Visualization and Presentation

4.8 Alignment Properties

Something like owl:sameAs or skos (but without it being a skos:Concept).

cf RDF Next Steps

5 Other Technical Development Work Items

5.1 Design Patterns for URIs

Produce guidance for minting URIs.

Update of http://www.w3.org/TR/cooluris/

UK URISets document

5.2 Versioning of Datasets

Explain/standardize how to publish data which changes, allowing for archiving and updating.

5.3 Change Propagation and Notification

Explain/standardize systems for efficiently distributing changes to datasets.

5.4 Distributed Query

Explain/standardize how to deploy a system with a central point of SPARQL querying and multiple loosely-coupled SPARQL data sources.

5.5 Developer-Friendly API and Serialization

cf Linked Data API

cf JSON in RDF (in RDF Core)