Skip to main content

Uniform Resource Identifier (URI)

A Uniform Resource Identifier (URI) is a way to represent a unique entity in a way that is reliable and usable by others. By naming an entity not by a local name but through reference to its authority URI, multiple datasets from various sources can communicate that they are all referring to the same thing. The easiest way to explain a URI is through an example. Take the URI example for Rembrandt: <>. The most granular part of this URI is the number (500011051), also called the path. Without context, this number does not uniquely identify the Rembrandt that you are trying to describe. The full URI provides that necessary context: it is clear that you are using the Getty vocabulary Union List of Artist Names as our authorities, and it is in this context that the number, and the full URI, becomes a unique way to identify something. In addition to the path, URIs often have a fragment, which is an identifier that follows a hash symbol (#) placed at the end of the path in the URI, to point to a specific part of a document.

While this example looks like a Uniform Resource Locator (URL), a URI does not need to look like this: it just needs to be reliably unique. Furthermore, while URI formats may be the same as a URL, they do not need to link to a web page or have a network location⁠—all URLs are URIs but not all URIs are URLs because a URI can describe anything at all, but a URL only describes the location of something on the web. In practice, however, not all URLs serve well as URIs for the purposes of Linked Open Data (LOD), since some are more persistent and authoritative than others. For instance, using the URL for a person’s LinkedIn profile is not as desirable as using on ORCID identifier, or using a link to a downloadable PDF of an article from a faculty member’s departmental web page is not good practice compared to using a Digital Object Identifier (DOI) for the same article. If a URI does resolve at a webpage, this means it is dereferenceable.

A URI should not change, and URIs should be designed with three things in mind: simplicity, stability, and manageability.


Further Resources