The address in the browser is not the institution

An organization prints a QR code on a product and links it to its website. Several years later the business sells its domain. The code still resolves, but the page tells a completely different story. The network address survived in one narrow sense. The institution that gave it meaning did not.

A web URL is a wonderfully useful reference. It contains a scheme and components that let software resolve a resource according to the relevant protocol. RFC 3986^{[1]RFC 3986} explains that syntax and the difference between identification and retrieval. It does not promise everlasting ownership of the referenced host.

A canonical URL is a publishing choice about which address should represent a page. A domain registration is an administratively maintained right to use a name, subject to renewal and transfer. A durable identity is an ongoing social or institutional relationship that may have to survive both of those mechanisms.

Confusing these leads to poor succession planning. Links can break when paths change; citations can be redirected to irrelevant products; a personal history can vanish when an account is closed. A site can continue serving HTML after the person or organization it purportedly represents has lost control.

Imagine a small journal moving from a hosting provider to an independently managed domain. The editor wants to preserve article URLs, bylines, feeds, subscriber relationships, canonical links and corrections. Redirects can help readers who still have the old URL, but the old domain must remain under suitable control for redirects to keep working.

Some independent identifiers can provide an additional layer of continuity. Yet any resolver has its own governance and failure modes. The question is not which single identifier is magical. It is who will keep it maintained when the original operator leaves.

Ownership of a domain does not imply ownership of all material once published through it. Conversely, preserving a lawful copy does not grant the ability to impersonate the original author. An archive and a domain's new administrator have different responsibilities.

Digital inheritance makes the issue concrete. When a creator dies or a cooperative dissolves, who may preserve the address, update an explanatory notice, maintain the source collection or publish new material under the old name? Those decisions require governance before the technical emergency.

Treat the domain as one address of an institution rather than its essential identity. Retain source records, attributed rights, stable internal subject references, published canonical locations, historical aliases and explicit successor authority. Preserve redirects and explanatory tombstones where lawful and feasible.

This connects to the Journal's account of the internet's inheritance problem. The point of a living web is not to make the platform immortal. It is to give people, associations and publications a chance to survive changes in operators without forfeiting their histories.