This article's tone or style may not reflect the encyclopedic tone used on Wikipedia. (November 2019) (Learn how and when to remove this template message)
This article includes a list of general references, but it remains largely unverified because it lacks sufficient corresponding inline citations. (May 2010) (Learn how and when to remove this template message)
Rather than expecting people to know about the growing number of Web archives, and to guess which archive might hold an older version of the resource they’re looking for, Memento proposes to make archived content discoverable via the original URL that the searcher already knew about. Essentially, Memento is an attempt to permit users to view any web page as it looked on a given date in the past.
A variety of web archives exist, collecting specific revisions of web pages as they existed at a particular point in time. Memento allows a user to seamlessly transition between these archives in search of the best archived page matching the datetime for the page that they desire.
Memento is defined in RFC 7089 as an implementation of the time dimension of content negotiation, as defined by Tim Berners Lee in 1996. HTTP accomplishes negotiation of content via headers. The table below shows the different headers available for HTTP that allow clients and servers to find the content that the user desires.
|Request Header||Response Header||Dimension||Examples||Reference|
|Accept||Content-Type||content-type of the representation||text/html
|Accept-Language||Content-Language||language of the representation||en
|Accept-Encoding||Content-Encoding||medium, typically compression, that the content has been encoded with||compress
|Accept-Charset||Content-Type||the character set used by the web page||iso-8859-5
|Accept-Datetime||Memento-Datetime||time of the representation||Fri, 15 Aug 2014 13:43:03
Memento provides the Accept-Datetime request header so that clients can provide a date to the server, and the server can provide the best archived version of a page for that date. This is referred to as datetime negotiation.
To understand Memento fully, one must realize that the Last-Modified header provided by HTTP does not necessarily reflect when a particular version of a web page came into existence. Also, the Last-Modified header may not exist in some cases. To provide more information, the Memento-Datetime header has been introduced to indicate when a specific representation of a web page was observed on the web.
The diagram above shows the 3 step process by which Memento finds the best archived web page for the datetime supplied by the user. The process works as follows:
- The Memento client contacts the original resource to see if it will return information about a TimeGate (URI-G) in the Link header.
- The Memento client then uses the Accept-Datetime request header to submit the datetime desired by the user to the URI-G discovered in the previous step. Most resources on the web do not return a URI-G yet, so most Memento clients use a predefined list of TimeGates to accomplish this step. The TimeGate then returns a 302 redirection status code and a Location header to tell the client where to find the archived resource (URI-M).
- The Memento client then requests the archived resource (URI-M) like it would any other web page. The response for the URI-M contains a Memento-Datetime indicating when it was observed on the web.
In this way, Memento utilizes the existing infrastructure of HTTP to accomplish the goals of finding the best archived web page based on a user's desired datetime and URI.
One can find copies of page by simply navigating, in a web browser, to a link formatted, replacing
urltoarchive with the full URL of the page desired:
JSON description of a Memento:
redirect to a Memento with a datetime that is close to a desired datetime:
- RFC 7089: HTTP Framework for Time-Based Access to Resource States -- Memento
- Berners Lee, Tim. "Web Architecture: Generic Resources". World Wide Web Consortium (W3C). 1996. http://www.w3.org/DesignIssues/Generic Archived 2015-06-02 at the Wayback Machine
- RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
- RFC 7232: Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
- Nelson, Michael L. "2010-11-05: Memento-Datetime is not Last-Modified". Web Science and Digital Libraries Research Group. November 5, 2010. http://ws-dl.blogspot.com/2010/11/2010-11-05-memento-datetime-is-not-last.html Archived 2015-05-19 at the Wayback Machine
- "Time Travel APIs". timetravel.mementoweb.org. Archived from the original on 2018-05-21. Retrieved 2018-05-15.
- Memento Project
- The When of the Web - Extensive information about the proposal and experiment is available in the November 2009 paper
- Memento: Time Travel for the Web