This document defines the design considerations and guidance by which UK public sector Universal Resource Identifier (URI) sets should be developed and maintained. They are designed both to encourage those that definitively own reference data to make it available for re-use, and to give those that have data that could be linked, the confidence to re-use a URI set that is not under their direct control.
Keywords: HTTP URIs, Dereferencability, Content negotiation, Government Open Data
Author: Davidson, Paul
Publisher: Chief Technology Officer (CTO) Council’s Information Domain
Date created: 2009-09-10 04:00:00.000
Time required: P30M
Educational use: professionalDevelopment
- Knows technical options for the form, content, and granularity of versions.
- Recognizes that URIs are "owned" by the owners of their respective Internet domains.
- Understands that a "real-world" thing may need to be named with a URI distinct from the URI for information about that thing.
- Recognizes the desirability of a published namespace policy describing an institution's commitment to the persistence and semantic stability of important URIs.
- Understands that to be "persistent", a URI must have a stable, well-documented meaning and be plausibly intended to identify a given resource in perpetuity.
- Understands trade-offs between "opaque" URIs and URIs using version numbers, server names, dates, application-specific file extensions, query strings or other obsoletable context.
- Understands that to be "dereferencable", a URI should be usable to retrieve a representation of the resource it identifies.
- Understands the purpose of publishing RDF vocabularies in multiple formats using content negotiation.