GitHub user tkurz opened a pull request:
https://github.com/apache/marmotta/pull/24
Marmotta 655 memento compliance issues
This fixes all the issues that are mentioned in 655. At least from my side
marmotta memento should now produce correct Links, Dates etc.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/marmotta
MARMOTTA-655_Memento_Compliance_Issues
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/marmotta/pull/24.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #24
----
commit cd789c9b1a26d886550269b170536874c0125dfa
Author: Thomas Kurz <[email protected]>
Date: 2016-10-13T13:49:15Z
redirect of timegate ist set to 302 response code
commit d216030b01ad921b36e2aeb96aec1468590ffe51
Author: Thomas Kurz <[email protected]>
Date: 2016-10-13T15:48:21Z
TimeGate now responds with the most recent Memento if date is not given.
Tests are added.
commit badefd3e66ef85feab6837ca5f9f6c415c398e91
Author: Thomas Kurz <[email protected]>
Date: 2016-10-13T15:51:56Z
TimeGate does not provice a Memento-Datetime anaymore.
commit ea07757c176138c5a59b3cace0c1249e48711e68
Author: Thomas Kurz <[email protected]>
Date: 2016-10-13T16:09:52Z
Use different date serializations for uris and other places (e.g. links,
headers, etc.)
commit 837d5d0e4097e3ebb69ee40f593873e499a6cce2
Author: Thomas Kurz <[email protected]>
Date: 2016-10-13T16:11:46Z
set link to most recent browser extension
commit 385a92bc7f4f4a11dcdf63864c9cf04b6a6e08cc
Author: Thomas Kurz <[email protected]>
Date: 2016-10-19T14:04:26Z
some fixes and tests
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
