Author: wikier
Date: Fri Nov 21 12:03:10 2014
New Revision: 1640901
URL: http://svn.apache.org/r1640901
Log:
improved some minor details of the memento module doc
Modified:
marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm
marmotta/site/trunk/content/markdown/platform/ldpath-module.md.vm
marmotta/site/trunk/content/markdown/platform/versioning-module.md.vm
Modified: marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm
URL:
http://svn.apache.org/viewvc/marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm?rev=1640901&r1=1640900&r2=1640901&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm (original)
+++ marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm Fri Nov 21 12:03:10
2014
@@ -18,7 +18,6 @@ border cases, we therefore deliberately
are documented below. If you want full standard compliance, you can still use
SPARQL
without the native support, at the expense of query performance (factor up to
1000).
-
[1]: http://www.w3.org/TR/sparql11-query/
Maven Artifact
@@ -181,4 +180,4 @@ SPARQL query.
According to the SPARQL standard, variables occurring in the left and right
argument of a MINUS are scoped
to their individual arguments. Since we translate this case into a NOT EXISTS,
our implementation does not support
this case, which can yield unexpected results for certain queries. These cases
should be solved by proper variable
-renaming. All other differences between MINUS and NOT EXISTS are implemented
according to the standard.
\ No newline at end of file
+renaming. All other differences between MINUS and NOT EXISTS are implemented
according to the standard.
Modified: marmotta/site/trunk/content/markdown/platform/ldpath-module.md.vm
URL:
http://svn.apache.org/viewvc/marmotta/site/trunk/content/markdown/platform/ldpath-module.md.vm?rev=1640901&r1=1640900&r2=1640901&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/platform/ldpath-module.md.vm (original)
+++ marmotta/site/trunk/content/markdown/platform/ldpath-module.md.vm Fri Nov
21 12:03:10 2014
@@ -2,4 +2,4 @@
# Apache Marmotta Platform: LDPath
-@TODO@
+This module provides [LDPath](../ldpath) support in the Marmotta plaform.
Modified: marmotta/site/trunk/content/markdown/platform/versioning-module.md.vm
URL:
http://svn.apache.org/viewvc/marmotta/site/trunk/content/markdown/platform/versioning-module.md.vm?rev=1640901&r1=1640900&r2=1640901&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/platform/versioning-module.md.vm
(original)
+++ marmotta/site/trunk/content/markdown/platform/versioning-module.md.vm Fri
Nov 21 12:03:10 2014
@@ -1,27 +1,32 @@
<head><title>Platform - Versioning</title></head> <!-- awaiting for
https://jira.codehaus.org/browse/DOXIA-472 -->
# Apache Marmotta Platform: Versioning
+
Marmotta offers a versioning service that keeps track of triple updates in
configurable graphs.
Versioning is transaction based, i.e. every time a transaction is committed
successfully, a new version entry is created
by the versioning services. Marmotta currently supports listing versions
(**timemap**) as well as inspecting snapshots
(**mementos**) (i.e. going back in time) for resources. To give a smooth web
access to **timemaps** and **snapshots**,
-Marmottas Versioning module implements the Memento protocol.
+Marmottas Versioning module implements the Memento protocol ([RFC
7089](https://tools.ietf.org/html/rfc7089)).
+
## Using the versioning module
+
To make use of the versioning service you have to insert the dependency to
**marmotta-versioning** module in the pom.xml
file of the Marmotta plattform like this:
- <modules>
- ...
- <module>marmotta-versioning</module>
- ...
- </modules>
+ <dependency>
+ <groupId>org.apache.marmotta</groupId>
+ <artifactId>marmotta-versioning</artifactId>
+ <version>${projectVersion}</version>
+ </dependency>
After starting the server the module appears in the administration interface.
## An introduction to the Memento Protocol
The Memento protocol aims to bring time-based access to web resources using
common web standards. The whole description of the
protocol with several examples of resource access and browsing can be found on
[the webpage of the Memento project]
(http://www.mementoweb.org). Nevertheless we give a short introduction to the
topic.
+
### Time-based access to resources
+
Memento decides between resources (URI-R), timegates (URI-G) and mementos
(URI-M<small>x</small>).
<img style="display:block;margin:0 auto;"
src="http://www.mementoweb.org/guide/quick-intro/memento.png";
alt="memento follow your nose architecture"
@@ -29,6 +34,7 @@ Memento decides between resources (URI-R
Resources are the original resources. When requesting such resources, the HTTP
response include links to the timemap (a
list of all versions of the resource) and the timegate (where you can request
the resource with Accept-Datetime header).
+
### Version Access and Timemaps
- A TimeGate supports content negotiation in the datetime dimension. When
negotiating with the TimeGate, the HTTP client
@@ -41,5 +47,7 @@ next version (rel=next memento). All lin
2 different formats (application/link-format and text/html) depending on the
HTTP Accept request header.
## Outlook
+
The underlying system is able to simulate the triplestore at all datetimes in
the past. In future versions, the Memento
protocol will be extended to snapshot access to the whole triplestore (via
SPARQL and LDPath).
+
![http://www.mementoweb.org/guide/quick-intro/memento.png"](http://www.mementoweb.org/guide/quick-intro/memento.png"){kind=link}