The article explains that stable URIs depend on deliberate design rather than accidental longevity.

When a domain owner controls a name space, URIs in theory remain under that owner’s authority, but practical factors such as corporate reorganizations, content updates, or server migrations frequently cause URIs to change.

Common causes include website redesigns that alter directory structures, moving files without updating links, switching from script‑based to static serving, and embedding mutable information such as author names, subjects, status tags, file extensions, or software identifiers in the path.

For example, the National Science Foundation moved documents from cgi‑bin scripts to static html pages, illustrating how changing implementation details can break existing references.

Broken links reduce confidence in the hosting organization and frustrate users who rely on those references.

To improve durability, webmasters should include the document creation date in the URI, omit mutable elements, avoid file extensions, and refrain from using software or access descriptors that may change.

Implementing content negotiation allows servers to serve different formats without altering the identifier, and maintaining a database that maps persistent URIs to current file locations supports long‑term stability.

Proper URI design requires planning for years or decades, allocating resources for mapping and version tracking, and resisting the urge to prioritize short‑term presentation over lasting link integrity.