Slide presentation used as part of a training module aiming to answer the following questions: What is a Uniform Resource Identifier (URI); Why is URI persistence important; How does one design and manage persistent URIs for data resources?
Keywords: HTTP URIs, Persistence, Disambiguation, Dereferencability, 303 URIs, Content negotiation
Author: Goedertier, Stijn
Date created: 2013-06-06 04:00:00.000
Time required: P20M
- Ensures that when dereferenced by a Web browser, a URI returns a representation of the resource in human-readable HTML.
- Ensures that when dereferenced by an RDF application, a URI returns representation of the resource in the requested RDF serialization syntax.
- 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.