Memento Link — Index Of

Memento extends HTTP to support datetime negotiation. Key components:

| Term | Definition | |------|-------------| | Original Resource | The live web page (e.g., http://example.com/page). | | Memento | An archived snapshot of the resource at a specific datetime. | | TimeGate | A server that accepts datetime negotiation and redirects to the nearest memento. | | TimeMap | A machine-readable list (e.g., application/link-format or text/html) of all mementos for a resource, ordered by datetime. | | Memento Link | An HTTP Link header or HTML <link> element that points to a TimeGate or TimeMap. |

The Index of Memento Link is typically the TimeMap — a comprehensive index linking to every captured version. index of memento link

The review of the memento-link implementation focuses on how it extends standard HTTP Link headers. When a client requests a resource, the server can now respond with a payload of links that define a temporal graph.

Key Link Relations introduced include:

Practical Utility: From a developer's perspective, this is a robust implementation of content negotiation. Instead of relying on brittle query parameters (e.g., example.com?date=2020-01-01), the protocol treats time as a first-class dimension of the web. It allows archives like the Internet Archive and the UK Web Archive to interoperate seamlessly.

A standard memento link (URI-M) usually looks like this: Memento extends HTTP to support datetime negotiation

https://web.archive.org/web/20231027124500/https://example.com/page

Breaking down the index structure:

An index of memento links, therefore, is a database that pairs the original URL with every available timestamp across multiple archives (not just the Wayback Machine).