You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by gi...@apache.org on 2020/04/30 20:44:58 UTC
[jena-site] branch asf-site updated: Updated site from master
(01443e5247b3c8e0fd007f3328949c1c7d0f4b3a)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new caf6fad Updated site from master (01443e5247b3c8e0fd007f3328949c1c7d0f4b3a)
caf6fad is described below
commit caf6fadafddd7840dbd05facb63e7b2d3a2b1915
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Apr 30 20:44:54 2020 +0000
Updated site from master (01443e5247b3c8e0fd007f3328949c1c7d0f4b3a)
---
.../{ => archive}/serving_data/fuseki1.html | 26 ++++++----
content/documentation/csv/get_started.html | 8 +--
.../documentation/fuseki2/data-access-control.html | 4 +-
content/documentation/fuseki2/fuseki-main.html | 7 ++-
content/documentation/fuseki2/index.html | 3 --
content/documentation/geosparql/index.html | 5 +-
content/documentation/index.xml | 20 ++++----
content/documentation/io/rdf-input.html | 2 +-
content/documentation/jdbc/drivers.html | 2 +-
content/documentation/query/construct-quad.html | 6 +--
.../query/generate-json-from-sparql.html | 2 +-
content/documentation/query/http-auth.html | 26 +++++-----
content/documentation/query/index.html | 2 +-
.../query/parameterized-sparql-strings.html | 4 +-
content/documentation/query/spatial-query.html | 2 +-
content/documentation/query/text-query.html | 2 +-
content/documentation/query/writing_propfuncs.html | 26 +++++-----
content/documentation/rdf/index.html | 10 ++--
content/documentation/rdfconnection/index.html | 7 ++-
content/documentation/serving_data/index.html | 11 ++--
content/documentation/shacl/index.html | 2 +-
content/documentation/tdb/index.html | 10 ++--
content/documentation/tdb2/index.html | 9 ++--
content/documentation/tools/schemagen-maven.html | 6 +--
content/index.xml | 20 ++++----
content/sitemap.xml | 58 +++++++++++-----------
content/tutorials/sparql.html | 2 +-
content/tutorials/sparql_pt.html | 2 +-
28 files changed, 140 insertions(+), 144 deletions(-)
diff --git a/content/documentation/serving_data/fuseki1.html b/content/documentation/archive/serving_data/fuseki1.html
similarity index 96%
rename from content/documentation/serving_data/fuseki1.html
rename to content/documentation/archive/serving_data/fuseki1.html
index 6a93ca3..d7504ae 100644
--- a/content/documentation/serving_data/fuseki1.html
+++ b/content/documentation/archive/serving_data/fuseki1.html
@@ -118,7 +118,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/serving_data/fuseki1.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
+ <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/archive/serving_data/fuseki1.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -153,7 +153,15 @@
- <li><a href='/documentation/serving_data'>SERVING DATA</a></li>
+ <li><a href='/documentation/archive'>ARCHIVE</a></li>
+
+
+
+
+
+
+
+ <li><a href='/documentation/archive/serving_data'>SERVING DATA</a></li>
@@ -178,11 +186,9 @@
<h2 id="see-the-fuseki2-documentationdocumentationfuseki2">See the <a href="/documentation/fuseki2/">Fuseki2 documentation</a>.</h2>
<hr>
<blockquote>
-<p>This page covers Fuseki v1.
-Fuseki1 is deprecated and has been retired.
-The last release of Jena with this module is Jena 3.9.0.
-See <a href="https://github.com/apache/jena/tree/master/fuseki1">jena-fuseki1/README.md</a>.
-This is the original documentation.</p>
+<p>This page covers Fuseki v1.<br/>
+Fuseki1 is deprecated and has been retired.<br/>
+The last release of Jena with this module is Jena 3.9.0.<br/></p>
</blockquote>
<hr>
<p>Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query,
@@ -215,7 +221,7 @@ repositories</a>.</p>
<h2 id="getting-started-with-fuseki">Getting Started With Fuseki</h2>
<p>This section provides a brief guide to getting up and running with
a simple server installation. It uses the
-<a href="../fuseki2/soh.html">SOH (SPARQL over HTTP)</a> scripts included in the
+<a href="/documentation/fuseki2/soh.html">SOH (SPARQL over HTTP)</a> scripts included in the
download.</p>
<ol>
<li>
@@ -366,7 +372,7 @@ accessed via the appropriate protocol at the following URLs:</p>
<li>SPARQL update: <code>http://localhost:3030/ds/update</code></li>
<li>SPARQL HTTP update: <code>http://localhost:3030/ds/data</code></li>
</ul>
-<p>The <a href="soh.html">SPARQL Over HTTP</a> scripts take care of naming
+<p>The <a href="/documentation/fuseki2/soh.html">SPARQL Over HTTP</a> scripts take care of naming
and protocol details. For example, to load in a file <code>data.rdf</code>:</p>
<pre><code> s-put http://localhost:3030/ds/data default data.rdf
</code></pre>
@@ -533,7 +539,7 @@ or making the default graph the union of all named graphs.</p>
<p><strong>SOH</strong> (SPARQL Over HTTP) is a set of command-line scripts for
working with SPARQL 1.1. SOH is server-independent and will work
with any compliant SPARQL 1.1 system offering HTTP access.</p>
-<p>See the <a href="soh.html">SPARQL Over HTTP</a> page.</p>
+<p>See the <a href="/documentation/fuseki2/soh.html">SPARQL Over HTTP</a> page.</p>
<h3 id="examples">Examples</h3>
<pre><code># PUT a file
s-put http://localhost:3030/ds/data default D.nt
diff --git a/content/documentation/csv/get_started.html b/content/documentation/csv/get_started.html
index c687a32..f9d164f 100644
--- a/content/documentation/csv/get_started.html
+++ b/content/documentation/csv/get_started.html
@@ -176,7 +176,7 @@
<h1 class="title">CSV PropertyTable - Get Started</h1>
<h2 id="using-csv-propertytable-with-apache-maven">Using CSV PropertyTable with Apache Maven</h2>
-<p>See <a href="http://jena.apache.org/download/maven.html">“Using Jena with Apache Maven”</a> for full details.</p>
+<p>See <a href="/download/maven.html">“Using Jena with Apache Maven”</a> for full details.</p>
<pre><code><dependency>
<groupId>org.apache.jena</groupId>
<artifactId>jena-csv</artifactId>
@@ -184,7 +184,7 @@
</dependency>
</code></pre>
<h2 id="using-csv-propertytable-from-java-through-the-api">Using CSV PropertyTable from Java through the API</h2>
-<p>In order to switch on CSV PropertyTable, it’s required to register <code>LangCSV</code> into <a href="http://jena.apache.org/documentation/io/">Jena RIOT</a>, through a simple method call:</p>
+<p>In order to switch on CSV PropertyTable, it’s required to register <code>LangCSV</code> into <a href="/documentation/io/">Jena RIOT</a>, through a simple method call:</p>
<pre><code>import org.apache.jena.propertytable.lang.CSV2RDF;
...
CSV2RDF.init() ;
@@ -218,7 +218,7 @@ model.read("test.csv") ;
// Usage 2: Reading using RDFDataMgr
Model model_2 = RDFDataMgr.loadModel("test.csv") ;
</code></pre>
-<p>For more information, see <a href="http://jena.apache.org/documentation/io/rdf-input.html">Reading RDF in Apache Jena</a>.</p>
+<p>For more information, see <a href="/documentation/io/rdf-input.html">Reading RDF in Apache Jena</a>.</p>
<p>Note that, the requirements for the CSV files are listed in the documentation of <a href="design.html">Design</a>. CSV PropertyTable only supports <strong>single-Value</strong>, <strong>regular-Shaped</strong>, <strong>table-headed</strong> and <strong>UTF-8-encoded</strong> CSV files (<strong>NOT</strong> Microsoft Excel files).</p>
<h2 id="command-line-tool">Command Line Tool</h2>
<p><a href="https://github.com/apache/jena/tree/master/jena-csv/src/main/java/riotcmd/csv2rdf.java">csv2rdf</a> is a tool for direct transforming from CSV to the formatted RDF syntax of N-Triples.
@@ -231,7 +231,7 @@ The script calls the <code>csv2rdf</code> java program in the <code>riotcmd</cod
<p>The script reuses <a href="../io/index.html">Common framework for running RIOT parsers</a>,
so that it also accepts the same arguments
(type <code>"riot --help"</code> to get command line reminders) from
-<a href="https://jena.apache.org/documentation/io/#command-line-tools">RIOT Command line tools</a>:</p>
+<a href="/documentation/io/#command-line-tools">RIOT Command line tools</a>:</p>
<ul>
<li><code>--validate</code>: Checking mode: same as <code>--strict --sink --check=true</code></li>
<li><code>--check=true/false</code>: Run with checking of literals and IRIs either on or off.</li>
diff --git a/content/documentation/fuseki2/data-access-control.html b/content/documentation/fuseki2/data-access-control.html
index 903f7a6..90dcf6d 100644
--- a/content/documentation/fuseki2/data-access-control.html
+++ b/content/documentation/fuseki2/data-access-control.html
@@ -178,14 +178,14 @@
<p>Fuseki can provide access control at the level on the server, on datasets,
on endpoints and also on specific graphs within a dataset. It also
provides native https to protect data in-flight.</p>
-<p><a href="http://jena.apache.org/documentation/fuseki2/fuseki-main.html">Fuseki Main</a>
+<p><a href="/documentation/fuseki2/fuseki-main.html">Fuseki Main</a>
provides some common patterns of authentication.</p>
<p><a href="#graph-acl">Graph level Data Access Control</a> provides control over the visibility of
graphs within a dataset, including the union graph of a dataset and
the default graph. Currently, Graph level access control only applies to
read-only datasets.</p>
<p>Fuseki Full (Fuseki with the UI) can be used when
-<a href="http://jena.apache.org/documentation/fuseki2/fuseki-run.html#fuseki-web-application">run in a web application server such as Tomcat</a>
+<a href="/documentation/fuseki2/fuseki-run.html#fuseki-web-application">run in a web application server such as Tomcat</a>
to provide authentication of the user. See “<a href="fuseki-security">Fuseki Security</a>” for configuring security over the whole of the Fuseki UI.</p>
<h2 id="contents">Contents</h2>
<ul>
diff --git a/content/documentation/fuseki2/fuseki-main.html b/content/documentation/fuseki2/fuseki-main.html
index b5b1333..3396b74 100644
--- a/content/documentation/fuseki2/fuseki-main.html
+++ b/content/documentation/fuseki2/fuseki-main.html
@@ -200,8 +200,7 @@ persistent work area on-disk.</p>
<pre><code>java -jar jena-fuseki-server-$VER.jar --help
</code></pre>
<p>The arguments are the same as the
-<a href="http://jena.apache.org/documentation/fuseki2/fuseki-run.html#fuseki-standalone-server">full UI server command line
-program</a>.
+<a href="/documentation/fuseki2/fuseki-run.html#fuseki-standalone-server">full UI server command line program</a>.
There are no special environment variables.</p>
<p>The entry point is <code>org.apache.jena.fuseki.main.cmds.FusekiMainCmd</code> so
the server can also be run as:</p>
@@ -251,7 +250,7 @@ encouraged to use a dependency manager because the number of Jetty and other dep
is quite large and difficult to set manually.</p>
<p>This dependency does not include a logging setting. Fuseki uses <a href="http://slf4j.org/">slf4j</a>.
See section “<a href="#logging">Logging</a>” for details.</p>
-<p>If the application wishes to use a dataset with a <a href="http://jena.apache.org/documentation/query/text-query.html">text-index</a>
+<p>If the application wishes to use a dataset with a <a href="/documentation/query/text-query.html">text-index</a>
then the application will also need to include jena-text in its dependencies.</p>
<h2 id="logging">Logging</h2>
<p>The application must set the logging provided for <a href="http://slf4j.org/">slf4j</a>.
@@ -282,7 +281,7 @@ Apache jena provides helpers for the JDK-provided java logging and for Apache Lo
<version>1.x.y</version>
</dependency>
</code></pre>
-<p>See <a href="http://jena.apache.org/documentation/fuseki2/fuseki-logging.html">Fuseki Logging</a>.</p>
+<p>See <a href="/documentation/fuseki2/fuseki-logging.html">Fuseki Logging</a>.</p>
<p>To silence logging from Java, try:</p>
<pre><code>LogCtl.setLevel(Fuseki.serverLogName, "WARN");
LogCtl.setLevel(Fuseki.actionLogName, "WARN");
diff --git a/content/documentation/fuseki2/index.html b/content/documentation/fuseki2/index.html
index 0bd9886..60429df 100644
--- a/content/documentation/fuseki2/index.html
+++ b/content/documentation/fuseki2/index.html
@@ -288,9 +288,6 @@ pull-requests.</p>
<a href="https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-fuseki/">SNAPSHOT</a></p>
<p>Source code mirrored to github:
<a href="https://github.com/apache/jena/tree/master/jena-fuseki2">https://github.com/apache/jena/tree/master/jena-fuseki2</a></p>
-<h2 id="fuseki-1">Fuseki 1</h2>
-<p>Fuseki 1 is still available for legacy use.
-<a href="/documentation/serving_data/">Documentation for Fuseki1</a>.</p>
</div>
diff --git a/content/documentation/geosparql/index.html b/content/documentation/geosparql/index.html
index 95c1a70..f1c5763 100644
--- a/content/documentation/geosparql/index.html
+++ b/content/documentation/geosparql/index.html
@@ -272,8 +272,7 @@ try (QueryExecution qe = QueryExecutionFactory.create(query, model)) {
ResultSetFormatter.outputAsTSV(rs);
}
</code></pre>
-<p>More information on SPARQL querying using Jena can be found on their website (<a href="https://jena.apache.org/tutorials/sparql.html)">https://jena.apache.org/tutorials/sparql.html)</a>.
-If your dataset needs to be separate from your application and accessed over HTTP then you probably need
+<p>If your dataset needs to be separate from your application and accessed over HTTP then you probably need
the <a href="geosparql-fuseki">GeoSPARQL Fuseki project</a>.
The GeoSPARQL functionality needs to be setup in the application or Fuseki server where the dataset is located.</p>
<p>It is <strong>recommended</strong> that <code>hasDefaultGeometry</code> properties are included in the dataset to access all functionality.
@@ -340,7 +339,7 @@ implementation "org.apache.sis.non-free:sis-embedded-data:$sisVersion"
<p>The following are implementation points that may be useful during usage.</p>
<h3 id="geosparql-schema">GeoSPARQL Schema</h3>
<p>An RDF/XML schema has been published for the GeoSPARQL v1.0 standard (v1.0.1 - <a href="http://schemas.opengis.net/geosparql/1.0/geosparql_vocab_all.rdf)">http://schemas.opengis.net/geosparql/1.0/geosparql_vocab_all.rdf)</a>.
-This can be applied to Jena Models (<a href="https://jena.apache.org/documentation/inference/">https://jena.apache.org/documentation/inference/</a>) to provide RDFS and OWL inferencing on a GeoSPARQL conforming dataset.
+This can be applied to Jena Models (see <a href="/documentation/inference/">the inference documentation</a>) to provide RDFS and OWL inferencing on a GeoSPARQL conforming dataset.
However, the published schema does not conform with the standard.</p>
<p>The property <code>hasDefaultGeometry</code> is missing from the schema and instead the <code>defaultGeometry</code> property is stated.</p>
<p>This prevents RDFS inferencing being performed correctly and has been reported to the OGC Standards Tracker.
diff --git a/content/documentation/index.xml b/content/documentation/index.xml
index 05e6ab6..dd1642b 100644
--- a/content/documentation/index.xml
+++ b/content/documentation/index.xml
@@ -738,24 +738,24 @@ SPARQL Graph Store Protocol inc extensions - dataset HTTP verbs.</description>
<item>
<title>Fuseki: serving RDF data over HTTP</title>
- <link>https://jena.apache.org/documentation/serving_data/</link>
+ <link>https://jena.apache.org/documentation/archive/serving_data/fuseki1.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/serving_data/</guid>
- <description>See the Fuseki2 documentation. This page covers Fuseki1. Fuseki1 is deprecated and has been retired. Fuseki2 is current. The last release of Jena with this module is Jena 3.9.0. See jena-fuseki1/README.md. The original documentation.
- </description>
+ <guid>https://jena.apache.org/documentation/archive/serving_data/fuseki1.html</guid>
+ <description>See the Fuseki2 documentation. This page covers Fuseki v1. Fuseki1 is deprecated and has been retired. The last release of Jena with this module is Jena 3.9.0.
+ Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.
+The relevant SPARQL standards are:
+ SPARQL 1.1 Query SPARQL 1.1 Update SPARQL 1.1 Protocol SPARQL 1.1 Graph Store HTTP Protocol Contents Download Getting Started Security Logging Server URI scheme Running a Fuseki Server Fuseki Configuration File SPARQL Over HTTP Use from Java Development System Download Fuseki1 Binaries for Fuseki1 are available from the maven repositories.</description>
</item>
<item>
<title>Fuseki: serving RDF data over HTTP</title>
- <link>https://jena.apache.org/documentation/serving_data/fuseki1.html</link>
+ <link>https://jena.apache.org/documentation/serving_data/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/serving_data/fuseki1.html</guid>
- <description>See the Fuseki2 documentation. This page covers Fuseki v1. Fuseki1 is deprecated and has been retired. The last release of Jena with this module is Jena 3.9.0. See jena-fuseki1/README.md. This is the original documentation.
- Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.
-The relevant SPARQL standards are:
- SPARQL 1.1 Query SPARQL 1.</description>
+ <guid>https://jena.apache.org/documentation/serving_data/</guid>
+ <description>See the Fuseki2 documentation. This page covers Fuseki1. Fuseki1 is deprecated and has been retired. Fuseki2 is current. The last release of Jena with this module is Jena 3.9.0. The original documentation.
+ </description>
</item>
<item>
diff --git a/content/documentation/io/rdf-input.html b/content/documentation/io/rdf-input.html
index 513e19e..295f97e 100644
--- a/content/documentation/io/rdf-input.html
+++ b/content/documentation/io/rdf-input.html
@@ -347,7 +347,7 @@ RDFDataMgr.read(model, "data2.ttl") ;
<h3 id="example-3--using-rdfparser">Example 3 : Using RDFParser</h3>
<p>Detail control over the setup of the parsing process is provided by
<code>RDFParser</code> which provides a builder pattern. It has many options - see
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/RDFParser.html">the javadoc for all details</a>.</p>
+<a href="/documentation/javadoc/arq/org/apache/jena/riot/RDFParser.html">the javadoc for all details</a>.</p>
<p>For example, to read Trig data, and set the error handler specially,</p>
<pre><code> // The parsers will do the necessary character set conversion.
try (InputStream in = new FileInputStream("data.some.unusual.extension")) {
diff --git a/content/documentation/jdbc/drivers.html b/content/documentation/jdbc/drivers.html
index 87effd8..239d5ab 100644
--- a/content/documentation/jdbc/drivers.html
+++ b/content/documentation/jdbc/drivers.html
@@ -296,7 +296,7 @@ via the SPARQL protocol:</p>
<p>All of these may be specified multiple times to specify multiple graph URIs for each.</p>
<p>Then you have the <code>select-results-type</code> and <code>model-results-type</code> which are used to set the MIME
type you’d prefer to have the driver retrieve SPARQL results from the remote endpoints in. If used
-you must set them to formats that ARQ supports, the ARQ <a href="http://jena.staging.apache.org/documentation/javadoc/arq/org/apache/jena/riot/WebContent.html">WebContent</a>
+you must set them to formats that ARQ supports, the ARQ <a href="/documentation/javadoc/arq/org/apache/jena/riot/WebContent.html">WebContent</a>
class has constants for the various supported formats.</p>
<h4 id="authentication">Authentication</h4>
<p>There is also comprehensive support for authentication using this driver, the standard JDBC <code>user</code>
diff --git a/content/documentation/query/construct-quad.html b/content/documentation/query/construct-quad.html
index 14d095b..7df743c 100644
--- a/content/documentation/query/construct-quad.html
+++ b/content/documentation/query/construct-quad.html
@@ -262,7 +262,7 @@ and no complex graph patterns are allowed in the short form). The keyword
<p><code>DatasetClause</code>, <code>WhereClause</code>, <code>SolutionModifier</code>, <code>TriplesTemplate</code>, <code>VarOrIri</code>,
<code>TriplesSameSubject</code> are as for the <a href="http://www.w3.org/TR/sparql11-query/#grammar">SPARQL 1.1 Grammar</a></p>
<h2 id="programming-api">Programming API</h2>
-<p>ARQ provides 2 additional methods in <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/QueryExecution.html">QueryExecution</a> for Construct Quad.</p>
+<p>ARQ provides 2 additional methods in <a href="/documentation/javadoc/arq/org/apache/jena/query/QueryExecution.html">QueryExecution</a> for Construct Quad.</p>
<pre><code>Iterator<Quad> QueryExecution.execConstructQuads() // allow duplication
Dataset QueryExecution.execConstructDataset() // no duplication
</code></pre>
@@ -291,10 +291,10 @@ Iterator<Triple> triples = qexec.execConstructTriples();
</code></pre>
<p>More examples can be found at <code>ExampleConstructQuads.java</code> under <code>jena-arq/src-examples</code></p>
<h2 id="fuseki-support">Fuseki Support</h2>
-<p>Jena <a href="http://jena.apache.org/documentation/fuseki2/index.html">Fuseki</a> is also empowered with Construct Quad query as a built-in
+<p>Jena <a href="/documentation/fuseki2/index.html">Fuseki</a> is also empowered with Construct Quad query as a built-in
function. No more additional configuration is required to switch it on.
Because
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html">QueryEngineHTTP</a>
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html">QueryEngineHTTP</a>
is just an implementation of QueryExecution, there’s no much difference
for the client users to manipulate the programming API described in the
previous sections, e.g.</p>
diff --git a/content/documentation/query/generate-json-from-sparql.html b/content/documentation/query/generate-json-from-sparql.html
index 41f4792..4023bd3 100644
--- a/content/documentation/query/generate-json-from-sparql.html
+++ b/content/documentation/query/generate-json-from-sparql.html
@@ -282,7 +282,7 @@ key/value pair pattern, which could produce the following output for the query a
<p><code>DatasetClause</code>, <code>WhereClause</code>, <code>SolutionModifier</code>, <code>String</code>, <code>Var</code>, ‘RDFLiteral’,
<code>NumericLiteral</code>, and ‘BooleanLiteral’ are as for the <a href="http://www.w3.org/TR/sparql11-query/#grammar">SPARQL 1.1 Grammar</a></p>
<h2 id="programming-api">Programming API</h2>
-<p>ARQ provides 2 additional methods in <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/QueryExecution.html">QueryExecution</a> for JSON.</p>
+<p>ARQ provides 2 additional methods in <a href="/documentation/javadoc/arq/org/apache/jena/query/QueryExecution.html">QueryExecution</a> for JSON.</p>
<pre><code>Iterator<JsonObject> QueryExecution.execJsonItems()
JsonArray QueryExecution.execJson()
</code></pre>
diff --git a/content/documentation/query/http-auth.html b/content/documentation/query/http-auth.html
index 048447b..4d38928 100644
--- a/content/documentation/query/http-auth.html
+++ b/content/documentation/query/http-auth.html
@@ -178,7 +178,7 @@
<p>After <a href="#http-authentication-from-jena-311">Jena 3.1.0</a>, Jena exposes the underlying HTTP Commons functionality to support a range of authentication mechanisms as well as <a href="https://hc.apache.org/httpcomponents-client-ga/examples.html">other HTTP configuration</a>. From <a href="#http-authentication-from-jena-300-through-310">Jena 3.0.0 through Jena 3.1.0</a> there is a Jena-specific framework that provides a uniform mechanism for HTTP authentication. This documentati [...]
<h2 id="http-authentication-from-jena-311">HTTP Authentication from Jena 3.1.1</h2>
<p>APIs that support authentication typically provide methods for providing an <a href="https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/HttpClient.html">HttpClient</a> for use with the given instance of that API class. Since it may not always be possible/practical to configure authenticators on a per-request basis the API includes a means to specify a default client that is used when no other client is explicitly specified. This may be configured [...]
-<code>setDefaultHttpClient(HttpClient httpClient)</code> method of the <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/web/HttpOp.html">HttpOp</a> class. This allows for static-scoped configuration of HTTP behavior.</p>
+<code>setDefaultHttpClient(HttpClient httpClient)</code> method of the <a href="/documentation/javadoc/arq/org/apache/jena/riot/web/HttpOp.html">HttpOp</a> class. This allows for static-scoped configuration of HTTP behavior.</p>
<h3 id="examples-of-authentication">Examples of authentication</h3>
<p>This section includes a series of examples showing how to use HTTP Commons classes to perform authenticated work. Most of them take advantage of <code>HttpOp.setDefaultHttpClient</code> as described above.</p>
<h4 id="simple-authentication-using-username-and-password">Simple authentication using username and password</h4>
@@ -234,16 +234,16 @@ qEngine.setHttpContext(httpContext);
ResultSet results = qEngine.execSelect();
</code></pre>
<h3 id="using-authentication-functionality-in-direct-query-execution">Using authentication functionality in direct query execution</h3>
-<p>Jena offers support for <a href="sparql-remote.html#from-your-application">directly creating</a> SPARQL queries against remote services. To use <a href="https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/QueryExecutionFactory.html">QueryExecutionFactory</a> in this case, select the methods (<code>sparqlService</code>, <code>createServiceRequest</code>) that offer an <code>HttpClient</code> parameter and use an authenticating client in that slot. In the case of <a [...]
+<p>Jena offers support for <a href="sparql-remote.html#from-your-application">directly creating</a> SPARQL queries against remote services. To use <a href="/documentation/javadoc/arq/org/apache/jena/query/QueryExecutionFactory.html">QueryExecutionFactory</a> in this case, select the methods (<code>sparqlService</code>, <code>createServiceRequest</code>) that offer an <code>HttpClient</code> parameter and use an authenticating client in that slot. In the case of <a href="/documentation/ja [...]
<h2 id="http-authentication-from-jena-300-through-310">HTTP Authentication from Jena 3.0.0 through 3.1.0</h2>
<p>APIs that support authentication typically provide two methods for providing authenticators, a <code>setAuthentication(String username, char[] password)</code> method
which merely configures a <code>SimpleAuthenticator</code>. There will also be a <code>setAuthenticator(HttpAuthenticator authenticator)</code> method
that allows you to configure an arbitrary authenticator.</p>
<p>Authenticators applied this way will only be used for requests by that specific API. APIs that currently support this are as follows:</p>
<ul>
-<li><a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html">QueryEngineHTTP</a> - This is the <code>QueryExecution</code> implementation returned by <code>QueryExecutionFactory.sparqlService()</code> calls</li>
-<li><a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/modify/UpdateProcessRemoteBase.html">UpdateProcessRemoteBase</a> - This is the base class of <code>UpdateProcessor</code> implementations returned by <code>UpdateExecutionFactory.createRemote()</code> and <code>UpdateExecutionFactory.createRemoteForm()</code> calls</li>
-<li><a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/web/DatasetGraphAccessorHTTP.html">DatasetGraphAccessorHTTP</a> - This is the <code>DatasetGraphAccessor</code> implementation underlying remote dataset accessors.</li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/sparql/engine/http/QueryEngineHTTP.html">QueryEngineHTTP</a> - This is the <code>QueryExecution</code> implementation returned by <code>QueryExecutionFactory.sparqlService()</code> calls</li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/sparql/modify/UpdateProcessRemoteBase.html">UpdateProcessRemoteBase</a> - This is the base class of <code>UpdateProcessor</code> implementations returned by <code>UpdateExecutionFactory.createRemote()</code> and <code>UpdateExecutionFactory.createRemoteForm()</code> calls</li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/web/DatasetGraphAccessorHTTP.html">DatasetGraphAccessorHTTP</a> - This is the <code>DatasetGraphAccessor</code> implementation underlying remote dataset accessors.</li>
</ul>
<p>From 2.11.0 onwards the relevant factory methods include overloads that allow providing a <code>HttpAuthenticator</code> at creation time which
avoids the needs to cast and manually set the authenticator afterwards e.g.</p>
@@ -255,16 +255,16 @@ try(QueryExecution qe = QueryExecutionFactory.sparqlService("http://example
}
</code></pre>
<h3 id="authenticators">Authenticators</h3>
-<p>Authentication mechanisms are provided by <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/HttpAuthenticator.html">HttpAuthenticator</a> implementations of which a number are provided built into ARQ.</p>
+<p>Authentication mechanisms are provided by <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/HttpAuthenticator.html">HttpAuthenticator</a> implementations of which a number are provided built into ARQ.</p>
<p>This API provides the authenticator with access to the <code>HttpClient</code>, <code>HttpContext</code> and target <code>URI</code> of the request that is about to be carried
out. This allows for authenticators to add credentials to requests on a per-request basis and/or to use different mechanisms and credentials for different services.</p>
<h4 id="simpleauthenticator">SimpleAuthenticator</h4>
-<p>The <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/SimpleAuthenticator.html">simple authenticator</a> is as the name suggests the simplest implementation. It takes a single set of credentials which is applied to
+<p>The <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/SimpleAuthenticator.html">simple authenticator</a> is as the name suggests the simplest implementation. It takes a single set of credentials which is applied to
any service.</p>
<p>Authentication however is not preemptive so unless the remote service sends a HTTP challenge (401 Unauthorized or 407 Proxy Authorization
Required) then credentials will not actually be submitted.</p>
<h4 id="scopedauthenticator">ScopedAuthenticator</h4>
-<p>The <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/ScopedAuthenticator.html">scoped authenticator</a> is an authenticator which maps credentials to different service URIs. This allows you to specify different
+<p>The <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/ScopedAuthenticator.html">scoped authenticator</a> is an authenticator which maps credentials to different service URIs. This allows you to specify different
credentials for different services as appropriate. Similarly to the simple authenticator this is not preemptive authentication so credentials are
not sent unless the service requests them.</p>
<p>Scoping of credentials is not based on exact mapping of the request URI to credentials but rather on a longest match approach. For example
@@ -272,11 +272,11 @@ if you define credentialsfor <code>http://example.org</code> then these are used
e.g. <code>http://example.org/some/path</code>. However if you had also defined credentials for <code>http://example.org/some/path</code> then these would be
used in favor of those for <code>http://example.org</code></p>
<h4 id="serviceauthenticator">ServiceAuthenticator</h4>
-<p>The <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/ServiceAuthenticator.html">service authenticator</a> is an authenticator which uses information encoded in the ARQ context and basically provides access to the
+<p>The <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/ServiceAuthenticator.html">service authenticator</a> is an authenticator which uses information encoded in the ARQ context and basically provides access to the
existing credential provision mechanisms provided for the <code>SERVICE</code> clause, see <a href="service.html">Basic Federated Query</a> for more information on
configuration for this.</p>
<h4 id="formsauthenticator">FormsAuthenticator</h4>
-<p>The <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/FormsAuthenticator.html">forms authenticator</a> is an authenticator usable with services that require form based logins and use session cookies to verify login state.
+<p>The <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/FormsAuthenticator.html">forms authenticator</a> is an authenticator usable with services that require form based logins and use session cookies to verify login state.
This is intended for use with services that don’t support HTTP’s built-in authentication mechanisms for whatever reason. One example of this
are servers secured using Apache HTTP Server <a href="https://httpd.apache.org/docs/2.4/mod/mod_auth_form.html">mod_auth_form</a>.</p>
<p>This is one of the more complex authenticators to configure because it requires you to know certain details of the form login mechanism of
@@ -300,7 +300,7 @@ FormsAuthenticator authenticator = new FormsAuthenticator(targetService, formLog
that maps each service to an associated form login and passing that to the <code>FormsAuthenticator</code> constructor.</p>
<p>Currently forms based login that require more than just a username and password are not supported.</p>
<h4 id="preemptivebasicauthenticator">PreemptiveBasicAuthenticator</h4>
-<p>This <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/PreemptiveBasicAuthenticator.html">authenticator</a> is a decorator over another authenticator that enables preemptive basic authentication, this <strong>only</strong> works for servers
+<p>This <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/PreemptiveBasicAuthenticator.html">authenticator</a> is a decorator over another authenticator that enables preemptive basic authentication, this <strong>only</strong> works for servers
that support basic authentication and so will cause authentication failures when any other authentication scheme is required. You should <strong>only</strong>
use this when you know the remote server uses basic authentication.</p>
<p>Preemptive authentication is not enabled by default for two reasons:</p>
@@ -313,12 +313,12 @@ use this when you know the remote server uses basic authentication.</p>
many servers will use more secure schemes like Digest authentication which <strong>cannot</strong> be done preemptively as they require more complex
challenge response sequences.</p>
<h4 id="delegatingauthenticator">DelegatingAuthenticator</h4>
-<p>The <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/DelegatingAuthenticator.html">delegating authenticator</a> allows for mapping different authenticators to different services, this is useful when you need to mix and
+<p>The <a href="/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/DelegatingAuthenticator.html">delegating authenticator</a> allows for mapping different authenticators to different services, this is useful when you need to mix and
match the types of authentication needed.</p>
<h3 id="the-default-authenticator">The Default Authenticator</h3>
<p>Since it may not always be possible/practical to configure authenticators on a per-request basis the API includes a means to specify a default
authenticator that is used when no authenticator is explicitly specified. This may be configured via the
-<code>setDefaultAuthenticator(HttpAuthenticator authenticator)</code> method of the <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/web/HttpOp.html">HttpOp</a> class.</p>
+<code>setDefaultAuthenticator(HttpAuthenticator authenticator)</code> method of the <a href="/documentation/javadoc/arq/org/apache/jena/riot/web/HttpOp.html">HttpOp</a> class.</p>
<p>By default there is already a default authenticator configured which is the <code>ServiceAuthenticator</code> since this preserves behavioural
backwards compatibility with prior versions of ARQ.</p>
<p>You can configure the default authenticator to whatever you need so even if you don’t directly control the code that is making HTTP requests
diff --git a/content/documentation/query/index.html b/content/documentation/query/index.html
index 72dc2cd..fd17b35 100644
--- a/content/documentation/query/index.html
+++ b/content/documentation/query/index.html
@@ -170,7 +170,7 @@
</div>
<h1 class="title">ARQ - A SPARQL Processor for Jena</h1>
- <p>ARQ is a query engine for <a href="http://jena.apache.org">Jena</a> that
+ <p>ARQ is a query engine for <a href="https://jena.apache.org/">Jena</a> that
supports the
<a href="http://www.w3.org/TR/sparql11-query/">SPARQL RDF Query language</a>.
SPARQL is the query language developed by the W3C
diff --git a/content/documentation/query/parameterized-sparql-strings.html b/content/documentation/query/parameterized-sparql-strings.html
index c86721a..ad31bd0 100644
--- a/content/documentation/query/parameterized-sparql-strings.html
+++ b/content/documentation/query/parameterized-sparql-strings.html
@@ -199,7 +199,7 @@ the query with constants and to add prefix and base declarations. A
the <code>asQuery()</code> and <code>asUpdate()</code> methods assuming the command an
instance represents is actually valid as a query/update.</p>
<h2 id="building-parameterised-commands">Building parameterised commands</h2>
-<p>A <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/ParameterizedSparqlString.html">ParameterizedSparqlString</a> is created as follows:</p>
+<p>A <a href="/documentation/javadoc/arq/org/apache/jena/query/ParameterizedSparqlString.html">ParameterizedSparqlString</a> is created as follows:</p>
<pre><code>ParameterizedSparqlString pss = new ParameterizedSparqlString();
</code></pre>
<p>There are also constructor overloads that take in an initial command text, parameter values, namespace prefixes etc.
@@ -240,7 +240,7 @@ injection is detected an <code>ARQException</code> will be thrown.</p>
<li>Using JDBC style positional parameters</li>
<li>Appending values directly to the command text being built</li>
</ul>
-<p>See the <a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/query/ParameterizedSparqlString.html">ParameterizedSparqlString</a> javadocs for a comprehensive reference of available methods for setting values,
+<p>See the <a href="/documentation/javadoc/arq/org/apache/jena/query/ParameterizedSparqlString.html">ParameterizedSparqlString</a> javadocs for a comprehensive reference of available methods for setting values,
the following sections shows some basic examples of this.</p>
<h4 id="variable-parameters">Variable Parameters</h4>
<p>Any SPARQL variable in the command text may have a value injected to it, injecting a value replaces all usages of
diff --git a/content/documentation/query/spatial-query.html b/content/documentation/query/spatial-query.html
index be1aea5..817377b 100644
--- a/content/documentation/query/spatial-query.html
+++ b/content/documentation/query/spatial-query.html
@@ -340,7 +340,7 @@ try {
</table>
<p>See <a href="http://edndoc.esri.com/arcsde/9.1/general_topics/understand_spatial_relations.htm">ESRIs docs on spatial relations</a></p>
<h2 id="spatial-dataset-assembler">Spatial Dataset Assembler</h2>
-<p>The usual way to describe an index is with a <a href="http://jena.apache.org/documentation/assembler/index.html">Jena assembler description</a>. Configurations can also be built with <a href="#how-to-use-it-by-code">code</a>. The assembler describes a “spatial dataset” which has an underlying RDF dataset and a spatial index. The spatial index describes the spatial index technology (Lucene or Solr) and the details needed for each.</p>
+<p>The usual way to describe an index is with a <a href="/documentation/assembler/index.html">Jena assembler description</a>. Configurations can also be built with <a href="#how-to-use-it-by-code">code</a>. The assembler describes a “spatial dataset” which has an underlying RDF dataset and a spatial index. The spatial index describes the spatial index technology (Lucene or Solr) and the details needed for each.</p>
<p>A spatial index has an
<a href="https://github.com/apache/jena/tree/master/jena-spatial/src/main/java/org/apache/jena/query/spatial/EntityDefinition.java">EntityDefinition</a>
which defines the properties to index, the name of the lucene/solr field used for storing the URI itself (e.g. “entityField”) and its geo information (e.g. latitude/longitude as “geoField”), and the custom geo predicates.</p>
diff --git a/content/documentation/query/text-query.html b/content/documentation/query/text-query.html
index af19ea9..bc74a85 100644
--- a/content/documentation/query/text-query.html
+++ b/content/documentation/query/text-query.html
@@ -243,7 +243,7 @@ structure of string literals rather than treating such literals as
opaque items. Unlike <code>FILTER</code>, an index can set the values of variables.
Assuming appropriate <a href="#configuration">configuration</a>, the
above query can use full text search via the
-<a href="https://jena.apache.org/documentation/query/extension.html#property-functions">ARQ property function extension</a>, <code>text:query</code>:</p>
+<a href="/documentation/query/extension.html#property-functions">ARQ property function extension</a>, <code>text:query</code>:</p>
<pre><code>PREFIX ex: <http://www.example.org/resources#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX text: <http://jena.apache.org/text#>
diff --git a/content/documentation/query/writing_propfuncs.html b/content/documentation/query/writing_propfuncs.html
index e4731f0..cf0467f 100644
--- a/content/documentation/query/writing_propfuncs.html
+++ b/content/documentation/query/writing_propfuncs.html
@@ -178,7 +178,7 @@
<p><strong>ARQ - Writing Property Functions</strong></p>
<p>See also <a href="writing_functions.html">Writing Filter Functions</a>.</p>
<p>Applications can add SPARQL property functions to the query engine. This is done by first implementing the
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunction.html"><code>PropertyFunction</code></a>
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunction.html"><code>PropertyFunction</code></a>
interface, and then either registering that function or using the fake <code>java:</code> URI scheme to dynamically
load the function.</p>
<p><strong>Writing SPARQL Property Functions</strong></p>
@@ -186,7 +186,7 @@ load the function.</p>
that allows a URI to name a function in the query processor. A key difference is that Property Functions may
generate new bindings.</p>
<p>Just like
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/function/Function.html">org.apache.jena.sparql.function.Function</a>
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/function/Function.html">org.apache.jena.sparql.function.Function</a>
there are various utility classes provided to simplify the creation of a Property Function. The selection of
one depends on the ‘style’ of the desired built-in. For example, <code>PFuncSimple</code> is expected to be the predicate
of triple patterns <code>?such ex:as ?this</code>, where neither argument is an <code>rdf:list</code>, and either may be a variable.
@@ -211,18 +211,18 @@ Alternatively, <code>PFuncAssignToObject</code> assumes that the subject will be
</code></pre>
<p>The choice of extension point determines the function signature that the developer will need to implement, and
primarily determines whether some of the arguments will be
-<a href="https://jena.apache.org/documentation/javadoc/jena/org/apache/jena/graph/Node.html"><code>org.apache.jena.graph.Node</code></a>s or
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropFuncArg.html"><code>org.apache.jena.sparql.pfunction.PropFuncArg</code></a>s.
+<a href="/documentation/javadoc/jena/org/apache/jena/graph/Node.html"><code>org.apache.jena.graph.Node</code></a>s or
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropFuncArg.html"><code>org.apache.jena.sparql.pfunction.PropFuncArg</code></a>s.
In the latter case, the programmer can determine whether the argument is a list as well as how many
arguments it consists of.</p>
<p><strong>Registration</strong></p>
<p>Every property function is associated with a particular
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/util/Context.html"><code>org.apache.jena.sparql.util.Context</code></a>.
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/util/Context.html"><code>org.apache.jena.sparql.util.Context</code></a>.
This allows you to limit the availability of the function to be global or associated with a particular dataset.
For example, a custom Property Function may expose an index which only has meaning with respect to some set
of data.</p>
<p>Assuming you have an implementation of
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunctionFactory.html"><code>org.apache.jena.sparql.pfunction.PropertyFunctionFactory</code></a>
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunctionFactory.html"><code>org.apache.jena.sparql.pfunction.PropertyFunctionFactory</code></a>
(shown later), you can register a function as follows:</p>
<pre><code>final PropertyFunctionRegistry reg = PropertyFunctionRegistry.chooseRegistry(ARQ.getContext());
reg.put("urn:ex:fn#example", new ExamplePropertyFunctionFactory);
@@ -235,7 +235,7 @@ reg.put("urn:ex:fn#example", new ExamplePropertyFunctionFactory);
PropertyFunctionRegistry.set(ds.getContext(), reg);
</code></pre>
<p>Note that
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunctionRegistry.html"><code>org.apache.jena.sparql.pfunction.PropertyFunctionRegistry</code></a>
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/pfunction/PropertyFunctionRegistry.html"><code>org.apache.jena.sparql.pfunction.PropertyFunctionRegistry</code></a>
has other <code>put</code> methods that allow registration by passing a <code>Class</code> object, as well.</p>
<p><strong>Implementation</strong></p>
<p>The implementation of a Property Function is actually quite straight forward once one is aware of the tools
@@ -270,14 +270,14 @@ no valid solutions to return, then an empty solution may be presented.</p>
easy to support typical use cases.</p>
<p>Of particular note:</p>
<ul>
-<li><a href="https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterNullIterator.html"><code>QueryIterNullIterator</code></a> - to indicate that there are no valid solutions/bindings for the given values</li>
-<li><a href="https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterSingleton.html"><code>QueryIterSingleton</code></a> - to provide a single solution/binding for the given values</li>
-<li><a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterPlainWrapper.html"><code>QueryIterPlainWrapper</code></a> - to provide multiple solutions/bindings for the given values</li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterNullIterator.html"><code>QueryIterNullIterator</code></a> - to indicate that there are no valid solutions/bindings for the given values</li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterSingleton.html"><code>QueryIterSingleton</code></a> - to provide a single solution/binding for the given values</li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/sparql/engine/iterator/QueryIterPlainWrapper.html"><code>QueryIterPlainWrapper</code></a> - to provide multiple solutions/bindings for the given values</li>
</ul>
<p>The second two cases require instances of <code>Binding</code> objects which can be obtained through static methods of
-<a href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/engine/binding/BindingFactory.html"><code>BindingFactory</code></a>.
-Creation of <code>Binding</code> objects will also require references to <a href="https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/sparql/core/Var.html"><code>Var</code></a>
-and <a href="https://jena.apache.org/documentation/javadoc/jena/org/apache/jena/graph/NodeFactory.html"><code>NodeFactory</code></a></p>
+<a href="/documentation/javadoc/arq/org/apache/jena/sparql/engine/binding/BindingFactory.html"><code>BindingFactory</code></a>.
+Creation of <code>Binding</code> objects will also require references to <a href="/documentation/javadoc/arq/org/apache/jena/sparql/core/Var.html"><code>Var</code></a>
+and <a href="/documentation/javadoc/jena/org/apache/jena/graph/NodeFactory.html"><code>NodeFactory</code></a></p>
<p>Note that it can make a lot of sense to generate the <code>Iterator<Binding></code> for <code>QueryIterPlainWrapper</code> by means of
Jena’s <code>ExtendedIterator</code>. This can allow domain-specific value to be easily mapped to <code>Binding</code> objects in
a lazy fashion.</p>
diff --git a/content/documentation/rdf/index.html b/content/documentation/rdf/index.html
index 762ddad..e685068 100644
--- a/content/documentation/rdf/index.html
+++ b/content/documentation/rdf/index.html
@@ -299,7 +299,7 @@ are defined by RDF or Turtle: authors of RDF content should ensure that all pref
are defined before use.</p>
<p><strong>Note</strong></p>
<p>Jena does not treat namespaces in a special way. A <code>Model</code> will remember any prefixes defined
-in the input RDF (see the <a href="http://jena.apache.org/documentation/javadoc/jena/org/apache/jena/shared/PrefixMapping.html"><code>PrefixMapping</code></a>
+in the input RDF (see the <a href="/documentation/javadoc/jena/org/apache/jena/shared/PrefixMapping.html"><code>PrefixMapping</code></a>
interface; all Jena <code>Model</code> objects extend <code>PrefixMapping</code>), and the output writers which
serialize a model to XML or Turtle will normally attempt to use prefixes to abbreviate URI’s.
However internally, a <code>Resource</code> URI is not separated into a namespace and local-name pair.
@@ -334,12 +334,12 @@ For brevity, we shorten <code>org.apache.jena</code> to <code>oaj</code>.</p>
<tr>
<td>oaj.jena.datatypes</td>
<td>Provides the core interfaces through which datatypes are described to Jena.</td>
-<td><a href="http://jena.apache.org/documentation/notes/typed-literals.html">Typed literals</a></td>
+<td><a href="/documentation/notes/typed-literals.html">Typed literals</a></td>
</tr>
<tr>
<td>oaj.jena.ontology</td>
<td>Abstractions and convenience classes for accessing and manipulating ontologies represented in RDF.</td>
-<td><a href="http://jena.apache.org/documentation/ontology/index.html">Ontology API</a></td>
+<td><a href="/documentation/ontology/index.html">Ontology API</a></td>
</tr>
<tr>
<td>oaj.jena.rdf.listeners</td>
@@ -349,7 +349,7 @@ For brevity, we shorten <code>org.apache.jena</code> to <code>oaj</code>.</p>
<tr>
<td>oaj.jena.reasoner</td>
<td>The reasoner subsystem is supports a range of inference engines which derive additional information from an RDF model</td>
-<td><a href="http://jena.apache.org/documentation/inference/index.html">Reasoner how-to</a></td>
+<td><a href="/documentation/inference/index.html">Reasoner how-to</a></td>
</tr>
<tr>
<td>oaj.jena.shared</td>
@@ -363,7 +363,7 @@ For brevity, we shorten <code>org.apache.jena</code> to <code>oaj</code>.</p>
</tr>
</tbody>
</table>
-<p>oaj.jena.xmloutput | Writing RDF/XML. | <a href="http://jena.apache.org/documentation/io/index.html">I/O index</a></p>
+<p>oaj.jena.xmloutput | Writing RDF/XML. | <a href="/documentation/io/index.html">I/O index</a></p>
</div>
diff --git a/content/documentation/rdfconnection/index.html b/content/documentation/rdfconnection/index.html
index e2d321b..b3c4e08 100644
--- a/content/documentation/rdfconnection/index.html
+++ b/content/documentation/rdfconnection/index.html
@@ -210,7 +210,7 @@ qExec.close() ;
conn.close() ;
</code></pre>
<p>Jena also provides a separate
-<a href="//jena.staging.apache.org/documentation/jdbc/index.html">SPARQL over JDBC driver</a>
+<a href="/documentation/jdbc/index.html">SPARQL over JDBC driver</a>
library.</p>
<h2 id="transactions">Transactions</h2>
<p>Transactions are the preferred way to work with RDF data.
@@ -273,7 +273,7 @@ builder to construct <code>RDFConnectionRemote</code>s.</p>
and <a href="https://github.com/apache/jena/blob/master/jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/examples/RDFConnectionExample5.java">example
5</a>.</p>
<p>There are many options, including setting HTTP headers for content types
-(<a href="//jena.apache.org/documentation/javadoc/rdfconnection/index.html">javadoc</a>)
+(<a href="/documentation/javadoc/rdfconnection/index.html">javadoc</a>)
and providing detailed configuration with
<a href="https://hc.apache.org/httpcomponents-client-ga/">Apache HttpComponents HttpClient</a>.</p>
<h3 id="fuseki-specific-connection">Fuseki Specific Connection</h3>
@@ -300,8 +300,7 @@ add more RDF data into a graph, and delete a graph from a dataset.</p>
</code></pre>
<p>The file extension is used to determine the syntax.</p>
<p>There is also a set of scripts to help do these operations from the command
-line with
-<a href="//jena.apache.org/documentation/fuseki2/soh.html">SOH</a>.
+line with <a href="/documentation/fuseki2/soh.html">SOH</a>.
It is possible to write curl scripts as well. The SPARQL Graph
Store Protocol provides a standardised way to manage the data in a dataset.</p>
<p>In addition, <code>RDFConnection</code> provides an extension to give the same style
diff --git a/content/documentation/serving_data/index.html b/content/documentation/serving_data/index.html
index 7c80ab4..d021591 100644
--- a/content/documentation/serving_data/index.html
+++ b/content/documentation/serving_data/index.html
@@ -173,13 +173,12 @@
<h2 id="see-the-fuseki2-documentationdocumentationfuseki2">See the <a href="/documentation/fuseki2/">Fuseki2 documentation</a>.</h2>
<hr>
<blockquote>
-<p>This page covers Fuseki1.
-Fuseki1 is deprecated and has been retired.
-<a href="/documentation/fuseki2/">Fuseki2</a> is current.
+<p>This page covers Fuseki1.<br/>
+Fuseki1 is deprecated and has been retired.<br/>
+<a href="/documentation/fuseki2/">Fuseki2</a> is current.<br/>
<br/>
-The last release of Jena with this module is Jena 3.9.0.
-See <a href="https://github.com/apache/jena/tree/master/fuseki1">jena-fuseki1/README.md</a>.
-The <a href="fuseki1">original documentation</a>.</p>
+The last release of Jena with this module is Jena 3.9.0.<br/>
+The <a href="/documentation/archive/serving_data/fuseki1.html">original documentation</a>.</p>
</blockquote>
<hr>
diff --git a/content/documentation/shacl/index.html b/content/documentation/shacl/index.html
index c55e4dd..95125e0 100644
--- a/content/documentation/shacl/index.html
+++ b/content/documentation/shacl/index.html
@@ -198,7 +198,7 @@ Group tests.</p>
.
</pre>
<p>This requires a “new style” endpoint declaration: see
-“<a href="https://jena.apache.org/documentation/fuseki2/fuseki-config-endpoint.html">Fuseki Endpoint Configuration</a>".</p>
+“<a href="/documentation/fuseki2/fuseki-config-endpoint.html">Fuseki Endpoint Configuration</a>".</p>
<p>This is not installed into a dataset setup by default; a configuration file using
<code>fuseki:serviceShacl</code> is necessary (or programmatic setup for Fuskei Main).</p>
<p>The service accepts a shapes graph posted as RDF to <tt>/<i>ds</i>/shacl</tt> with
diff --git a/content/documentation/tdb/index.html b/content/documentation/tdb/index.html
index c7d72c3..26f5b45 100644
--- a/content/documentation/tdb/index.html
+++ b/content/documentation/tdb/index.html
@@ -170,12 +170,10 @@
</div>
<h1 class="title">TDB</h1>
- <p>TDB is a component of
-<a href="http://jena.apache.org/">Jena</a> for RDF storage
-and query. It support the full range of Jena APIs.
-TDB can be used as a high performance RDF store on a single machine.
-This documentation describes the latest version, unless
-otherwise noted.</p>
+ <p>TDB is a component of <a href="https://jena.apache.org/">Jena</a> for RDF storage and
+query. It support the full range of Jena APIs. TDB can be used as a high
+performance RDF store on a single machine. This documentation describes the
+latest version, unless otherwise noted.</p>
<p>This is the documentation for the current standard version of TDB.
This is also called TDB1 to distinguish it from the next generation version
<a href="../tdb2/">TDB2</a></p>
diff --git a/content/documentation/tdb2/index.html b/content/documentation/tdb2/index.html
index 8acc61d..ab4ae72 100644
--- a/content/documentation/tdb2/index.html
+++ b/content/documentation/tdb2/index.html
@@ -170,11 +170,10 @@
</div>
<h1 class="title">TDB2</h1>
- <p>TDB2 is a component of
-<a href="http://jena.apache.org">Apache Jena</a> for RDF storage
-and query. It support the full range of Jena APIs.
-TDB2 can be used as a high performance RDF store on a single machine.
-TDB2 can be used with Apache Jena Fuseki.</p>
+ <p>TDB2 is a component of <a href="https://jena.apache.org">Apache Jena</a> for RDF storage
+and query. It support the full range of Jena APIs. TDB2 can be used as a high
+performance RDF store on a single machine. TDB2 can be used with Apache Jena
+Fuseki.</p>
<p>TDB1 is the previous generation native storage system for Jena.</p>
<p>Compared to TDB1:</p>
<ul>
diff --git a/content/documentation/tools/schemagen-maven.html b/content/documentation/tools/schemagen-maven.html
index 893390a..838d049 100644
--- a/content/documentation/tools/schemagen-maven.html
+++ b/content/documentation/tools/schemagen-maven.html
@@ -176,8 +176,8 @@
<h1 class="title">Schemagen Maven</h1>
<h1 id="schemagen-maven-generating-java-source-files-from-owl-and-rdfs-ontologies-via-maven">Schemagen-maven: generating Java source files from OWL and RDFS ontologies via Maven</h1>
-<p>The <a href="http://jena.apache.org">Apache Jena</a> command line tool
-<a href="http://jena.apache.org/documentation/tools/schemagen.html"><code>schemagen</code></a>
+<p>The <a href="/">Apache Jena</a> command line tool
+<a href="/documentation/tools/schemagen.html"><code>schemagen</code></a>
provides an automated way of creating
Java source code constants from ontology files in an RDF-based project. This
can be very convenient, as it provides both a level of robustness that the
@@ -278,7 +278,7 @@ in <code>src/main/vocabs</code>:</p>
<h3 id="specifying-processing-options">Specifying processing options</h3>
<p>Options are, in general, given in the <code><fileOptions></code> section. A given
<code><source></code> refers to one input source - one file - as named by the
-<code><input></code> name. The actual option names are taken from the RDF <a href="http://jena.apache.org/documentation/tools/schemagen.html">config
+<code><input></code> name. The actual option names are taken from the RDF <a href="/documentation/tools/schemagen.html">config
file property names</a>,
omitting the namespace:</p>
<pre><code> <fileOptions>
diff --git a/content/index.xml b/content/index.xml
index 8a29e87..44d041c 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -798,24 +798,24 @@ SPARQL Graph Store Protocol inc extensions - dataset HTTP verbs.</description>
<item>
<title>Fuseki: serving RDF data over HTTP</title>
- <link>https://jena.apache.org/documentation/serving_data/</link>
+ <link>https://jena.apache.org/documentation/archive/serving_data/fuseki1.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/serving_data/</guid>
- <description>See the Fuseki2 documentation. This page covers Fuseki1. Fuseki1 is deprecated and has been retired. Fuseki2 is current. The last release of Jena with this module is Jena 3.9.0. See jena-fuseki1/README.md. The original documentation.
- </description>
+ <guid>https://jena.apache.org/documentation/archive/serving_data/fuseki1.html</guid>
+ <description>See the Fuseki2 documentation. This page covers Fuseki v1. Fuseki1 is deprecated and has been retired. The last release of Jena with this module is Jena 3.9.0.
+ Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.
+The relevant SPARQL standards are:
+ SPARQL 1.1 Query SPARQL 1.1 Update SPARQL 1.1 Protocol SPARQL 1.1 Graph Store HTTP Protocol Contents Download Getting Started Security Logging Server URI scheme Running a Fuseki Server Fuseki Configuration File SPARQL Over HTTP Use from Java Development System Download Fuseki1 Binaries for Fuseki1 are available from the maven repositories.</description>
</item>
<item>
<title>Fuseki: serving RDF data over HTTP</title>
- <link>https://jena.apache.org/documentation/serving_data/fuseki1.html</link>
+ <link>https://jena.apache.org/documentation/serving_data/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/serving_data/fuseki1.html</guid>
- <description>See the Fuseki2 documentation. This page covers Fuseki v1. Fuseki1 is deprecated and has been retired. The last release of Jena with this module is Jena 3.9.0. See jena-fuseki1/README.md. This is the original documentation.
- Fuseki is a SPARQL server. It provides REST-style SPARQL HTTP Update, SPARQL Query, and SPARQL Update using the SPARQL protocol over HTTP.
-The relevant SPARQL standards are:
- SPARQL 1.1 Query SPARQL 1.</description>
+ <guid>https://jena.apache.org/documentation/serving_data/</guid>
+ <description>See the Fuseki2 documentation. This page covers Fuseki1. Fuseki1 is deprecated and has been retired. Fuseki2 is current. The last release of Jena with this module is Jena 3.9.0. The original documentation.
+ </description>
</item>
<item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 2b0561d..ec3ee22 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -64,12 +64,12 @@
<url>
<loc>https://jena.apache.org/documentation/fuseki2/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:36+01:00</lastmod>
</url>
<url>
<loc>https://jena.apache.org/documentation/geosparql/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -89,12 +89,12 @@
<url>
<loc>https://jena.apache.org/documentation/shacl/</loc>
- <lastmod>2020-04-22T11:21:55-05:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
<loc>https://jena.apache.org/documentation/query/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -134,7 +134,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/construct-quad.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -159,7 +159,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/generate-json-from-sparql.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -224,7 +224,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/writing_propfuncs.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -284,7 +284,7 @@
<url>
<loc>https://jena.apache.org/documentation/csv/get_started.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -294,12 +294,12 @@
<url>
<loc>https://jena.apache.org/documentation/fuseki2/data-access-control.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
<loc>https://jena.apache.org/documentation.html</loc>
- <lastmod>2020-04-28T17:30:14+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:36+01:00</lastmod>
</url>
<url>
@@ -344,7 +344,7 @@
<url>
<loc>https://jena.apache.org/documentation/fuseki2/fuseki-main.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -383,13 +383,13 @@
</url>
<url>
- <loc>https://jena.apache.org/documentation/serving_data/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <loc>https://jena.apache.org/documentation/archive/serving_data/fuseki1.html</loc>
+ <lastmod>2020-04-29T21:07:36+01:00</lastmod>
</url>
<url>
- <loc>https://jena.apache.org/documentation/serving_data/fuseki1.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <loc>https://jena.apache.org/documentation/serving_data/</loc>
+ <lastmod>2020-04-29T21:07:36+01:00</lastmod>
</url>
<url>
@@ -449,7 +449,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/http-auth.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -499,7 +499,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/text-query.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -514,7 +514,7 @@
<url>
<loc>https://jena.apache.org/documentation/jdbc/drivers.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -614,7 +614,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/parameterized-sparql-strings.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -644,7 +644,7 @@
<url>
<loc>https://jena.apache.org/documentation/rdfconnection/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:36+01:00</lastmod>
</url>
<url>
@@ -659,7 +659,7 @@
<url>
<loc>https://jena.apache.org/documentation/io/rdf-input.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -699,7 +699,7 @@
<url>
<loc>https://jena.apache.org/documentation/tools/schemagen-maven.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -804,7 +804,7 @@
<url>
<loc>https://jena.apache.org/tutorials/sparql.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -849,7 +849,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/spatial-query.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -869,7 +869,7 @@
<url>
<loc>https://jena.apache.org/documentation/tdb/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -954,7 +954,7 @@
<url>
<loc>https://jena.apache.org/documentation/tdb2/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -984,7 +984,7 @@
<url>
<loc>https://jena.apache.org/documentation/rdf/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -1014,7 +1014,7 @@
<url>
<loc>https://jena.apache.org/tutorials/sparql_pt.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
@@ -1044,7 +1044,7 @@
<url>
<loc>https://jena.apache.org/tutorials.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-04-29T21:07:12+01:00</lastmod>
</url>
<url>
diff --git a/content/tutorials/sparql.html b/content/tutorials/sparql.html
index 6cc36ef..0439664 100644
--- a/content/tutorials/sparql.html
+++ b/content/tutorials/sparql.html
@@ -171,7 +171,7 @@
SPARQL. The tutorial covers the major features of the query
language through examples but does not aim to be complete.</p>
<p>If you are looking for a short introduction to SPARQL and Jena try
-<a href="http://www.ibm.com/developerworks/xml/library/j-sparql/">Search RDF data with SPARQL</a>. If you are looking to execute SPARQL queries in code and already known SPARQL then you likely want to read the <a href="https://jena.apache.org/documentation/query/index.html">ARQ Documentation</a> instead.</p>
+<a href="http://www.ibm.com/developerworks/xml/library/j-sparql/">Search RDF data with SPARQL</a>. If you are looking to execute SPARQL queries in code and already known SPARQL then you likely want to read the <a href="/documentation/query/index.html">ARQ Documentation</a> instead.</p>
<p>SPARQL is a
<a href="http://www.w3.org/TR/sparql11-query/">query language</a> and a
<a href="http://www.w3.org/TR/rdf-sparql-protocol/">protocol</a> for accessing
diff --git a/content/tutorials/sparql_pt.html b/content/tutorials/sparql_pt.html
index 23e83f8..7985d50 100644
--- a/content/tutorials/sparql_pt.html
+++ b/content/tutorials/sparql_pt.html
@@ -169,7 +169,7 @@
<p>O objetivo deste tutorial é dar um curso rápido sobre SPARQL. Esse tutorial cobre os principais aspectos desta linguagem de consulta através de exemplos, mas não tem como objetivo ser completo.</p>
<p>Se você estiver procurando uma pequena introdução a SPARQL e Jena, experimente
-<a href="http://www.ibm.com/developerworks/xml/library/j-sparql/">Search RDF data with SPARQL</a>. Se você quer executar consultas SPARQL e já sabe como ele funciona, então você deveria ler a <a href="http://jena.apache.org/documentation/query/index.html">ARQ Documentation</a>.</p>
+<a href="http://www.ibm.com/developerworks/xml/library/j-sparql/">Search RDF data with SPARQL</a>. Se você quer executar consultas SPARQL e já sabe como ele funciona, então você deveria ler a <a href="/documentation/query/index.html">ARQ Documentation</a>.</p>
<p>SPARQL é uma
<a href="http://www.w3.org/TR/sparql11-query/">linguagem de consulta</a> e um
<a href="http://www.w3.org/TR/rdf-sparql-protocol/">protocolo</a> para acesso a