[MARMOTTA-655] Memento Compliance Issues

• Type: Bug
• Status: In Progress
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.3.0, 3.4.0
• Component/s: Web Services
• Assignee: Thomas Kurz
• Reporter: Harihar Shankar
• Created: 19/Sep/16 22:13
• Updated: 25/Oct/16 19:21

Description

We tested the Memento Compliance of Marmotta, and found a few issues that I have listed below. I apologize in advance for the long list, please let me know if you need more information, I am happy to help.

• The Marmotta TimeGate must respond with an HTTP 302 instead of an HTTP 301 when redirecting to a Memento.

• The Marmotta TimeGate responds with "HTTP 400 Bad Request" when no Accept-Datetime header is provided. Instead, the TimeGate should respond with the most recent Memento in this case. This section of the Memento RFC describes this scenario.

• The Marmotta TimeGate should not provide the Memento-Datetime header.

• The Date value expressed in all the headers must be in the HTTP Date format specified by RFC 1123 and in the GMT timezone, like

  Memento-Datetime: Tue, 15 Nov 1994 08:12:31 GMT

  This would apply to all the date values in the Link headers, Memento-Datetime header, and in the TimeMaps.

• When importing data in to Marmotta from a document, the rel="original" in the Link headers for TimeGate and Memento point to the Subject URL and not the Marmotta resource instance's {base URL + Subject URL}

  .
  For eg, When we uploaded a document with subject http://dbpedia.org/resource/English, the TimeGate responds with:

  curl -I "Accept-Datetime: Mon, 19 Sep 2016 23:47:12 GMT" http://localhost:8080/marmotta/memento/timegate/http://dbpedia.org/resource/English
  Link: ..., <http://dbpedia.org/resource/English>;rel="original", ....
  

  Instead, this should be something like:

  Link: ...., <{marmotta_base_url}+http://dbpedia.org/resource/English>; rel="original",...
  

• The Marmotta versioning page at http://localhost:8080/marmotta/versioning/admin/about.html points to MementoFox, which is not maintained any longer and is not recommended. The Memento For Chrome extension is actively maintained and is highly recommended.

In case you are not aware, there is a Memento Validator that tests an instance for RFC compliance.