You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by bu...@apache.org on 2015/07/26 12:50:20 UTC
svn commit: r959629 [2/10] - in /websites/staging/jena/trunk/content: ./
about_jena/ documentation/ documentation/assembler/ documentation/csv/
documentation/extras/ documentation/extras/querybuilder/
documentation/fuseki2/ documentation/hadoop/ docume...
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,14 +144,25 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="fuseki-data-services">Fuseki : Data Services</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fuseki-data-services">Fuseki : Data Services<a class="headerlink" href="#fuseki-data-services" title="Permanent link">¶</a></h1>
<p>Fuseki provides a number of "data services" - each data service is an RDF datasets
and a configurable set of endpoints for various operations such as SPARQL query,
SPARQL update and file upload.</p>
<p>URI scheme.
Datasets and services
Admin</p>
-<h2 id="sparql-protocol">SPARQL Protocol</h2>
+<h2 id="sparql-protocol">SPARQL Protocol<a class="headerlink" href="#sparql-protocol" title="Permanent link">¶</a></h2>
<p>Queyr
update
GSP including direct naming for GSP</p>
@@ -161,7 +172,7 @@ GSP including direct naming for GSP</p>
<blockquote>
<p><em>@@ Just rough notes : out-of-date and inconsistent</em></p>
</blockquote>
-<h2 id="naming">Naming</h2>
+<h2 id="naming">Naming<a class="headerlink" href="#naming" title="Permanent link">¶</a></h2>
<p>The naming style for application operations is:</p>
<p>/ name / endpoint ? parameters</p>
<p>where <code>name</code> is</p>
@@ -175,9 +186,9 @@ of the dataset.</p>
<p>There is also an internal name, generated by the server which is a UUID.
This UUID is never reused even if the dataset name is reused after the
first use is deleted.</p>
-<h2 id="services-and-datasets">Services and Datasets</h2>
+<h2 id="services-and-datasets">Services and Datasets<a class="headerlink" href="#services-and-datasets" title="Permanent link">¶</a></h2>
<p>Service </p>
-<h3 id="query">Query</h3>
+<h3 id="query">Query<a class="headerlink" href="#query" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">GEThttp</span><span class="p">:</span><span class="o">//</span><span class="n">host</span><span class="p">:</span><span class="n">port</span><span class="o">/</span><span class="n">dataset</span>?<span class="n">query</span><span class="p">=..</span>
<span class="n">POST</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">host</span><span class="p">:</span><span class="n">port</span><span class="o">/</span><span class="n">dataset</span>
@@ -185,7 +196,7 @@ first use is deleted.</p>
</pre></div>
-<h3 id="update">Update</h3>
+<h3 id="update">Update<a class="headerlink" href="#update" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">POST</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">host</span><span class="p">:</span><span class="n">port</span><span class="o">/</span><span class="n">dataset</span>?<span class="n">update</span><span class="p">=...</span>
<span class="n">POST</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">host</span><span class="p">:</span><span class="n">port</span><span class="o">/</span><span class="n">dataset</span>?<span class="n">update</span>
</pre></div>
@@ -197,13 +208,13 @@ first use is deleted.</p>
</pre></div>
-<h3 id="gsp">GSP</h3>
+<h3 id="gsp">GSP<a class="headerlink" href="#gsp" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">host</span><span class="p">:</span><span class="n">port</span><span class="o">/</span><span class="n">dataset</span>?<span class="n">default</span>
<span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">host</span><span class="p">:</span><span class="n">port</span><span class="o">/</span><span class="n">dataset</span>?<span class="n">graph</span><span class="p">=...</span>
</pre></div>
-<h2 id="the-dataset-lifecycle">The Dataset Lifecycle</h2>
+<h2 id="the-dataset-lifecycle">The Dataset Lifecycle<a class="headerlink" href="#the-dataset-lifecycle" title="Permanent link">¶</a></h2>
<p>The lifecycle of a dataset </p>
<ul>
<li>Active </li>
@@ -214,7 +225,7 @@ first use is deleted.</p>
<p>When offline, the dataset is unavailable for application requests but the name remains in-use and the configuration information retained. When made active again, the dataset and it's associated services are recreated. When offline, Fuseki does not retain any access to the data so the dataset can be changed with tools outside of Fuseki. When active, Fuseki assumes it has full control of a dataset (in particular TDB datasets can not be updated by other applications while active).</p>
<p>When Fuseki is not running, all datasets can be considered offline even if they were not explicitly made so prior to shutdown of the server.</p>
<p>(If a dataset uses in-memory storage, changes to its state are lost even though it is recreated from its; configuration when the server restarts.)</p>
-<h2 id="links">Links</h2>
+<h2 id="links">Links<a class="headerlink" href="#links" title="Permanent link">¶</a></h2>
</div>
</div>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-java.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-java.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-java.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h2 id="client-code-working-with-sparql-servers">Client code : Working with SPARQL Servers</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="client-code-working-with-sparql-servers">Client code : Working with SPARQL Servers<a class="headerlink" href="#client-code-working-with-sparql-servers" title="Permanent link">¶</a></h2>
<blockquote>
<p><em>@@</em></p>
</blockquote>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-layout.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-layout.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-layout.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="fuskei-file-system-layout">Fuskei File System Layout</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fuskei-file-system-layout">Fuskei File System Layout<a class="headerlink" href="#fuskei-file-system-layout" title="Permanent link">¶</a></h1>
<blockquote>
<p>@@ Check: log4j.properties, run/databases/</p>
</blockquote>
@@ -157,7 +168,7 @@ Symbolic links can be used to create var
is used for Unix service deployments. When deployment as a WAR file,
everything is in the WAR file itself.</p>
<p><code>FUSEKI_BASE</code> - this contains the deployment files.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Mode</th>
@@ -203,10 +214,10 @@ everything is in the WAR file itself.</p
<code>FUSEKI_BASE</code> will be <code>/etc/fuseki</code>.</p>
<p>If <code>FUSEKI_BASE</code> is the same as <code>FUSEKI_HOME</code>, be careful when upgrading not to delete
server deployment files and directories.</p>
-<h1 id="old-world-and-migration-from-fuseki-1">Old World and migration from Fuseki 1.</h1>
+<h1 id="old-world-and-migration-from-fuseki-1">Old World and migration from Fuseki 1.<a class="headerlink" href="#old-world-and-migration-from-fuseki-1" title="Permanent link">¶</a></h1>
<p><code>config.ttl</code></p>
-<h1 id="distribution-area-fuseki_home">Distribution area -- <code>FUSEKI_HOME</code></h1>
-<table>
+<h1 id="distribution-area-fuseki_home">Distribution area -- <code>FUSEKI_HOME</code><a class="headerlink" href="#distribution-area-fuseki_home" title="Permanent link">¶</a></h1>
+<table class="table">
<thead>
<tr>
<th>Directory or File</th>
@@ -248,8 +259,8 @@ server deployment files and directories.
</tr>
</tbody>
</table>
-<h1 id="runtime-area-fuseki_base">Runtime area -- <code>FUSEKI_BASE</code></h1>
-<table>
+<h1 id="runtime-area-fuseki_base">Runtime area -- <code>FUSEKI_BASE</code><a class="headerlink" href="#runtime-area-fuseki_base" title="Permanent link">¶</a></h1>
+<table class="table">
<thead>
<tr>
<th>Directory or File</th>
@@ -293,7 +304,7 @@ server deployment files and directories.
</table>
<p>The <code>system_files/</code> keeps a copy of any assemblers uploaded to
configure the server. The master copy is kept in the system database.</p>
-<h1 id="resetting">Resetting</h1>
+<h1 id="resetting">Resetting<a class="headerlink" href="#resetting" title="Permanent link">¶</a></h1>
<p>To reset the server, stop the server, and delete the system database in <code>system/</code>,
the <code>system_files/</code> and any other unwanted deployment files,
then restart the server.</p>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,13 +144,24 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="fuseki-logging">Fuseki Logging</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fuseki-logging">Fuseki Logging<a class="headerlink" href="#fuseki-logging" title="Permanent link">¶</a></h1>
<p>Fuseki logs operation details and also provides a standard NCSA request log. </p>
<p>Logging is via <a href="http://slf4j.org/">slj4j</a> over
(Apache Log4J)[http://logging.apache.org/log4j/].
Logging output is controlled via log4j.</p>
-<h2 id="server-logs">Server Logs</h2>
-<table>
+<h2 id="server-logs">Server Logs<a class="headerlink" href="#server-logs" title="Permanent link">¶</a></h2>
+<table class="table">
<thead>
<tr>
<th>Full Log name</th>
@@ -184,14 +195,14 @@ Logging output is controlled via log4j.<
</tr>
</tbody>
</table>
-<h2 id="ncsa-request-log">NCSA request Log.</h2>
+<h2 id="ncsa-request-log">NCSA request Log.<a class="headerlink" href="#ncsa-request-log" title="Permanent link">¶</a></h2>
<p>This log is in NCSA extended/combined log format.<br />
Many web log analysers can process this format.</p>
<p>This log is normally off.</p>
<p>When run as a WAR file inside a webapp container
(e.g. <a href="http://tomcat.apache.org/">Apache Tomcat</a>), the webapp container
or reverse proxy will log access requests anyway. </p>
-<h2 id="setting-logging">Setting logging</h2>
+<h2 id="setting-logging">Setting logging<a class="headerlink" href="#setting-logging" title="Permanent link">¶</a></h2>
<p>The Fuseki engine looks for the log4j configuration as follows:</p>
<ul>
<li>Use system property <code>log4j.configuration</code> if defined (as usual for log4j).</li>
@@ -208,9 +219,9 @@ the base jar. It is better to include <
<code>FUSEKI_BASE</code>. For the WAR file, <code>FUSEKI_BASE</code> defaults to <code>/etc/fuseki</code>
on Linux. For the standalone server, <code>FUSEKI_BASE</code> defaults to directory
<code>run/</code> within the directory where the server is run.</p>
-<h2 id="default-setting">Default setting</h2>
+<h2 id="default-setting">Default setting<a class="headerlink" href="#default-setting" title="Permanent link">¶</a></h2>
<p>The <a href="https://github.com/apache/jena/blob/master/jena-fuseki2/jena-fuseki-core/src/main/resources/org/apache/jena/fuseki/log4j.properties">default log4j.properties</a>.</p>
-<h2 id="logrotate">Logrotate</h2>
+<h2 id="logrotate">Logrotate<a class="headerlink" href="#logrotate" title="Permanent link">¶</a></h2>
<p>Below is an example logrotate(1) configuration (to go in <code>/etc/logrotate.d</code>)
assuming the log file has been put in <code>/etc/fuseki/logs/fuseki.log</code>.</p>
<p>It rotates the logs once a month, compresses logs on rotation and keeps them for 6 months.</p>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-quick-start.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-quick-start.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-quick-start.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,10 +144,21 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="fuseki-quickstart">Fuseki Quickstart</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fuseki-quickstart">Fuseki Quickstart<a class="headerlink" href="#fuseki-quickstart" title="Permanent link">¶</a></h1>
<p>This page describes how to achieve certain common tasks in the most direct way possible.</p>
<p><em>CHECK</em></p>
-<h2 id="running-with-apache-tomcat-and-loading-a-file">Running with Apache Tomcat and loading a file.</h2>
+<h2 id="running-with-apache-tomcat-and-loading-a-file">Running with Apache Tomcat and loading a file.<a class="headerlink" href="#running-with-apache-tomcat-and-loading-a-file" title="Permanent link">¶</a></h2>
<ol>
<li>Unpack the distribution.</li>
<li>Copy the WAR file into the Aapche tomcat webass dietory, under the name 'fuseki'</li>
@@ -155,12 +166,12 @@
<li>Press "", choose "in-memory".</li>
<li>Go to "add data" and load the file (single graph).</li>
</ol>
-<h2 id="publish-an-rdf-file-as-a-sparql-endpoint">Publish an RDF file as a SPARQL endpoint.</h2>
+<h2 id="publish-an-rdf-file-as-a-sparql-endpoint">Publish an RDF file as a SPARQL endpoint.<a class="headerlink" href="#publish-an-rdf-file-as-a-sparql-endpoint" title="Permanent link">¶</a></h2>
<ol>
<li>Unpack the distribution.</li>
<li>Run <code>fuseki-server --file FILE /name</code></li>
</ol>
-<h2 id="explore-a-tdb-database">Explore a TDB database</h2>
+<h2 id="explore-a-tdb-database">Explore a TDB database<a class="headerlink" href="#explore-a-tdb-database" title="Permanent link">¶</a></h2>
<ol>
<li>Unpack the distribution.</li>
<li>Run <code>fuseki-server --loc=DATABASE /name</code>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-run.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-run.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-run.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="running-fuseki">Running Fuseki</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="running-fuseki">Running Fuseki<a class="headerlink" href="#running-fuseki" title="Permanent link">¶</a></h1>
<p>Fuseki can be run in three ways</p>
<ul>
<li><a href="#fuseki-as-a-standalone-server">As a standalone server</a></li>
@@ -155,7 +166,7 @@
change internally but the scripts used here will retain the same interface.</p>
<p>See "<a href="fuseki-configuration.html">Fuseki Configuration</a>" for information on
how to provides datasetsand configure services.</p>
-<h2 id="fuseki-as-a-standalone-server">Fuseki as a Standalone Server</h2>
+<h2 id="fuseki-as-a-standalone-server">Fuseki as a Standalone Server<a class="headerlink" href="#fuseki-as-a-standalone-server" title="Permanent link">¶</a></h2>
<p>This is running Fuseki from the command line.</p>
<div class="codehilite"><pre><span class="n">fuseki</span><span class="o">-</span><span class="n">server</span> <span class="p">[</span><span class="o">--</span><span class="n">mem</span> <span class="o">|</span> <span class="o">--</span><span class="n">loc</span><span class="p">=</span><span class="n">DIR</span><span class="p">]</span> <span class="p">[[</span><span class="o">--</span><span class="n">update</span><span class="p">]</span> <span class="o">/</span><span class="n">NAME</span><span class="p">]</span>
@@ -178,7 +189,7 @@ the environment variable <code>FUSEKI_HO
distribution.</p>
<p>Unlike Fuseki v1, starting with no dataset and no configuration is possible.
Datasets can be added from the admin UI to a running server.</p>
-<h2 id="fuseki-as-a-web-application">Fuseki as a Web Application</h2>
+<h2 id="fuseki-as-a-web-application">Fuseki as a Web Application<a class="headerlink" href="#fuseki-as-a-web-application" title="Permanent link">¶</a></h2>
<p>Fuseki can run from a <a href="http://en.wikipedia.org/wiki/WAR_%28file_format%29">WAR</a> file.
Fuseki requires at least support for the Servlet 3.0 API (e.g. Apache Tomcat 7 or Jetty 8) as well as Java7.</p>
<p><code>FUSEKI_HOME</code> is not applicable.</p>
@@ -187,7 +198,7 @@ directory. It is initialised the first
<a href="http://shiro.apache.org/">Apache Shiro</a> security file but this is only
intended as a starting point. It restricts use of the admin UI to the
local machine.</p>
-<h2 id="fuseki-as-a-service">Fuseki as a Service</h2>
+<h2 id="fuseki-as-a-service">Fuseki as a Service<a class="headerlink" href="#fuseki-as-a-service" title="Permanent link">¶</a></h2>
<p>Fuseki can run as an operating system service, started when the server
machine boots. The script <code>fuseki</code> is a Linux <code>init.d</code> with the common
secondary arguments of <code>start</code> and <code>stop</code>.</p>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Security in Fuseki2</h1>
- <p>Fuseki2 provides security by using
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>Fuseki2 provides security by using
<a href="http://shiro.apache.org/">Apache Shiro</a>. This is controlled by a
configuration file <code>shiro.ini</code> located at <code>$FUSEKI_BASE/shiro.ini</code>.
If not found, the server initializes this with an preset initial
@@ -173,9 +184,9 @@ server to only process requests from the
ports.</p>
<p>Changing the security setup requires a server restart.</p>
<p>Contributions of more examples are very welcome.</p>
-<h2 id="examples">Examples</h2>
+<h2 id="examples">Examples<a class="headerlink" href="#examples" title="Permanent link">¶</a></h2>
<p>The shipped <code>shiro.ini</code> has additional comments.</p>
-<h3 id="the-default-configuration">The default configuration.</h3>
+<h3 id="the-default-configuration">The default configuration.<a class="headerlink" href="#the-default-configuration" title="Permanent link">¶</a></h3>
<p>This is a minimal configuration for the default configuration.</p>
<div class="codehilite"><pre><span class="k">[main]</span>
<span class="na">localhost</span><span class="o">=</span><span class="s">org.apache.jena.fuseki.authz.LocalhostFilter</span>
@@ -191,7 +202,7 @@ ports.</p>
</pre></div>
-<h3 id="simple-userpassword">Simple user/password</h3>
+<h3 id="simple-userpassword">Simple user/password<a class="headerlink" href="#simple-userpassword" title="Permanent link">¶</a></h3>
<p>This extract shows the simple user/password setup.</p>
<p>It adds a <code>[users]</code> section and changes the <code>/$/**</code> line in <code>[urls]</code></p>
<div class="codehilite"><pre><span class="k">[users]</span>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-stats.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-stats.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-stats.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,20 +144,31 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="fuseki-service-statistics">Fuseki Service Statistics</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="fuseki-service-statistics">Fuseki Service Statistics<a class="headerlink" href="#fuseki-service-statistics" title="Permanent link">¶</a></h1>
<p>A Fuseki server keeps detailed statistics for each dataset and each service
of a dataset keeps counters as to the number
of incoming requests, number of successful requests, number of bad requests
(i.e client errors), and number of failing requests (i.e. server errors).
Statistics are returned as JSON. They are also available via JMX.</p>
-<h2 id="structure-of-the-statistics-report">Structure of the Statistics Report</h2>
-<h3 id="sparql-protocol-service">SPARQL Protocol Service</h3>
+<h2 id="structure-of-the-statistics-report">Structure of the Statistics Report<a class="headerlink" href="#structure-of-the-statistics-report" title="Permanent link">¶</a></h2>
+<h3 id="sparql-protocol-service">SPARQL Protocol Service<a class="headerlink" href="#sparql-protocol-service" title="Permanent link">¶</a></h3>
<p>Query and Update</p>
-<h3 id="sparql-graph-store-protocol">SPARQL Graph Store Protocol</h3>
+<h3 id="sparql-graph-store-protocol">SPARQL Graph Store Protocol<a class="headerlink" href="#sparql-graph-store-protocol" title="Permanent link">¶</a></h3>
<p>inc extensions - dataset HTTP verbs.</p>
-<h4 id="other-services">Other services.</h4>
+<h4 id="other-services">Other services.<a class="headerlink" href="#other-services" title="Permanent link">¶</a></h4>
<p>File upload.</p>
-<h2 id="example">Example</h2>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="p">{</span> "<span class="n">datasets</span>" <span class="p">:</span> <span class="p">{</span>
"<span class="o">/</span><span class="n">ds</span>" <span class="p">:</span>
<span class="p">{</span> "<span class="n">Requests</span>" <span class="p">:</span> 0 <span class="p">,</span>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h2 id="apache-jena-fuseki">Apache Jena Fuseki</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="apache-jena-fuseki">Apache Jena Fuseki<a class="headerlink" href="#apache-jena-fuseki" title="Permanent link">¶</a></h2>
<blockquote>
<p>Fuseki2 is a new major revision of Fuseki.</p>
<ul>
@@ -167,7 +178,7 @@ transactional persistent storage layer,
and <a href="query/spatial-query.html">Jena spatial query</a>.<br />
It can be used to provide the protocol engine for other RDF query and
storage systems.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="#download-fuseki">Download</a></li>
<li><a href="#getting-started-with-fuseki">Getting Started</a></li>
@@ -175,7 +186,7 @@ storage systems.</p>
<li><a href="fuseki-run.html">Running Fuseki</a><ul>
<li><a href="fuseki-run.html#fuseki-as-a-web-application">As a web application</a></li>
<li><a href="fuseki-run.html#fuseki-as-a-service">As a service</a></li>
-<li><a href="fuseki-run.html#fuseki-as-a-standalone%20server">As a standalone server</a></li>
+<li><a href="fuseki-run.html#fuseki-as-a-standalone server">As a standalone server</a></li>
</ul>
</li>
<li>Architecture<ul>
@@ -195,9 +206,9 @@ storage systems.</p>
</ul>
<p>The Jena users mailing is the place to get help with Fuseki. </p>
<p><a href="/help_and_support/#email-support-lists">Email support lists</a></p>
-<h2 id="fuseki-1">Fuseki 1</h2>
+<h2 id="fuseki-1">Fuseki 1<a class="headerlink" href="#fuseki-1" title="Permanent link">¶</a></h2>
<p><a href="/documentation/serving_data/">Documentation for Fuseki1</a>.</p>
-<h2 id="download-fuseki">Download Fuseki</h2>
+<h2 id="download-fuseki">Download Fuseki<a class="headerlink" href="#download-fuseki" title="Permanent link">¶</a></h2>
<p>Releases of Apache Jena Fuseki can be downloaded from one of the mirror sites:</p>
<p><a href="/download">Jena Downloads</a></p>
<p>and previous releases are available from <a href="http://archive.apache.org/dist/jena/">the archive</a>.
@@ -205,7 +216,7 @@ We strongly recommend that users use the
preference to any older versions or of development builds.</p>
<p>Fuseki requires Java7.</p>
<p><strong>Fuseki download files</strong></p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Filename</th>
@@ -240,29 +251,29 @@ It is also available as a Java web appli
</pre></div>
-<h3 id="previous-releases">Previous releases</h3>
+<h3 id="previous-releases">Previous releases<a class="headerlink" href="#previous-releases" title="Permanent link">¶</a></h3>
<p>While previous releases are available, we strongly recommend that wherever
possible users use the latest official Apache releases of Jena in
preference to using any older versions of Jena.</p>
<p>Previous Apache Jena releases can be found in the Apache archive area
at <a href="http://archive.apache.org/dist/jena/">http://archive.apache.org/dist/jena</a></p>
-<h3 id="development-builds">Development Builds</h3>
+<h3 id="development-builds">Development Builds<a class="headerlink" href="#development-builds" title="Permanent link">¶</a></h3>
<p>Regular developement builds of all of Jena are available (these are not
formal releases) from the
<a href="https://repository.apache.org/snapshots/org/apache/jena">Apache snapshots maven repository</a>.
This includes packaged builds of Fuseki.</p>
-<h2 id="getting-started-with-fuseki">Getting Started With Fuseki</h2>
+<h2 id="getting-started-with-fuseki">Getting Started With Fuseki<a class="headerlink" href="#getting-started-with-fuseki" title="Permanent link">¶</a></h2>
<p>This section serves as a basic guide to getting a Fuskei server running on
your local machine. See <a href="fuseki-run.html">other sections</a> for complete
coverage of all the deployment methods for Fuseki.</p>
-<h2 id="how-to-contribute">How to Contribute</h2>
+<h2 id="how-to-contribute">How to Contribute<a class="headerlink" href="#how-to-contribute" title="Permanent link">¶</a></h2>
<p>We welcome contributions towards making Jena a better platform for semantic
web and linked data applications. We appreciate feature suggestions, bug
reports and patches for code or documentation.</p>
<p>See "<a href="/getting_involved/index.html">Getting Involved</a>" for ways to
contribute to Jena and Fuseki, including patches and making github
pull-requests.</p>
-<h3 id="source-code">Source code</h3>
+<h3 id="source-code">Source code<a class="headerlink" href="#source-code" title="Permanent link">¶</a></h3>
<p>The development codebase is available from git.</p>
<p>Development builds (not a formal release):
<a href="https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-fuseki/">SNAPSHOT</a></p>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/rdf-sparql-standards.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/rdf-sparql-standards.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/rdf-sparql-standards.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,8 +144,19 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="sparql-and-rdf-standards">SPARQL and RDF Standards</h1>
-<h2 id="sparql-standards">SPARQL Standards</h2>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="sparql-and-rdf-standards">SPARQL and RDF Standards<a class="headerlink" href="#sparql-and-rdf-standards" title="Permanent link">¶</a></h1>
+<h2 id="sparql-standards">SPARQL Standards<a class="headerlink" href="#sparql-standards" title="Permanent link">¶</a></h2>
<p>The relevant SPARQL 1.1 standards are:</p>
<ul>
<li><a href="http://www.w3.org/TR/sparql11-query/" title="http://www.w3.org/TR/sparql11-query/">SPARQL 1.1 Query</a></li>
@@ -156,7 +167,7 @@
<li><a href="http://www.w3.org/TR/sparql11-results-csv-tsv/" title="http://www.w3.org/TR/sparql11-results-csv-tsv/">SPARQL 1.1 Query Results CSV and TSV Formats</a></li>
<li><a href="http://www.w3.org/TR/rdf-sparql-XMLres/" title="http://www.w3.org/TR/rdf-sparql-XMLres/">SPARQL Query Results XML Format</a></li>
</ul>
-<h2 id="rdf-standards">RDF Standards</h2>
+<h2 id="rdf-standards">RDF Standards<a class="headerlink" href="#rdf-standards" title="Permanent link">¶</a></h2>
<p>Some RDF 1.1 standards</p>
<ul>
<li><a href="http://www.w3.org/TR/turtle/" title="http://www.w3.org/TR/turtle/">RDF 1.1 Turtle</a></li>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/soh.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/soh.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/soh.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title"></h1>
- <h1 id="soh-sparql-over-http">SOH - SPARQL over HTTP</h1>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="soh-sparql-over-http">SOH - SPARQL over HTTP<a class="headerlink" href="#soh-sparql-over-http" title="Permanent link">¶</a></h1>
<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>
@@ -161,21 +172,21 @@ with any compliant SPARQL 1.1 system off
</ul>
<p>Each command supports the <code>-v</code> flag to print out details of the
HTTP interaction.</p>
-<h2 id="contents">Contents</h2>
+<h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent link">¶</a></h2>
<ul>
<li><a href="#soh-sparql-query">SOH SPARQL Query</a></li>
<li><a href="#soh-sparql-http">SOH SPARQL HTTP</a></li>
<li><a href="#soh-sparql-update">SOH SPARQL Update</a></li>
<li><a href="#service-endpoints">Service endpoints</a></li>
</ul>
-<h2 id="soh-sparql-query">SOH SPARQL Query</h2>
+<h2 id="soh-sparql-query">SOH SPARQL Query<a class="headerlink" href="#soh-sparql-query" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">s</span><span class="o">-</span><span class="n">query</span> <span class="o">--</span><span class="n">service</span><span class="p">=</span><span class="n">endpointURL</span> <span class="s">'query string'</span>
<span class="n">s</span><span class="o">-</span><span class="n">query</span> <span class="o">--</span><span class="n">service</span><span class="p">=</span><span class="n">endpointURL</span> <span class="o">--</span><span class="n">query</span><span class="p">=</span><span class="n">queryFile</span><span class="p">.</span><span class="n">rq</span>
</pre></div>
-<h2 id="soh-sparql-http">SOH SPARQL HTTP</h2>
+<h2 id="soh-sparql-http">SOH SPARQL HTTP<a class="headerlink" href="#soh-sparql-http" title="Permanent link">¶</a></h2>
<p>The <a href="http://www.w3.org/TR/sparql11-http-rdf-update/">SPARQL Graph Store Protocol</a>
is a way to read, create and update whole graphs in an RDF Dataset.
It is useful for data management and building into
@@ -204,21 +215,21 @@ the HTTP content type.</p>
</pre></div>
-<h2 id="soh-sparql-update">SOH SPARQL Update</h2>
+<h2 id="soh-sparql-update">SOH SPARQL Update<a class="headerlink" href="#soh-sparql-update" title="Permanent link">¶</a></h2>
<div class="codehilite"><pre><span class="n">s</span><span class="o">-</span><span class="n">update</span> <span class="o">--</span><span class="n">service</span><span class="p">=</span><span class="n">endpointURL</span> <span class="s">'update string'</span>
<span class="n">s</span><span class="o">-</span><span class="n">update</span> <span class="o">--</span><span class="n">service</span><span class="p">=</span><span class="n">endpointURL</span> <span class="o">--</span><span class="n">update</span><span class="p">=</span><span class="n">updateFile</span><span class="p">.</span><span class="n">ru</span>
</pre></div>
-<h2 id="service-endpoints">Service endpoints</h2>
+<h2 id="service-endpoints">Service endpoints<a class="headerlink" href="#service-endpoints" title="Permanent link">¶</a></h2>
<p>SOH is a general purpose set of scripts that work with any SPARQL
1.1. server. Different servers offer different naming conventions
for HTTP REST, query and update. This section provides summary
information about using SOH with some servers. See the
documentation for each server for authoritative information.</p>
<p>If you have details for other servers, <a href="/getting_involved/index.html">get involved</a></p>
-<h3 id="fuseki">Fuseki</h3>
+<h3 id="fuseki">Fuseki<a class="headerlink" href="#fuseki" title="Permanent link">¶</a></h3>
<p>If a <a href="index.html">Fuseki</a> server is run with the
command:</p>
<div class="codehilite"><pre><span class="n">fuseki</span><span class="o">-</span><span class="n">server</span> <span class="o">--</span><span class="n">update</span> <span class="o">--</span><span class="n">mem</span> <span class="o">/</span><span class="n">MyDataset</span>
Modified: websites/staging/jena/trunk/content/documentation/hadoop/artifacts.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/hadoop/artifacts.html (original)
+++ websites/staging/jena/trunk/content/documentation/hadoop/artifacts.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,10 +144,21 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Maven Artifacts for Apache Jena Elephas</h1>
- <p>The Apache Jena Elephas libraries for Apache Hadoop are a collection of maven artifacts which can be used individually
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The Apache Jena Elephas libraries for Apache Hadoop are a collection of maven artifacts which can be used individually
or together as desired. These are available from the same locations as any other Jena
artifact, see <a href="/download/maven.html">Using Jena with Maven</a> for more information.</p>
-<h1 id="hadoop-dependencies">Hadoop Dependencies</h1>
+<h1 id="hadoop-dependencies">Hadoop Dependencies<a class="headerlink" href="#hadoop-dependencies" title="Permanent link">¶</a></h1>
<p>The first thing to note is that although our libraries depend on relevant Hadoop libraries these dependencies
are marked as <code>provided</code> and therefore are not transitive. This means that you may typically also need to
declare these basic dependencies as <code>provided</code> in your own POM:</p>
@@ -169,7 +180,7 @@ declare these basic dependencies as <cod
</pre></div>
-<h3 id="using-alternative-hadoop-versions">Using Alternative Hadoop versions</h3>
+<h3 id="using-alternative-hadoop-versions">Using Alternative Hadoop versions<a class="headerlink" href="#using-alternative-hadoop-versions" title="Permanent link">¶</a></h3>
<p>If you wish to use a different Hadoop version then we suggest that you build the modules yourself from source which can be
found in the <code>jena-elephas</code> folder of our source release (available on the <a href="../download/">Downloads</a> page) or from our Git
repository (see <a href="../getting_involved/">Getting Involved</a> for details of the repository).</p>
@@ -180,8 +191,8 @@ repository (see <a href="../getting_invo
<p>Would build for Hadoop <code>2.4.1</code></p>
<p><strong>Note</strong> that we only support Hadoop 2.x APIs and so Elephas cannot be built for Hadoop 1.x</p>
-<h1 id="jena-rdf-tools-for-apache-hadoop-artifacts">Jena RDF Tools for Apache Hadoop Artifacts</h1>
-<h2 id="common-api">Common API</h2>
+<h1 id="jena-rdf-tools-for-apache-hadoop-artifacts">Jena RDF Tools for Apache Hadoop Artifacts<a class="headerlink" href="#jena-rdf-tools-for-apache-hadoop-artifacts" title="Permanent link">¶</a></h1>
+<h2 id="common-api">Common API<a class="headerlink" href="#common-api" title="Permanent link">¶</a></h2>
<p>The <code>jena-elephas-common</code> artifact provides common classes for enabling RDF on Hadoop. This is mainly
composed of relevant <code>Writable</code> implementations for the various supported RDF primitives.</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
@@ -192,7 +203,7 @@ composed of relevant <code>Writable</cod
</pre></div>
-<h2 id="io-api">IO API</h2>
+<h2 id="io-api">IO API<a class="headerlink" href="#io-api" title="Permanent link">¶</a></h2>
<p>The <a href="io.html">IO API</a> artifact provides support for reading and writing RDF in Hadoop:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.jena<span class="nt"></groupId></span>
@@ -202,7 +213,7 @@ composed of relevant <code>Writable</cod
</pre></div>
-<h2 id="mapreduce">Map/Reduce</h2>
+<h2 id="mapreduce">Map/Reduce<a class="headerlink" href="#mapreduce" title="Permanent link">¶</a></h2>
<p>The <a href="mapred.html">Map/Reduce</a> artifact provides various building block mapper and reducer implementations
to help you get started writing Map/Reduce jobs over RDF data quicker:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
@@ -213,7 +224,7 @@ to help you get started writing Map/Redu
</pre></div>
-<h2 id="rdf-stats-demo">RDF Stats Demo</h2>
+<h2 id="rdf-stats-demo">RDF Stats Demo<a class="headerlink" href="#rdf-stats-demo" title="Permanent link">¶</a></h2>
<p>The <a href="demo.html">RDF Stats Demo</a> artifact is a Hadoop job jar which can be used to run some simple demo applications over your
own RDF data:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
Modified: websites/staging/jena/trunk/content/documentation/hadoop/common.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/hadoop/common.html (original)
+++ websites/staging/jena/trunk/content/documentation/hadoop/common.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,10 +144,21 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Apache Jena Elephas - Common API</h1>
- <p>The Common API provides the basic data model for representing RDF data within Apache Hadoop applications. This primarily takes the form of <code>Writable</code> implementations and the necessary machinery to efficiently serialise and deserialise these.</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The Common API provides the basic data model for representing RDF data within Apache Hadoop applications. This primarily takes the form of <code>Writable</code> implementations and the necessary machinery to efficiently serialise and deserialise these.</p>
<p>Currently we represent the three main RDF primitives - Nodes, Triples and Quads - though in future a wider range of primitives may be supported if we receive contributions to implement them.</p>
-<h1 id="rdf-primitives">RDF Primitives</h1>
-<h2 id="nodes">Nodes</h2>
+<h1 id="rdf-primitives">RDF Primitives<a class="headerlink" href="#rdf-primitives" title="Permanent link">¶</a></h1>
+<h2 id="nodes">Nodes<a class="headerlink" href="#nodes" title="Permanent link">¶</a></h2>
<p>The <code>Writable</code> type for nodes is predictably enough called <code>NodeWritable</code> and it implements the <code>WritableComparable</code> interface which means it can be used as both a key and/or value in Map/Reduce. In standard Hadoop style a <code>get()</code> method returns the actual value as a Jena <code>Node</code> instance while a corresponding <code>set()</code> method allows the value to be set. Coveying <code>null</code> values is acceptable and fully supported.</p>
<p>Note that nodes are lazily converted to and from the underlying binary representation so there is minimal overhead if you create a <code>NodeWritable</code> instance that does not actually ever get read/written.</p>
<p><code>NodeWritable</code> supports and automatically registers itself for Hadoop's <a href="https://hadoop.apache.org/docs/stable/api/org/apache/hadoop/io/WritableComparator.html"><code>WritableComparator</code></a> mechanism which allows it to provide high efficiency binary comparisons on nodes which helps reduce phases run faster by avoiding unnecessary deserialisation into POJOs.</p>
@@ -163,13 +174,13 @@
</pre></div>
-<h2 id="triples">Triples</h2>
+<h2 id="triples">Triples<a class="headerlink" href="#triples" title="Permanent link">¶</a></h2>
<p>Again the <code>Writable</code> type for nodes is simply called <code>TripleWritable</code> and it also implements the <code>WritableComparable</code> interface meaning it may be used as both a key and/or value. Again the standard Hadoop conventions of a <code>get()</code> and <code>set()</code> method to get/set the value as a Jena <code>Triple</code> are followed. Unlike the <code>NodeWritable</code> this class does not support conveying <code>null</code> values.</p>
<p>Like the other primitives it is lazily converted to and from the underlying binary representations and it also supports & registers itself for Hadoop's <code>WritableComparator</code> mechanism.</p>
-<h2 id="quads">Quads</h2>
+<h2 id="quads">Quads<a class="headerlink" href="#quads" title="Permanent link">¶</a></h2>
<p>Similarly the <code>Writable</code> type for quads is again simply called <code>QuadWritable</code> and it implements the <code>WritableComparable</code> interface making it usable as both a key and/or value. As per the other primitives standard Hadoop conventions of a <code>get()</code> and <code>set()</code> method are provided to get/set the value as a Jena <code>Quad</code>. Unlike the <code>NodeWritable</code> this class does not support conveying <code>null</code> values.</p>
<p>Like the other primitives it is lazily converted to and from the underlying binary representations and it also supports & registers itself for Hadoop's <code>WritableComparator</code> mechanism.</p>
-<h2 id="arbitrary-sized-tuples">Arbitrary sized tuples</h2>
+<h2 id="arbitrary-sized-tuples">Arbitrary sized tuples<a class="headerlink" href="#arbitrary-sized-tuples" title="Permanent link">¶</a></h2>
<p>In some cases you may have data that is RDF like but not itself RDF or that is a mix of triples and quads in which case you may wish to use the <code>NodeTupleWritable</code>. This is used to represent an arbitrarily sized tuple consisting of zero or more <code>Node</code> instances, there is no restriction on the number of nodes per tuple and no requirement that tuple data be uniform in size.</p>
<p>Like the other primitives it implements <code>WritableComparable</code> so can be used as a key and/or value. However this primitive does not support binary comparisons meaning it may not perform as well as using the other primitives.</p>
<p>In this case the <code>get()</code> and <code>set()</code> methods get/set a <code>Tuple<Node></code> instance which is a convenience container class provided by ARQ. Currently the implementation does not support lazy conversion so the full <code>Tuple<Node></code> is reconstructed as soon as an <code>NodeTupleWritable</code> instance is deserialised.</p>
Modified: websites/staging/jena/trunk/content/documentation/hadoop/demo.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/hadoop/demo.html (original)
+++ websites/staging/jena/trunk/content/documentation/hadoop/demo.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>
@@ -144,7 +144,18 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Apache Jena Elephas - RDF Stats Demo</h1>
- <p>The RDF Stats Demo is a pre-built application available as a ready to run Hadoop Job JAR with all dependencies embedded within it. The demo app uses the other libraries to allow calculating a number of basic statistics over any RDF data supported by Elephas.</p>
+ <style type="text/css">
+/* The following code is added by mdx_elementid.py
+ It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+ visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<p>The RDF Stats Demo is a pre-built application available as a ready to run Hadoop Job JAR with all dependencies embedded within it. The demo app uses the other libraries to allow calculating a number of basic statistics over any RDF data supported by Elephas.</p>
<p>To use it you will first need to build it from source or download the relevant Maven artefact:</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.jena<span class="nt"></groupId></span>
@@ -156,9 +167,9 @@
<p>Where <code>x.y.z</code> is the desired version.</p>
-<h1 id="pre-requisites">Pre-requisites</h1>
+<h1 id="pre-requisites">Pre-requisites<a class="headerlink" href="#pre-requisites" title="Permanent link">¶</a></h1>
<p>In order to run this demo you will need to have a Hadoop 2.x cluster available, for simple experimentation purposes a <a href="http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/SingleCluster.html">single node cluster</a> will be sufficient.</p>
-<h1 id="running">Running</h1>
+<h1 id="running">Running<a class="headerlink" href="#running" title="Permanent link">¶</a></h1>
<p>Assuming your cluster is started and running and the <code>hadoop</code> command is available on your path you can run the application without any arguments to see help:</p>
<div class="codehilite"><pre><span class="o">></span> <span class="n">hadoop</span> <span class="n">jar</span> <span class="n">jena</span><span class="o">-</span><span class="n">elephas</span><span class="o">-</span><span class="n">stats</span><span class="o">-</span><span class="n">VERSION</span><span class="o">-</span><span class="n">hadoop</span><span class="o">-</span><span class="n">job</span><span class="p">.</span><span class="n">jar</span> <span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">jena</span><span class="p">.</span><span class="n">hadoop</span><span class="p">.</span><span class="n">rdf</span><span class="p">.</span><span class="n">stats</span><span class="p">.</span><span class="n">RdfStats</span>
<span class="n">NAME</span>
@@ -223,11 +234,11 @@
<p>This calculates the node counts for the input data found in <code>/example/input</code> placing the generated counts in <code>/example/output</code></p>
-<h2 id="specifying-inputs-and-outputs">Specifying Inputs and Outputs</h2>
+<h2 id="specifying-inputs-and-outputs">Specifying Inputs and Outputs<a class="headerlink" href="#specifying-inputs-and-outputs" title="Permanent link">¶</a></h2>
<p>Inputs are specified simply by providing one or more paths to the data you wish to analyse. You can provide directory paths in which case all files within the directory will be processed.</p>
<p>To specify the output location use the <code>-o</code> or <code>--output</code> option followed by the desired output path.</p>
<p>By default the demo application assumes a mixture of quads and triples data, if you know your data is only in triples/quads then you can use the <code>--input-type</code> argument followed by <code>triples</code> or <code>quads</code> to indicate the type of your data. Not doing this can skew some statistics as the default is to assume mixed data and so all triples are upgraded into quads when calculating the statistics.</p>
-<h2 id="available-statistics">Available Statistics</h2>
+<h2 id="available-statistics">Available Statistics<a class="headerlink" href="#available-statistics" title="Permanent link">¶</a></h2>
<p>The following statistics are available and are activated by the relevant command line option:</p>
<table>
<tr><th>Command Line Option</th><th>Statistic</th><th>Description & Notes</th></tr>
Modified: websites/staging/jena/trunk/content/documentation/hadoop/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/hadoop/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/hadoop/index.html Sun Jul 26 10:50:18 2015
@@ -83,8 +83,8 @@
<li><a href="/documentation/tdb/index.html">TDB</a></li>
<li><a href="/documentation/sdb/index.html">SDB</a></li>
<li><a href="/documentation/jdbc/index.html">SPARQL over JDBC</a></li>
- <li><a href="/documentation/security/index.html">Security</a></li>
<li><a href="/documentation/fuseki2/index.html">Fuseki</a></li>
+ <li><a href="/documentation/permissions/index.html">Permissions</a></li>
<li><a href="/documentation/assembler/index.html">Assembler</a></li>
<li><a href="/documentation/ontology/">Ontology API</a></li>
<li><a href="/documentation/inference/index.html">Inference API</a></li>