Table of Contents

• 1. Summary of Best PracticesPrepare Stakeholders
• 2. Preparing to Publish Linked Open Data 3.Select a Dataset
• 4.3. Model the Data
• Modeling 5. Basic Metadata 6. Personal Identifiable Information 7.4. Specify an Appropriate License
• 8. Convert Data to5. The Role of "Good URIs" for Linked Data
• 9. URI Design Principles 10. URI Construction 11. URI Policy for Persistence 12. Internationalized Resource Identifiers 13.6. Standard Vocabularies
• 14. Vocabulary Checklist 15. Vocabulary Creation 16. Using SKOS7. Convert Data to Create a Controlled Vocabulary 17. Multilingual Vocabularies 18. PublishingLinked Data
• for Access and Reuse 19.8. Provide Machine Access to Data
• 20. Domain and Hosting 21.9. Announce to the Public
• 22.10. Social Contract of a Linked Data Publisher
• 23. Stability PropertiesA. Acknowledgments
• B. References
  • B.1 Informative references

The following best practices are discussed in this document and listed here for convenience.

PREPARE:STEP #1 PREPARE STAKEHOLDERS:
Prepare stakeholders by explaining the high level workflow orprocess involved in publishingof creating and usingmaintaining Linked Open Data.

STEP #2 SELECT A DATASET:
Select a dataset that provides benefit to others for re-use. MODEL:reuse.

STEP #3 MODEL THE DATA:
Modeling Linked Data involves representing data objects and how they are related in an application-independent way.

BASIC METADATA: Always provide basic metadata . PERSONAL IDENTIFIABLE DATA: Do not publish personal identifiable information as Linked Open Data as it can potentially be misused.STEP #4 SPECIFY AAN APPROPRIATE LICENSE:
Specify an appropriate open license with the published data.data CONVERSION: Convertlicense. Data reuse is more likely to occur when there is a clear statement about the origin, ownership and terms related to the use of the published data.

STEP #5 GOOD URIs FOR LINKED DATA:
The core of Linked Data representation, typically done by script or other automated processes. HTTP URIs: Createis a well-considered URI naming strategy and implementation plan, based on HTTP URIs as names for your objects. Give careful. Consideration to the URIfor naming strategy. Consider how theobjects, multilingual support, data willchange over time and name as necessary. STANDARD_VOCABULARIES: Describepersistence strategy are the building blocks for useful Linked Data.

STEP #6 USE STANDARD VOCABULARIES:
Describe objects with previously defined standardvocabularies whenever possible. Extend standard vocabularies where necessary.necessary, and create vocabularies (only when required followingrequired) that follow best practices whereverwhenever possible.

PUBLISHSTEP #7 CONVERT DATA:
Convert data FOR ACCESS AND REUSE: Select, model and publish dataset(s) with linksto other interestinga Linked Data thereby making it immediately more useful.representation. This is typically done by script or other automated processes.

STEP #8 PROVIDE MACHINE ACCESSIBLE:ACCESS TO DATA:
Provide various ways for search engines and other automated processes to access data using standard Web mechanisms.

DOMAIN AND HOSTING: Deliver Linked OpenSTEP #9 ANNOUNCE NEW DATA SETS:
Remember to announce new data sets on an authoritative domain. ANNOUNCE: Announce the Linked Open Data on multiple channels and haveImportantly, remember that as a plan in place to support it over time. SOCIAL_CONTRACT: PublishingLinked Open Data onpublisher, an implicit social contract is in effect.

STEP #10 RECOGNIZE THE Web implies aSOCIAL contract. Associating a good openCONTRACT:
Recognize your responsibility in maintaining data license is necessary. Regular updates and maintenance is a requirement. A permanent identifier schemeonce it is highly recommended. If authorities move or remove datapublished. Ensure that is published tothe Web, third party applications or mashups can break, whichdataset(s) remain available where your organization says it will be and is clearly undesirable. 2. Preparing to Publish Linked Open Datamaintained over time.

1. Prepare Stakeholders

Preparation and setting expectationsis crucial for any project's success. Prepare stakeholders with a discussion on the goalssuccess of Linked Data, as well as,an information management project. Sharing with government stakeholders the processbenefits of producing Linked Opendata .sharing in terms of their agency mission or charter helps ensure success. The concepts of data modeling will be familiar to information management professionals. While the specifics and goalsof Linked Open Data may be new to stakeholderspeople who are used to traditional data management however,information manaagement approaches, they are well-documented in W3C Recommendations, Notes and many peer reviewed publications [WOOD2013], [howto-lodp], [BHYLAND2011], [BVILLAZON]. Linked Data has entered the mainstream. Itmainstream and is used by governments large and small,around the world'sworld, major search engines, international firmscorporations and agile startups.

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.

• 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.

• 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.

• 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.

3.2. Select a Dataset

When publishing a dataset, select data that is uniquely collected or created by your organization. Ideally, this information when combined with other open data provides greater value. Government agencies are in a unique position to collect and curate valuable datasets. Since there is effort and cost associated with modeling, publishing and maintaining any data set as a public service, selection of high value data sets may be guided re-use potential and popularity, among other factors. Data about geographic features, human health, legislation, population and demographics, and the environmental data are just some of the popular open government data sets that have been published as Linked Open Data.

For example, publishing regulated facilities that can then be linked with latitude and longitude allows the facilities to be plotted on a map. That data can then be extended using post codes allowing people to search via post code what facilities are near them on a map view. Facilities data published as extensible Linked Data allows Web developers to rapidly build Web interfaces that are both useful to machines and humans.

4. Data Modeling Modeling Linked3. Model the Data

During the data canmodeling phase, at least one individual familiar with the logical model and is used within government agencies to improve data integration for related or complementary information.the processschema of data modelingthe dataset should involve someone whobe involved. Typically, this person is intimatelya database administrator or application developer very familiar with the representationmeaning of the data. Additionally, including a Linked Data using open Web standards. Familiarity with standard vocabulariessubject matter expert will both expediteassist in the modeling process and help produce data that can be more readily linked to other data sets. 5.process.

Provide Basic Metadata

AlwaysWhen modeling Linked Data, it is a best practice to provide basic metadata, 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,subsequent sections, further guidance on the use of existing standardvocabularies, extending a standard vocabulary and creatingas well as a newvocabulary "checklist" are provided as further informative guidance. 6. Personal Identifiable Information Do not publish personally identifiable informationguidance as they play a key role in the Linked OpenData 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. Exceptionsmodeling process to this practice may include public information required by law, such as individual names, office extensions, salaries and tax information, for some public officials. 7. Specify an Appropriate Licenseencourage reuse.

4. Specify an Appropriate openLicense

OneIt is important to specify who owns data published on the Web and to explicitely connect that license with the data itself. Governmental authorities publishing open data are encouraged to review the relevant guidance for open licenses and copyright. Publishing Linked Open Data makes associating a license that travels with the data itself easy. Thus, people are more likely to reuse data when there is a clear, acceptable license associated with it.

A valuable resource isfor open data publishers to review may be found on the Creative Commons Web site. Creative Commons develops, supports, and stewards legal and technical infrastructure for digital content publishing.

5. The Role of processing. 9."Good URIs" for Linked Data

URI Design Principles

The Web makes use of the URI 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 resources using URIs. This section provides a set of general principles aimed at helping government stakeholders to define and manage URIs for their resources.

Use HTTP URIs
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.

Provide at least one machine-readable representation of the resource identified by the URI
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 URI structure will not contain anything that could change
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] andArchitecture of the World Wide Web: URI Opacity.

URI Opacity
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: Agents making use of URIs SHOULD NOT attempt to infer properties of the referenced resource. 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.

10.URI Construction The following guidance is has been developed by organizations involved inPolicy for Persistence

Defining and documenting a persistent URI strategypolicy and implementation for government agencies: Cool URIs forplan is vital to the Semantic Web [ COOLURIS ] Designing URI Sets forongoing success and stability of publishing open government data.

The UK Public Sector [ uk-govuri ] Designing URI Sets foreffect of changing or moving resources has the UK Public Sector ,effect of breaking applications dependent upon it. Therefore, government authorities should define 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; Creating URIs (data.gov.uk). --> 10 rules for persistent URI Draft URIpersistence strategy for the NL Public Sector (PDF) General-purpose guidelines exist for the URI designerand implementation plan to consider, including Cool URIs forprovide content using the Semantic Web , which provides guidance on how to use URIs to describe things that are notsame Web documents; Style Guidelines for Naming and Labeling Ontologies inaddress, even though the Multilingual Web (PDF) 11. URI Policy for Persistenceresources in question may have moved. 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 additionreal world and concepts, in addition to information resources.

The choice of a particular URI scheme provides no guarantee that those URIs will be persistent. URI persistence is a matter of policy and commitment on the part of the URI owner. HTTP [RFC2616] has been designed to information resources.help manage URI persistence. For example, persistent identifiers have been created byHTTP redirection (using the United Nations Food and Agriculture Organization (FAO)3xx response codes) permits servers to provide URIs for major food crops. The National Center for Biomedical Ontology provides persistent identifierstell an agent that further action needs to unify and addressbe taken by the terminology usedagent in many existing biomedical databases. The US Government Printing Office uses persistent identifiers to pointorder to documents likefulfill the U.S. Budget that are deemed essential torequest (for example, a democratic, transparent government.new URI is associated with the resource).

The PURL concept allows for generalized URL curation of HTTP URIs on the World Wide Web. PURLs allow third party control over both URL resolution and resource metadata provision. 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 ofdesign 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.

The Open Source PURLs Project is used widely to run persistent identifier management sites. The Open Source PURLs Project is used by libraries, academic organizations, government agencies and non-government organizations around the world. For example, persistent URLs are used by the United Nations Food and Agriculture Organization (FAO) to provide URIs for major food crops. The National Center for Biomedical Ontology provides persistent URLs to unify and address the terminology used in many existing biomedical databases. The US Government Printing Office also uses persistent URLs to point to documents like the U.S. Budget that are deemed essential to a democratic, transparent government.

Recently, a software project called Permanent Identifiers for the World Wide Web, but may be partially restored by allowing resource users or third partiesWeb emerged to influence where and howprovide a secure, permanent URL resolves. A simple PURL works by respondingre-direction service for Web applications. The service operates in HTTPS-only mode to an HTTP GET request with a responseensure end-to-end security. This means that it may be used for Linked Data applications that require high levels of type 302 (“Found”). The response contains an HTTP “Location” header,security such as those found in the value of which isfinancial, medical, and public infrastructure sectors. A URLgrowing group of organizations that have pledged responsibility to ensure the client should subsequently retrieve via a new HTTP GET request.operation of this website over time. Those interested in learning more are encouraged to contact the W3C Permanent Identifier Community Group.

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 identificationschemesidentification schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, “the active involvement of information professionals in the management, including the preservation, of digital data for future use.” [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.

URI persistenceConstruction

The following guidance is a matter of policyhas been developed by organizations involved in URI strategy and commitment on the part ofimplementation for government agencies:

• Cool URIs for the Semantic Web [COOLURIS]
• Designing URI owner.Sets for the choice of a particular URI scheme provides no guarantee that those URIs will be persistent or that they will not be persistent. HTTPUK Public Sector [ RFC2616uk-govuri]
• has been designed to help manageDesigning URI persistence.Sets for example, HTTP redirection (usingthe 3xx response codes) permits servers to tell an agentUK Public Sector, a document from the UK Cabinet offices that further action needsdefines the design considerations on how to URIs can be taken byused to publish public sector reference data;
• Study on Persistent URIs with identification of best practices and recommendations on the agent in order to fulfilltopic for the request (for example,Member States and the European Commission
[PARCHER]
• Towards a newNL URI is associated withStrategy

General-purpose guidelines exist for the resource). In addition, content negotiation also promotes consistency, as a site manager is not requiredURI designer to define newconsider, including

• Cool URIs when adding supportfor 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. Improperthe Semantic Web, which provides guidance on how to use of content negotiation can leadURIs to inconsistent representations. 12.describe things that are not Web documents;
• Style Guidelines for Naming and Labeling Ontologies in the Multilingual Web (PDF)

Internationalized Resource Identifiers

Stakeholders who are planning to create URIs using characters that go beyond the subset defined in [RFC3986] are encouraged to reference IRIs. Defined in (RFC 3987 )), IRI is a protocol element,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].

The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the IETF in March 2003.

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.

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 An Introduction to Multilingual Web Addresses, however some of the most relevant issues are following:

• Domain Name lookup: Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as .cn, .jp, .kr , etc., and global top level domains such as .info, .org and .museum.
• Domain names and phishing: 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.
• Encoding problems: 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 uniformlyuniform 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] .

The URI syntax defined in [RFC3986] 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. 13.6. Standard Vocabularies

Standardized vocabularies should be reused as much as possible to facilitate inclusion and expansion of the Web of data. The W3C has published several useful vocabularies for Linked Data. For example, the following standard vocabularies help developers to describe basic or more complex relationships for describing data catalogs, organizations, and multidimentionalmultidimensional data, such as statistics on the Web. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.

Specifically, Data Catalog Vocabulary (DCAT) [vocab-dcat] 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.

Organizational structures and activities are often described by government authorities. The Organization Ontology [vocab-org] supports the 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 neighboring information such as organizational activities.

Many government agencies publish statistical information on the public Web. The Data Cube Vocabulary [vocab-cube] provides a means to do this using the Resource Description Framework (RDF). CSARVENón-Capadisli propose in [ CSARVEN ]The RDF Data Cube Vocabulary makes it possible to discover and identify statistical data artifacts in a uniform way and presents a design and implementation approach using the Data Cube Vocabulary.way.[CSARVEN] 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 datasets.

How to Find Existing Vocabularies

Where to find existing vocabularies in data catalogues
Another way around is to perform search using the previously identified key terms in datasets catalogs. Some of these catalogs provide samples of how the underlying data was modeled and used. One popular catalogue is the: Data Hub.

18. Publishing7. Convert Data for Access and Reuse While organizations aroundto Linked Data

Now with the globe are making very valuable steps in government transparency by publishing datasetsground work in non-proprietary formats such as CSV and PDF, strivingplace, the next step is to publish authoritativeactually convert a dataset into a Linked Data representation. There is more than one way to convert data including scripts, declarative mapping languages, languages that perform query translation rather then data translation (e.g. R2RML). Regardless of which approach is used, data conversion involves mapping the source data into a set of RDF statements. As 5 Stardata is converted, data is serialized into RDF statements. RDF can be converted into a range of RDF serializations that include:

• RDFa,
• JSON-LD,
• Turtle and N-Triples,
• RDF/XML

8. Provide Machine Access to Data

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:

• A RESTful API,
• a SPARQL endpoint, and/or
• via file download.

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].

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 list of some SPARQL endpoints may be found here.

20. Domain and Hosting 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 critical9. Announce to re-use of authoritative datasets.the Public

21. AnnounceNow you're ready to point people to authoritative open government data. Be sure the Public Announcedatasets are available via an authoritative domain. Using an authoritative domain increases the Linked Openperception of trusted content. Authoritative data that is regularly updated on multiple channels including mailing lists, blogs, newsletters and traditional fora. Be sure to havea plan in placegovernment domain is critical to handle timely feedback.re-use of authoritative datasets.

The publicfollowing checklist is looking at and counting on yourintended to help organizations realize the benefits of publishing open government data, so ensure you have people in placeas well as, communicate to handlethe customer servicepublic that you are serious about providing this data over time.

• Use multiple channels including mailing lists, blogs and technical support required to support the public audience. The following is intendednewsletters to help your organizationannounce useful new datasets and help fulfill the implicit social contract: Notea newly published data set;
• Publish a description for each published dataset using [vocab-dcat] or [void] vocabulary;
• Define the frequency of data updates (as metadata);
• Associate an appropriate license;
• Plan and implement a persistence strategy;
• Ensure data is accurate to the greatest degree possible;
• Provide a form to give useful feedback. Forms help with structure; Publish an email addressfor people to report problematic data;data and give feedback;
• Provide a contact email address (alias) to team membersfor those responsible for curating and publishing the data. 22.data;
and
• Ensure staff have the necessary training to respond in a timely manner to feedback.

10. Social Contract of a Linked Data Publisher

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.

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. 23.Below we provide an introduction to the best practice of defining a persistence strategy and implementation plan.

Stability Properties

Several data properties that a government authorities should contemplate in their published data strategy include: Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward forAs a given dataset. Plan for departmental names and organizationsfinal note related to change - discouragethe use of embedding originating source as a componentimportance of the data file name and/or URI. This information can and should be included as metadata in the RDF itself. 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).stability. The W3C willprepares to 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 data stability as the vast majority of government data is quickly available only 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!