Author: wikier
Date: Fri Oct 9 16:05:41 2015
New Revision: 1707764
URL: http://svn.apache.org/viewvc?rev=1707764&view=rev
Log:
more clarifications
Modified:
marmotta/site/trunk/content/markdown/kiwi/geosparql.md.vm
marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm
Modified: marmotta/site/trunk/content/markdown/kiwi/geosparql.md.vm
URL:
http://svn.apache.org/viewvc/marmotta/site/trunk/content/markdown/kiwi/geosparql.md.vm?rev=1707764&r1=1707763&r2=1707764&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/kiwi/geosparql.md.vm (original)
+++ marmotta/site/trunk/content/markdown/kiwi/geosparql.md.vm Fri Oct 9
16:05:41 2015
@@ -37,7 +37,7 @@ Please, take into account that GeoSPARQL
In PostgreSQL, it is necessary to install the [PostGIS](http://postgis.net/)
extension into the Marmotta database. Depending
on your operating system and distribution, this might also require
installation of additional software packages (under Debian:
-`postgresql-9.3-postgis-scripts`). To install the `postgis` extension, connect
to the database as superuser and run:
+[postgis](http://packages.debian.org/postgis)). To install the `postgis`
extension, connect to the database as superuser and run:
CREATE EXTENSION IF NOT EXISTS postgis;
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=1707764&r1=1707763&r2=1707764&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm (original)
+++ marmotta/site/trunk/content/markdown/kiwi/sparql.md.vm Fri Oct 9 16:05:41
2015
@@ -119,7 +119,7 @@ vs
}
According to the SPARQL standard, the first query only yields results when the
values for `:p2` and `:p3` are the
-same, while the second query essentially ignores the OPTIONAL. Since SQL has a
declarative semantics where the order
+same, while the second query essentially ignores the `OPTIONAL`. Since SQL has
a declarative semantics where the order
of statements does not matter, we do not support this case. We always
implement the semantics of the second
SPARQL query.
