Government Linked Data Working Group CharterThis group will develop standards-track documents and maintain a community website in order to help governments at all levels (from small towns to nations) share their data as high quality ("five-star") linked data. This group is exclusively focused on data publication using Semantic Web standards, deployed on the Web following linked data principles, as introduced by Tim Berners-Lee in 2006, in Linked Data.Government Linked Data Working GroupGLD_cd86386e-e4a2-11e0-8f9e-24647a64ea2aThe GLD, a part of the eGovernment Activity and closely connected with the Semantic Web Activity, will collect and make available information about government Linked Data activities around the world. It will use that information and the experience of its participants to develop W3C Recommendations for Best Practices and for RDF Vocabularies necessary for publication of government data in RDF, as Linked Data. Concurrently with this Working Group, W3C has chartered the eGovernment Interest Group for broad community discussion of government use of the Web ParticipantsIn general, people participate in this group as representatives of W3C member organizations. At least one representative from each participating organization is expected to devote significant time to this effort (about one day per week, or more, depending on duties), to accept and complete appropriate action items on a timely basis, and to travel to face-to-face meetings, as scheduled by the chairs, 2-4 times per year.On a case-by-case basis, using the invited expert process, people may be allowed to participate as individuals, not representing an organization.To be successful, the Working Group is expected to have between ten and thirty active participants for its duration.Participants are reminded of the Good Standing requirements of the W3C Process.eGovernement Interest Group The IG may be able to provide use cases, contacts, and information for the Community Directory. If it does a Community Directory project, the two might share data and infrastructre. If it does Data Licensing, it will be important to make sure any details that need to be different for Linked Data are noted.Provenance WG The Provenance Interchange Working Group is chartered to support the widespread publication and use of provenance information of Web documents, data, and resources. Its work is likely to be very useful for government linked data deployments, and the GLD WG should make sure its use cases are understood and, if possible, addressed by this group.RDF WG The RDF WG can provide technical reviews and its work could potentially be informed by use cases provided by GLD WG.Points of Interest (POI) WG The POI WG may provide the the Geography vocabulary, or at least settle some of the design issuesW3C Offices The W3C Offices may serve as an effective way to reach governments around the world._cd863ada-e4a2-11e0-8f9e-24647a64ea2aTo provide standards and other information which help governments around the world publish their data as effective and usable Linked Data using Semantic Web technologies._cd863c2e-e4a2-11e0-8f9e-24647a64ea2aCommunity DirectoryConstruct and maintain an online directory of the government linked data community._cd863d1e-e4a2-11e0-8f9e-24647a64ea2a2.1The Working Group will construct and maintain an online directory of the government linked data community, containing the following items:* Deployments, at every stage of the effort from initial consideration to maturity, with (when available) success stories, lessons learned, and ongoing challenges (concrete use cases)* Vendors of linked data products and services* Contractors (firms and individuals) offering linked data services* End-User Applications which are available to the general public* Optionally: Research groups, researchers, and sources of research funding* Optionally: Outreach and Advocacy groups, individuals, and funding sources* Optionally: Training materials and programs, including classes, tutorials, and books_cd863ddc-e4a2-11e0-8f9e-24647a64ea2aBest PracticesProduce one or more Recommendations [pertaining to] Best Practices for Publishing Linked Data_cd863e9a-e4a2-11e0-8f9e-24647a64ea2a2.2The group will produce one or more Recommendations which address the following issues:ProcurementDefine specific products and services involved in governments publishing linked data._cd863f62-e4a2-11e0-8f9e-24647a64ea2a2.2.1Specific 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 SelectionProvide advice on how governments should select RDF vocabulary terms._cd86402a-e4a2-11e0-8f9e-24647a64ea2a2.2.2The 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 ConstructionSpecify how to create good URIs for use in government linked data._cd8640fc-e4a2-11e0-8f9e-24647a64ea2a2.2.3The group will specify 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.VersioningSpecify how to publish data which has multiple versions._cd8641e2-e4a2-11e0-8f9e-24647a64ea2a2.2.4The group will specify how to publish data which has multiple versions, including variations such as:* data covering different time periods* corrected data about the same time period* the same data published using different vocabularies, formats, and presentation styles* retracting published dataStabilitySpecify how to publish data so that others can rely on it being available in perpetuity._cd8642c8-e4a2-11e0-8f9e-24647a64ea2a2.2.5The group will specify how to publish data so that others can rely on it being available in perpetuity, persistently archived if necessary. Legacy DataProduce specific advice concerning how to expose legacy data._cd8643b8-e4a2-11e0-8f9e-24647a64ea2a2.2.6The group will produce specific advice concerning how to expose legacy data, data which is being maintained in pre-existing (non-linked-data) systems.CookbookProduce a collection of advice on smaller, more specific issues, where known solutions exist to problems collected for the Community Directory._cd8644b2-e4a2-11e0-8f9e-24647a64ea2a2.2.7The group will produce a collection of advice on smaller, more specific issues, where known solutions exist to problems collected for the Community Directory. This document is to be published as a Working Group Note, or website, rather than a Recommendation. It may, instead, become part of the Community Directory site. Standard VocabulariesDevelop one or more W3C Recommendations to guide governments publishing data in which RDF vocabulary terms to use in information about certain common concept areas._cd8645b6-e4a2-11e0-8f9e-24647a64ea2a2.3The group will develop one or more W3C Recommendations to guide governments publishing data in which RDF vocabulary terms to use in information about certain common concept areas. The publishing granularity, in terms of which topics are covered in which documents, is left to the group to decide.The group will have to determine whether it is better to reuse existing widely-deployed terms such as foaf:name and dc:temporal, in their existing name space, or mint new URIs in a w3.org name space. Even if the group decides to mint new URIs, it should link them to equivalent concepts (using, for example, owl:equivalentProperty links) unless there are strong reasons not to.The decisions behind these deliverables will be closely related to the Best Practice advice on Vocabulary Selection (above), although the factors affecting W3C URIs are somewhat different from those affecting government URIs.The group will gather and publish use cases and requirements for vocabularies to cover each of the following areas, and it will produce W3C Recommendation(s) defining the meaning and usage of each element in these vocabularies, where they are not already defined in suitable open standards. The group will also produce documentation, examples, and, optionally, test cases and OWL ontologies for these vocabularies.MetadataGather and publish use cases and requirements for metadata for provenance, data catalogs, data quality, timeliness, status, and refresh rate._cd8646ec-e4a2-11e0-8f9e-24647a64ea2a2.3.1Provenance Interchange Working GroupLibrary Linked Data Incubator GroupMetadata, suitable for provenance (in coordination the Provenance Interchange Working Group), data catalogs (see the dcat data catalog vocabulary and the Comprehensive Knowledge Archive Network CKAN, and VoiD), data quality, timeliness of data, status, refresh rate, etc. The Library Linked Data Incubator Group reports offer some use cases and possible technical inputs. One challenge in metadata is granularity, as some attributes apply to vast ongoing collections of data, while others apply to particular triples, and most apply to some intermediate size dataset or graph.Statistical Cube DataGather and publish use cases and requirements for statistical cube data._cd864818-e4a2-11e0-8f9e-24647a64ea2a2.3.2Statistical "Cube" Data. The group will produce a vocabulary, compatible with SDMX, for expressing some kinds of statistical data. This need not be as expressive as all of SDMX, but may provide a subset as in the RDF Data Cube vocabulary. It may also include ways to annotate data to indicate its assumptions and comparability.PeopleGather and publish use cases and requirements for data pertaining to people._cd8649a8-e4a2-11e0-8f9e-24647a64ea2a2.3.3People, such as elements of FOAF or vCard in RDF. This is an area for particular attention to privacy considerations. Organizational StructuresGather and publish use cases and requirements for data for organizational structures._cd864ae8-e4a2-11e0-8f9e-24647a64ea2a2.3.4Such as the Epimorphics the organization ontology (see also its requirements document). Spatial InformationGather and publish use cases and requirements for spatial information._cd864c32-e4a2-11e0-8f9e-24647a64ea2a2.3.5optional: Geography, Spatial Information, such as latitude and longitude. Inputs include W3C Geospatial Ontologies Incubator Report the European INSPIRE Directive, and vocabulary elements of GeoSPARQL. (See liaisons.)2011-06-302013-05-312011-09-21http://www.w3.org/2011/gld/charterOwenAmburOwen.Ambur@verizon.net