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 [1/10] - in /websites/staging/jena/trunk/content: ./
about_jena/ documentation/ documentation/assembler/ documentation/csv/
documentation/extras/ documentation/extras/querybuilder/
documentation/fuseki2/ documentation/hadoop/ docume...
Author: buildbot
Date: Sun Jul 26 10:50:18 2015
New Revision: 959629
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/about_jena/about.html
websites/staging/jena/trunk/content/about_jena/architecture.html
websites/staging/jena/trunk/content/about_jena/contributions.html
websites/staging/jena/trunk/content/about_jena/index.html
websites/staging/jena/trunk/content/about_jena/roadmap.html
websites/staging/jena/trunk/content/about_jena/team.html
websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html
websites/staging/jena/trunk/content/documentation/assembler/index.html
websites/staging/jena/trunk/content/documentation/assembler/inside-assemblers.html
websites/staging/jena/trunk/content/documentation/csv/design.html
websites/staging/jena/trunk/content/documentation/csv/get_started.html
websites/staging/jena/trunk/content/documentation/csv/implementation.html
websites/staging/jena/trunk/content/documentation/csv/index.html
websites/staging/jena/trunk/content/documentation/extras/index.html
websites/staging/jena/trunk/content/documentation/extras/querybuilder/index.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-data-services.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-java.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-layout.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-logging.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-quick-start.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-run.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-security.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-server-protocol.html
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-stats.html
websites/staging/jena/trunk/content/documentation/fuseki2/index.html
websites/staging/jena/trunk/content/documentation/fuseki2/rdf-sparql-standards.html
websites/staging/jena/trunk/content/documentation/fuseki2/soh.html
websites/staging/jena/trunk/content/documentation/hadoop/artifacts.html
websites/staging/jena/trunk/content/documentation/hadoop/common.html
websites/staging/jena/trunk/content/documentation/hadoop/demo.html
websites/staging/jena/trunk/content/documentation/hadoop/index.html
websites/staging/jena/trunk/content/documentation/hadoop/io.html
websites/staging/jena/trunk/content/documentation/hadoop/mapred.html
websites/staging/jena/trunk/content/documentation/index.html
websites/staging/jena/trunk/content/documentation/inference/index.html
websites/staging/jena/trunk/content/documentation/io/arp.html
websites/staging/jena/trunk/content/documentation/io/arp_sax.html
websites/staging/jena/trunk/content/documentation/io/arp_standalone.html
websites/staging/jena/trunk/content/documentation/io/index.html
websites/staging/jena/trunk/content/documentation/io/rdf-input.html
websites/staging/jena/trunk/content/documentation/io/rdf-output.html
websites/staging/jena/trunk/content/documentation/io/rdfxml_howto.html
websites/staging/jena/trunk/content/documentation/io/streaming-io.html
websites/staging/jena/trunk/content/documentation/javadoc/elephas/index.html
websites/staging/jena/trunk/content/documentation/javadoc/extras/index.html
websites/staging/jena/trunk/content/documentation/javadoc/index.html
websites/staging/jena/trunk/content/documentation/jdbc/artifacts.html
websites/staging/jena/trunk/content/documentation/jdbc/custom_driver.html
websites/staging/jena/trunk/content/documentation/jdbc/drivers.html
websites/staging/jena/trunk/content/documentation/jdbc/index.html
websites/staging/jena/trunk/content/documentation/larq/index.html
websites/staging/jena/trunk/content/documentation/migrate_jena2_jena3.html
websites/staging/jena/trunk/content/documentation/notes/concurrency-howto.html
websites/staging/jena/trunk/content/documentation/notes/event-handler-howto.html
websites/staging/jena/trunk/content/documentation/notes/file-manager.html
websites/staging/jena/trunk/content/documentation/notes/index.html
websites/staging/jena/trunk/content/documentation/notes/iri.html
websites/staging/jena/trunk/content/documentation/notes/jena-internals.html
websites/staging/jena/trunk/content/documentation/notes/model-factory.html
websites/staging/jena/trunk/content/documentation/notes/rdf-frames.html
websites/staging/jena/trunk/content/documentation/notes/reification.html
websites/staging/jena/trunk/content/documentation/notes/reification_previous.html
websites/staging/jena/trunk/content/documentation/notes/sse.html
websites/staging/jena/trunk/content/documentation/notes/typed-literals.html
websites/staging/jena/trunk/content/documentation/ontology/index.html
websites/staging/jena/trunk/content/documentation/ontology/toc-test.html
websites/staging/jena/trunk/content/documentation/query/algebra.html
websites/staging/jena/trunk/content/documentation/query/app_api.html
websites/staging/jena/trunk/content/documentation/query/architecture.html
websites/staging/jena/trunk/content/documentation/query/arq-query-eval.html
websites/staging/jena/trunk/content/documentation/query/assignment.html
websites/staging/jena/trunk/content/documentation/query/cmds.html
websites/staging/jena/trunk/content/documentation/query/custom_aggregates.html
websites/staging/jena/trunk/content/documentation/query/download.html
websites/staging/jena/trunk/content/documentation/query/explain.html
websites/staging/jena/trunk/content/documentation/query/extension.html
websites/staging/jena/trunk/content/documentation/query/faq.html
websites/staging/jena/trunk/content/documentation/query/function_forms.html
websites/staging/jena/trunk/content/documentation/query/group-by.html
websites/staging/jena/trunk/content/documentation/query/http-auth.html
websites/staging/jena/trunk/content/documentation/query/index.html
websites/staging/jena/trunk/content/documentation/query/java-uri.html
websites/staging/jena/trunk/content/documentation/query/library-function.html
websites/staging/jena/trunk/content/documentation/query/library-propfunc.html
websites/staging/jena/trunk/content/documentation/query/logging.html
websites/staging/jena/trunk/content/documentation/query/manipulating_sparql_using_arq.html
websites/staging/jena/trunk/content/documentation/query/manipulating_sparql_using_arq_pt.html
websites/staging/jena/trunk/content/documentation/query/negation.html
websites/staging/jena/trunk/content/documentation/query/parameterized-sparql-strings.html
websites/staging/jena/trunk/content/documentation/query/programmatic.html
websites/staging/jena/trunk/content/documentation/query/property_paths.html
websites/staging/jena/trunk/content/documentation/query/rdf_lists.html
websites/staging/jena/trunk/content/documentation/query/select_expr.html
websites/staging/jena/trunk/content/documentation/query/service.html
websites/staging/jena/trunk/content/documentation/query/sparql-remote.html
websites/staging/jena/trunk/content/documentation/query/spatial-query.html
websites/staging/jena/trunk/content/documentation/query/sub-select.html
websites/staging/jena/trunk/content/documentation/query/support.html
websites/staging/jena/trunk/content/documentation/query/support_request.html
websites/staging/jena/trunk/content/documentation/query/text-query.html
websites/staging/jena/trunk/content/documentation/query/update.html
websites/staging/jena/trunk/content/documentation/query/writing_functions.html
websites/staging/jena/trunk/content/documentation/query/writing_propfuncs.html
websites/staging/jena/trunk/content/documentation/rdf/index.html
websites/staging/jena/trunk/content/documentation/sdb/commands.html
websites/staging/jena/trunk/content/documentation/sdb/configuration.html
websites/staging/jena/trunk/content/documentation/sdb/database_layouts.html
websites/staging/jena/trunk/content/documentation/sdb/databases_supported.html
websites/staging/jena/trunk/content/documentation/sdb/dataset_description.html
websites/staging/jena/trunk/content/documentation/sdb/db_notes.html
websites/staging/jena/trunk/content/documentation/sdb/faq.html
websites/staging/jena/trunk/content/documentation/sdb/fuseki_integration.html
websites/staging/jena/trunk/content/documentation/sdb/index.html
websites/staging/jena/trunk/content/documentation/sdb/installation.html
websites/staging/jena/trunk/content/documentation/sdb/javaapi.html
websites/staging/jena/trunk/content/documentation/sdb/loading_data.html
websites/staging/jena/trunk/content/documentation/sdb/loading_performance.html
websites/staging/jena/trunk/content/documentation/sdb/query_performance.html
websites/staging/jena/trunk/content/documentation/sdb/quickstart.html
websites/staging/jena/trunk/content/documentation/sdb/store_description.html
websites/staging/jena/trunk/content/documentation/security/assembler.html
websites/staging/jena/trunk/content/documentation/security/evaluator.html
websites/staging/jena/trunk/content/documentation/security/example.html
websites/staging/jena/trunk/content/documentation/security/index.html
websites/staging/jena/trunk/content/documentation/serving_data/index.html
websites/staging/jena/trunk/content/documentation/serving_data/soh.html
websites/staging/jena/trunk/content/documentation/tdb/architecture.html
websites/staging/jena/trunk/content/documentation/tdb/assembler.html
websites/staging/jena/trunk/content/documentation/tdb/commands.html
websites/staging/jena/trunk/content/documentation/tdb/configuration.html
websites/staging/jena/trunk/content/documentation/tdb/datasets.html
websites/staging/jena/trunk/content/documentation/tdb/dynamic_datasets.html
websites/staging/jena/trunk/content/documentation/tdb/faqs.html
websites/staging/jena/trunk/content/documentation/tdb/index.html
websites/staging/jena/trunk/content/documentation/tdb/java_api.html
websites/staging/jena/trunk/content/documentation/tdb/optimizer.html
websites/staging/jena/trunk/content/documentation/tdb/quadfilter.html
websites/staging/jena/trunk/content/documentation/tdb/requirements.html
websites/staging/jena/trunk/content/documentation/tdb/store-parameters.html
websites/staging/jena/trunk/content/documentation/tdb/tdb_system.html
websites/staging/jena/trunk/content/documentation/tdb/tdb_transactions.html
websites/staging/jena/trunk/content/documentation/tdb/value_canonicalization.html
websites/staging/jena/trunk/content/documentation/tools/eyeball-getting-started.html
websites/staging/jena/trunk/content/documentation/tools/eyeball-guide.html
websites/staging/jena/trunk/content/documentation/tools/eyeball-manual.html
websites/staging/jena/trunk/content/documentation/tools/index.html
websites/staging/jena/trunk/content/documentation/tools/schemagen-maven.html
websites/staging/jena/trunk/content/documentation/tools/schemagen.html
websites/staging/jena/trunk/content/download/index.html
websites/staging/jena/trunk/content/download/maven.html
websites/staging/jena/trunk/content/download/osgi.html
websites/staging/jena/trunk/content/getting_involved/index.html
websites/staging/jena/trunk/content/getting_involved/reviewing_contributions.html
websites/staging/jena/trunk/content/getting_started/fuseki.html
websites/staging/jena/trunk/content/getting_started/index.html
websites/staging/jena/trunk/content/getting_started/rdf_api.html
websites/staging/jena/trunk/content/getting_started/sparql.html
websites/staging/jena/trunk/content/getting_started/tell_me_how.html
websites/staging/jena/trunk/content/help_and_support/bugs_and_suggestions.html
websites/staging/jena/trunk/content/help_and_support/faq.html
websites/staging/jena/trunk/content/help_and_support/index.html
websites/staging/jena/trunk/content/index.html
websites/staging/jena/trunk/content/tutorials/index.html
websites/staging/jena/trunk/content/tutorials/rdf_api.html
websites/staging/jena/trunk/content/tutorials/rdf_api_pt.html
websites/staging/jena/trunk/content/tutorials/sparql.html
websites/staging/jena/trunk/content/tutorials/sparql_basic_patterns.html
websites/staging/jena/trunk/content/tutorials/sparql_basic_patterns_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_data.html
websites/staging/jena/trunk/content/tutorials/sparql_data_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_datasets.html
websites/staging/jena/trunk/content/tutorials/sparql_datasets_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_filters.html
websites/staging/jena/trunk/content/tutorials/sparql_filters_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_optionals.html
websites/staging/jena/trunk/content/tutorials/sparql_optionals_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_page.html
websites/staging/jena/trunk/content/tutorials/sparql_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_query1.html
websites/staging/jena/trunk/content/tutorials/sparql_query1_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_results.html
websites/staging/jena/trunk/content/tutorials/sparql_results_pt.html
websites/staging/jena/trunk/content/tutorials/sparql_union.html
websites/staging/jena/trunk/content/tutorials/sparql_union_pt.html
websites/staging/jena/trunk/content/tutorials/using_jena_with_eclipse.html
websites/staging/jena/trunk/content/tutorials/using_jena_with_eclipse_pt.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jul 26 10:50:18 2015
@@ -1 +1 @@
-1691850
+1692709
Modified: websites/staging/jena/trunk/content/about_jena/about.html
==============================================================================
--- websites/staging/jena/trunk/content/about_jena/about.html (original)
+++ websites/staging/jena/trunk/content/about_jena/about.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">What is Jena?</h1>
- <p>Jena is a Java framework for building Semantic Web applications. It provides a
+ <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>Jena is a Java framework for building Semantic Web applications. It provides a
extensive Java libraries for helping developers develop code that
handles RDF, RDFS, RDFa, OWL and SPARQL in line with
published <a href="http://www.w3.org/2001/sw/">W3C recommendations</a>.
Jena includes a rule-based inference engine
to perform reasoning based on OWL and RDFS ontologies, and a variety of storage
strategies to store RDF <em>triples</em> in memory or on disk.</p>
-<h3 id="history">History</h3>
+<h3 id="history">History<a class="headerlink" href="#history" title="Permanent link">¶</a></h3>
<p>Jena was originally developed by researchers in <a href="http://www.hpl.hp.com">HP Labs</a>,
starting in Bristol, UK, in 2000. Jena has always been an open-source project,
and has been extensively used in a wide variety of semantic web applications and
@@ -160,10 +171,10 @@ support of development of Jena, though r
The project team successfully applied to have Jena adopted by the Apache
Software Foundation
in November 2010 (see the <a href="http://mail-archives.apache.org/mod_mbox/incubator-general/201011.mbox/%3C4CEC31E4.9080401@apache.org%3E">vote result</a>).</p>
-<h3 id="current-status">Current status</h3>
+<h3 id="current-status">Current status<a class="headerlink" href="#current-status" title="Permanent link">¶</a></h3>
<p>Jena entered incubation with the Apache in November 2010, and graduated as a top-level
project in April 2012.</p>
-<h3 id="thanks">Thanks</h3>
+<h3 id="thanks">Thanks<a class="headerlink" href="#thanks" title="Permanent link">¶</a></h3>
<p>YourKit is kindly supporting open source projects with its full-featured Java Profiler.
YourKit, LLC is the creator of innovative and intelligent tools for profiling
Java and .NET applications. Take a look at YourKit's leading software products:
Modified: websites/staging/jena/trunk/content/about_jena/architecture.html
==============================================================================
--- websites/staging/jena/trunk/content/about_jena/architecture.html (original)
+++ websites/staging/jena/trunk/content/about_jena/architecture.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">Jena architecture overview</h1>
- <p>There's quite a lot of code inside Jena, and it can be daunting for new Jena
+ <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>There's quite a lot of code inside Jena, and it can be daunting for new Jena
users to find their way around. On this page we'll summarise the
key features and interfaces in Jena, as a general overview and guide to the
more detailed documentation.</p>
Modified: websites/staging/jena/trunk/content/about_jena/contributions.html
==============================================================================
--- websites/staging/jena/trunk/content/about_jena/contributions.html (original)
+++ websites/staging/jena/trunk/content/about_jena/contributions.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">Jena-related projects and tools</h1>
- <p>This page lists various projects and tools related to Jena - classes, packages,
+ <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>This page lists various projects and tools related to Jena - classes, packages,
libraries, applications, or ontologies that enhance Jena or are
built on top of it. These projects are not part of the Jena project itself, but
may be useful to Jena users.</p>
@@ -152,8 +163,8 @@ may be useful to Jena users.</p>
endorsement of the mentioned projects by the Jena team.</p>
<p>If you wish your contribution to appear on this page, please raise a
Jira issue with the details to be published.</p>
-<h2 id="related-projects">Related projects</h2>
-<table>
+<h2 id="related-projects">Related projects<a class="headerlink" href="#related-projects" title="Permanent link">¶</a></h2>
+<table class="table">
<thead>
<tr>
<th>Name</th>
Modified: websites/staging/jena/trunk/content/about_jena/index.html
==============================================================================
--- websites/staging/jena/trunk/content/about_jena/index.html (original)
+++ websites/staging/jena/trunk/content/about_jena/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">Welcome to Apache Jena</h1>
- <!-- This page will not normally be seen. The javascript nav should ensure that the index.mdtext in the
+ <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>
+<!-- This page will not normally be seen. The javascript nav should ensure that the index.mdtext in the
root directory will be seen instead of this one. Nevertheless, for safety this page should be a copy
of /index.mdtext -->
@@ -165,7 +176,7 @@ of protocols, including SPARQL</li>
</ul>
<p>In April 2012, Jena graduated from the Apache incubator process and
was approved as a top-level Apache project.</p>
-<h2 id="quick-shortcuts">Quick shortcuts</h2>
+<h2 id="quick-shortcuts">Quick shortcuts<a class="headerlink" href="#quick-shortcuts" title="Permanent link">¶</a></h2>
<p>I would like to ...</p>
<ul>
<li>... <a href="/download/index.cgi">download Jena components</a></li>
Modified: websites/staging/jena/trunk/content/about_jena/roadmap.html
==============================================================================
--- websites/staging/jena/trunk/content/about_jena/roadmap.html (original)
+++ websites/staging/jena/trunk/content/about_jena/roadmap.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/about_jena/team.html
==============================================================================
--- websites/staging/jena/trunk/content/about_jena/team.html (original)
+++ websites/staging/jena/trunk/content/about_jena/team.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 project team members</h1>
- <p>In first name alphabetical order:</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>In first name alphabetical order:</p>
<ul>
<li>Andy Seaborne (andy) <strong>CP VP</strong></li>
<li>Chris Dollin (chrisdollin) <strong>CP</strong></li>
@@ -165,7 +176,7 @@
<li>Leo Simons</li>
<li>Ross Gardler</li>
</ul>
-<h3 id="key">Key</h3>
+<h3 id="key">Key<a class="headerlink" href="#key" title="Permanent link">¶</a></h3>
<dl>
<dt>C</dt>
<dd>a committer</dd>
Modified: websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.html (original)
+++ websites/staging/jena/trunk/content/documentation/assembler/assembler-howto.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">Jena Assembler howto</h1>
- <h2 id="introduction">Introduction</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="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">¶</a></h2>
<p>This document describes the vocabulary and effect of the built-in
Jena assembler descriptions for constructing models (and other
things). A <a href="inside-assemblers.html">companion document</a> describes
@@ -165,7 +176,7 @@ extracted from the <code>ja-vocabulary</
properties" (as per Jena's <code>listDeclaredProperties</code> method) of the
class. Only the most specialised super-classes and range classes are
shown, so (for example) <code>rdf:Resource</code> typically won't appear.</p>
-<h3 id="overview">Overview</h3>
+<h3 id="overview">Overview<a class="headerlink" href="#overview" title="Permanent link">¶</a></h3>
<p>An Assembler specification is a Resource in some RDF Model. The
properties of that Resource describe what kind of object is to be
assembled and what its components are: for example, an InfModel is
@@ -209,7 +220,7 @@ environment):</p>
<code>eg:opening-example</code> in our example. <code>general</code> knows how to create
all the kinds of objects - not just Models - that we describe in
the next sections.</p>
-<h2 id="specifications-common-to-all-models">Specifications common to all models</h2>
+<h2 id="specifications-common-to-all-models">Specifications common to all models<a class="headerlink" href="#specifications-common-to-all-models" title="Permanent link">¶</a></h2>
<p>Assembler specifications can describe many kinds of models: memory,
inference, ontology, and file-backed. All of these model
specifications share a set of base properties for attaching
@@ -266,7 +277,7 @@ has any prefix mappings, then they are a
constructed and used to set the prefixes of the model. See
<a href="#prefix-mappings">PrefixMapping</a> for the description of
Content specifications.</p>
-<h3 id="content-specification">Content specification</h3>
+<h3 id="content-specification">Content specification<a class="headerlink" href="#content-specification" title="Permanent link">¶</a></h3>
<p>A Content specification describes content that can be used to fill
models. Content can be external (files and URLs) or literal
(strings in the specification) or quotations (referring to RDF
@@ -323,7 +334,7 @@ interpretation.</p>
resources. The subgraphs rooted at those resources (using the
algorithm from <code>ResourceUtils.reachableClosure()</code>) are added to the
content.</p>
-<h3 id="inference-models-and-reasoners">Inference models and reasoners</h3>
+<h3 id="inference-models-and-reasoners">Inference models and reasoners<a class="headerlink" href="#inference-models-and-reasoners" title="Permanent link">¶</a></h3>
<p>Inference models are specified by supplying a description of the
reasoner that is used by the model and (optionally) a base model to
reason over. For example:</p>
@@ -414,7 +425,7 @@ schema is used.</p>
<p>If the Reasoner is a GenericRuleReasoner, it may have any of the
RuleSet properties <code>ja:rules</code>, <code>ja:rulesFrom</code>, or <code>ja:rule</code>. The
rules of the implied <code>RuleSet</code> are added to the <code>Reasoner</code>.</p>
-<h4 id="reasonerfactory">ReasonerFactory</h4>
+<h4 id="reasonerfactory">ReasonerFactory<a class="headerlink" href="#reasonerfactory" title="Permanent link">¶</a></h4>
<p>A ReasonerFactory can be specified by URL or by class name (but not
both).</p>
<div class="codehilite"><pre><span class="n">ja</span><span class="o">:</span><span class="n">ReasonerFactory</span> <span class="n">a</span> <span class="n">rdfs</span><span class="o">:</span><span class="n">Class</span> <span class="o">;</span>
@@ -451,7 +462,7 @@ supply the <code>ReasonerFactory</code>
instance of that class is constructed. Jena's reasoner factories
come equipped with this method; for other factories, see the
documentation.</p>
-<h4 id="rulesets">Rulesets</h4>
+<h4 id="rulesets">Rulesets<a class="headerlink" href="#rulesets" title="Permanent link">¶</a></h4>
<p>A <code>RuleSet</code> specification allows rules (for ReasonerFactories) to
be specified inline, elsewhere in the specification model, or in an
external resource.</p>
@@ -472,7 +483,7 @@ can be loaded as Jena rules. All those r
resource which identifies another <code>RuleSet</code> in the specification
model. All those rules from that <code>RuleSet</code> are added to this
<code>RuleSet</code>.</p>
-<h3 id="ontology-models">Ontology models</h3>
+<h3 id="ontology-models">Ontology models<a class="headerlink" href="#ontology-models" title="Permanent link">¶</a></h3>
<p>Ontology models can be specified in several ways. The simplest is
to use the name of an OntModelSpec from the Java OntModelSpec
class:</p>
@@ -576,7 +587,7 @@ those of <code>OntModelSpec.OWL_MEM_RDFS
OntModelSpec resource is in the JA namespace, and its local name is
the same as that of an OntModelSpec constant, then that constant is
used as the default value.</p>
-<h3 id="document-managers">Document managers</h3>
+<h3 id="document-managers">Document managers<a class="headerlink" href="#document-managers" title="Permanent link">¶</a></h3>
<p>An <code>OntDocumentManager</code> can be specified by a <code>ja:DocumentManager</code>
specification which describes the <code>OntDocumentManager</code>'s file
manager and policy settings.</p>
@@ -654,7 +665,7 @@ object initialising that file manager.</
describing the location mapping, as described in the FileManager
documentation. (Note that the vocabulary for those items is in a
different namespace than the JA properties and classes.)</p>
-<h3 id="union-models">Union models</h3>
+<h3 id="union-models">Union models<a class="headerlink" href="#union-models" title="Permanent link">¶</a></h3>
<p>Union models can be constructed from any number of sub-models and a
single <em>root</em> model. The root model is the one written to when the
union model is updated; the sub-models are untouched.</p>
@@ -682,7 +693,7 @@ as its root.</p>
remaining sub-models of the union. The order of the sub-models in
the union is <em>undefined</em> (which is why there's a special rootModel
property).</p>
-<h3 id="prefix-mappings">Prefix mappings</h3>
+<h3 id="prefix-mappings">Prefix mappings<a class="headerlink" href="#prefix-mappings" title="Permanent link">¶</a></h3>
<p>The PrefixMappings of a model may be set from PrefixMapping
specifications.</p>
<div class="codehilite"><pre><span class="n">ja</span><span class="o">:</span><span class="n">PrefixMapping</span> <span class="n">a</span> <span class="n">rdfs</span><span class="o">:</span><span class="n">Class</span> <span class="o">;</span>
@@ -712,10 +723,10 @@ content of other specified PrefixMapping
<p>The <code>ja:prefix</code> and <code>ja:namespace</code> properties allow the
construction of a single element of a prefix mapping by specifying
the prefix and namespace of the mapping.</p>
-<h3 id="other-assembler-directives">Other Assembler directives</h3>
+<h3 id="other-assembler-directives">Other Assembler directives<a class="headerlink" href="#other-assembler-directives" title="Permanent link">¶</a></h3>
<p>There are two more <code>Assembler</code> directives that can be used in an
Assembler specification: the <em>assembler</em> and <em>imports</em> directives.</p>
-<h4 id="assembler">Assembler</h4>
+<h4 id="assembler">Assembler<a class="headerlink" href="#assembler" title="Permanent link">¶</a></h4>
<p>A specification may contain statements of the form:</p>
<div class="codehilite"><pre><span class="n">someResource</span> <span class="n">ja</span><span class="p">:</span><span class="n">assembler</span> "<span class="n">some</span><span class="p">.</span><span class="n">Assembler</span><span class="p">.</span><span class="n">class</span><span class="p">.</span><span class="n">name</span>"
</pre></div>
@@ -734,7 +745,7 @@ details.</p>
<p>will cause the named class to be loaded (but not treated as
assemblers).</p>
-<h4 id="imports">Imports</h4>
+<h4 id="imports">Imports<a class="headerlink" href="#imports" title="Permanent link">¶</a></h4>
<p>If a specification contains statements of the form:</p>
<div class="codehilite"><pre><span class="n">anyResource</span> <span class="n">owl</span><span class="p">:</span><span class="n">imports</span> <span class="n">someURL</span>
</pre></div>
@@ -748,7 +759,7 @@ assemblers).</p>
<p>then the specification is regarded as also containing the contents
of the RDF at <code>someURL</code>. That RDF may in turn contain <code>imports</code>
referring to other RDF.</p>
-<h2 id="limited-rdfs-inference">Limited RDFS inference</h2>
+<h2 id="limited-rdfs-inference">Limited RDFS inference<a class="headerlink" href="#limited-rdfs-inference" title="Permanent link">¶</a></h2>
<p>The Assembler engine uses limited RDFS inference to complete the
model it is given, so that the spec-writer does not need to write
excessive and redundant RDF. (It does not use the usual Jena
Modified: websites/staging/jena/trunk/content/documentation/assembler/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/assembler/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/assembler/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,24 +144,35 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Jena assembler quickstart</h1>
- <p>Jena's assembler provides a means of constructing Jena models
+ <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>Jena's assembler provides a means of constructing Jena models
according to a recipe, where that recipe is itself stated in
RDF. This is the Assembler quickstart page. For more detailed
information, see the <a href="assembler-howto.html">Assembler howto</a>
or <a href="inside-assemblers.html">Inside assemblers</a>.</p>
-<h2 id="what-is-an-assembler-specification">What is an Assembler specification?</h2>
+<h2 id="what-is-an-assembler-specification">What is an Assembler specification?<a class="headerlink" href="#what-is-an-assembler-specification" title="Permanent link">¶</a></h2>
<p>An Assembler <em>specification</em> is an RDF description of how to
construct a model and its associated resources, such as reasoners,
prefix mappings, and initial content. The Assembler vocabulary is
given in the <a href="assembler.ttl">Assembler schema</a>,
and we'll use the prefix <code>ja</code> for its identifiers.</p>
-<h2 id="what-is-an-assembler">What is an Assembler?</h2>
+<h2 id="what-is-an-assembler">What is an Assembler?<a class="headerlink" href="#what-is-an-assembler" title="Permanent link">¶</a></h2>
<p>An <em>Assembler</em> is an object that implements the <code>Assembler</code>
interface and can construct objects (typically models) from
Assembler specifications. The constant <code>Assembler.general</code> is an
Assembler that knows how to construct some general patterns
of model specification.</p>
-<h2 id="how-can-i-make-a-model-according-to-a-specification">How can I make a model according to a specification?</h2>
+<h2 id="how-can-i-make-a-model-according-to-a-specification">How can I make a model according to a specification?<a class="headerlink" href="#how-can-i-make-a-model-according-to-a-specification" title="Permanent link">¶</a></h2>
<p>Suppose the Model <code>M</code> contains an Assembler specification whose
<em>root</em> - the Resource describing the whole Model to construct is
<code>R</code> (so <code>R.getModel() == M)</code>. Invoke:</p>
@@ -173,15 +184,15 @@ of model specification.</p>
<code>Assembler</code> interface, the special Assembler <code>general</code>, and the
details of specific Assemblers, are deferred to the
<a href="assembler-howto.html">Assembler howto</a>.</p>
-<h2 id="how-can-i-specify">How can I specify ...</h2>
+<h2 id="how-can-i-specify">How can I specify ...<a class="headerlink" href="#how-can-i-specify" title="Permanent link">¶</a></h2>
<p>In the remaining sections, the object we want to describe is given
the root resource <code>my:root</code>.</p>
-<h3 id="a-memory-model">... a memory model?</h3>
+<h3 id="a-memory-model">... a memory model?<a class="headerlink" href="#a-memory-model" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">root</span> <span class="n">a</span> <span class="n">ja</span><span class="o">:</span><span class="n">MemoryModel</span><span class="o">.</span>
</pre></div>
-<h3 id="an-inference-model">... an inference model?</h3>
+<h3 id="an-inference-model">... an inference model?<a class="headerlink" href="#an-inference-model" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">root</span>
<span class="n">ja</span><span class="o">:</span><span class="n">reasoner</span> <span class="o">[</span><span class="n">ja</span><span class="o">:</span><span class="n">reasonerURL</span> <span class="n">theReasonerURL</span><span class="o">]</span> <span class="o">;</span>
<span class="n">ja</span><span class="o">:</span><span class="n">baseModel</span> <span class="n">theBaseModelResource</span>
@@ -192,7 +203,7 @@ the root resource <code>my:root</code>.<
<p><em>theReasonerURL</em> is one of the reasoner (factory) URLs given in the
inference documentation and code; <em>theBaseModelResource</em> is another
resource in the same document describing the base model.</p>
-<h3 id="some-initialising-content">... some initialising content?</h3>
+<h3 id="some-initialising-content">... some initialising content?<a class="headerlink" href="#some-initialising-content" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">root</span>
<span class="n">ja</span><span class="o">:</span><span class="n">content</span> <span class="o">[</span><span class="n">ja</span><span class="o">:</span><span class="n">externalContent</span> <span class="o"><</span><span class="n">someContentURL</span><span class="o">>]</span>
<span class="o">...</span> <span class="n">rest</span> <span class="n">of</span> <span class="n">model</span> <span class="n">specification</span> <span class="o">...</span>
@@ -201,7 +212,7 @@ resource in the same document describing
<p>The model will be pre-loaded with the contents of <em>someContentURL</em>.</p>
-<h3 id="an-ontology-model">... an ontology model?</h3>
+<h3 id="an-ontology-model">... an ontology model?<a class="headerlink" href="#an-ontology-model" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="n">my</span><span class="o">:</span><span class="n">root</span>
<span class="n">ja</span><span class="o">:</span><span class="n">ontModelSpec</span> <span class="n">ja</span><span class="o">:</span><span class="n">OntModelSpecName</span> <span class="o">;</span>
<span class="n">ja</span><span class="o">:</span><span class="n">baseModel</span> <span class="n">somebaseModel</span>
Modified: websites/staging/jena/trunk/content/documentation/assembler/inside-assemblers.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/assembler/inside-assemblers.html (original)
+++ websites/staging/jena/trunk/content/documentation/assembler/inside-assemblers.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">Inside assemblers</h1>
- <p>This document describes Jena's built-in assembler classes and how
+ <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>This document describes Jena's built-in assembler classes and how
to write and integrate your own assemblers. If you just need a
quick guide to the common model specifications, see the
<a href="index.html">assembler quickstart</a>; if you want mroe details on
writing assembler descriptions, see the
<a href="assembler-howto.html">assembler howto</a>.</p>
-<h2 id="the-assembler-interface">The Assembler interface</h2>
+<h2 id="the-assembler-interface">The Assembler interface<a class="headerlink" href="#the-assembler-interface" title="Permanent link">¶</a></h2>
<p>An <code>Assembler</code> is an object that builds objects (most importantly,
<code>Model</code>s) from RDF descriptions.</p>
<div class="codehilite"><pre><span class="n">public</span> <span class="n">Object</span> <span class="n">open</span><span class="p">(</span> <span class="n">Assembler</span> <span class="n">a</span><span class="p">,</span> <span class="n">Resource</span> <span class="n">root</span><span class="p">,</span> <span class="n">Mode</span> <span class="n">mode</span> <span class="p">);</span>
@@ -176,12 +187,12 @@ descriptions hanging off <code>root</cod
construct those. If the object is to be constructed in some
persistent store, <code>mode</code> defines whether objects can be re-used or
created: see <a href="#modes">modes</a> for more details.</p>
-<h2 id="builtin-assemblers">Builtin assemblers</h2>
+<h2 id="builtin-assemblers">Builtin assemblers<a class="headerlink" href="#builtin-assemblers" title="Permanent link">¶</a></h2>
<p>Jena comes with a collection of built-in assemblers: various
<em>basic assemblers</em> and a composite <em>general assembler</em>. Each of
these assemblers has a constant instance declared as a field of
<code>Assembler</code>.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>Assembler</th>
@@ -197,7 +208,7 @@ these assemblers has a constant instance
</tr>
</tbody>
</table>
-<h2 id="inside-assemblers">Inside Assemblers</h2>
+<h2 id="inside-assemblers">Inside Assemblers<a class="headerlink" href="#inside-assemblers" title="Permanent link">¶</a></h2>
<p><code>Assembler.general</code> is a particular implementation of the
<code>Assembler</code> interface. An <code>Assembler</code> knows how to build the
objects - not just models - described by an Assembler
@@ -259,7 +270,7 @@ user can write specialised <code>Mode</c
other root properties to make their decision.
Note that the Modes only apply to persistent objects, so <em>eg</em>
MemoryModels or PrefixMappings ignore their Mode arguments.</p>
-<h2 id="implementing-your-own-assemblers">Implementing your own assemblers</h2>
+<h2 id="implementing-your-own-assemblers">Implementing your own assemblers<a class="headerlink" href="#implementing-your-own-assemblers" title="Permanent link">¶</a></h2>
<p>(Temporary documentation pasted in from email; will be integrated
and made nice RSN.)</p>
<div class="codehilite"><pre><span class="n">You</span> <span class="n">have</span> <span class="n">to</span> <span class="n">implement</span> <span class="n">the</span> <span class="n">Assembler</span> <span class="n">interface</span><span class="p">,</span> <span class="n">most</span> <span class="n">straightforwardly</span>
@@ -293,13 +304,13 @@ and made nice RSN.)</p>
</pre></div>
-<h2 id="basic-assemblers">basic assemblers</h2>
+<h2 id="basic-assemblers">basic assemblers<a class="headerlink" href="#basic-assemblers" title="Permanent link">¶</a></h2>
<p>There is a family of <em>basic assemblers</em>, each of which knows how to
assemble a specific kind of object so long as they're given an
Assembler that can construct their sub-objects. There are defined
constants in <code>Assembler</code> for (an instance of) each of these basic
assembler classes.</p>
-<table>
+<table class="table">
<thead>
<tr>
<th>produces</th>
@@ -378,7 +389,7 @@ construct objects will use <code>general
<p>In the remaining sections we will discuss the <code>Assembler</code> classes
that return non-Model objects and conclude with a description of
<code>AssemblerGroup</code>.</p>
-<h3 id="basic-assembler-contentassembler">Basic assembler ContentAssembler</h3>
+<h3 id="basic-assembler-contentassembler">Basic assembler ContentAssembler<a class="headerlink" href="#basic-assembler-contentassembler" title="Permanent link">¶</a></h3>
<p>The ContentAssembler constructs Content objects (using the
<code>ja:Content</code> vocabulary) used to supply content to models. A
Content object has the method:</p>
@@ -388,14 +399,14 @@ Content object has the method:</p>
<p>Invoking the <code>fill</code> method adds the represented content to the
model. The supplied ModelAssemblers automatically apply the
<code>Content</code> objects corresponding to <code>ja:content</code> property values.</p>
-<h3 id="basic-assembler-rulesetassembler">Basic assembler RulesetAssembler</h3>
+<h3 id="basic-assembler-rulesetassembler">Basic assembler RulesetAssembler<a class="headerlink" href="#basic-assembler-rulesetassembler" title="Permanent link">¶</a></h3>
<p>A RulesetAssembler generates lists of Jena rules.</p>
-<h3 id="basic-assembler-defaultmodelassembler">Basic assembler DefaultModelAssembler</h3>
+<h3 id="basic-assembler-defaultmodelassembler">Basic assembler DefaultModelAssembler<a class="headerlink" href="#basic-assembler-defaultmodelassembler" title="Permanent link">¶</a></h3>
<p>A "default model" is a model of unspecified type which is
implemented as whatever kind the assembler for <code>ja:DefaultModel</code>
generates. The default for a DefaultModel is to create a
MemoryModel with no special properties.</p>
-<h3 id="assemblergroup">AssemblerGroup</h3>
+<h3 id="assemblergroup">AssemblerGroup<a class="headerlink" href="#assemblergroup" title="Permanent link">¶</a></h3>
<p>The AssemblerGroup class allows a bunch of other Assemblers to be
bundled together and selected by RDF type. AssemblerGroup
implements Assembler and adds the methods:</p>
@@ -413,7 +424,7 @@ particular objects.</p>
<p>The <code>assemblerFor</code> method returns the assembler associated with the
argument type by a previous call of <code>implementWith</code>, or <code>null</code> if
there is no associated assembler.</p>
-<h3 id="loading-assembler-classes">Loading assembler classes</h3>
+<h3 id="loading-assembler-classes">Loading assembler classes<a class="headerlink" href="#loading-assembler-classes" title="Permanent link">¶</a></h3>
<p>AssemblerGroups implement the <code>ja:assembler</code> functionality. The
object of an <code>(type ja:assembler "ClassName")</code> statement is a
string which is taken as the name of an <code>Assembler</code> implementation
Modified: websites/staging/jena/trunk/content/documentation/csv/design.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/csv/design.html (original)
+++ websites/staging/jena/trunk/content/documentation/csv/design.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/csv/get_started.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/csv/get_started.html (original)
+++ websites/staging/jena/trunk/content/documentation/csv/get_started.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">CSV PropertyTable - Get Started</h1>
- <h2 id="using-csv-propertytable-with-apache-maven">Using CSV PropertyTable with Apache Maven</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="using-csv-propertytable-with-apache-maven">Using CSV PropertyTable with Apache Maven<a class="headerlink" href="#using-csv-propertytable-with-apache-maven" title="Permanent link">¶</a></h2>
<p>See <a href="http://jena.apache.org/download/maven.html">"Using Jena with Apache Maven"</a> for full details.</p>
<div class="codehilite"><pre><span class="nt"><dependency></span>
<span class="nt"><groupId></span>org.apache.jena<span class="nt"></groupId></span>
@@ -154,7 +165,7 @@
</pre></div>
-<h2 id="using-csv-propertytable-from-java-through-the-api">Using CSV PropertyTable from Java through the API</h2>
+<h2 id="using-csv-propertytable-from-java-through-the-api">Using CSV PropertyTable from Java through the API<a class="headerlink" href="#using-csv-propertytable-from-java-through-the-api" title="Permanent link">¶</a></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>
<div class="codehilite"><pre><span class="n">import</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">propertytable</span><span class="p">.</span><span class="n">lang</span><span class="p">.</span><span class="n">CSV2RDF</span><span class="p">;</span>
<span class="p">...</span>
@@ -164,7 +175,7 @@
<p>It's a static method call of registration, which needs to be run just one time for an application before using CSV PropertyTable (e.g. during the initialization phase).</p>
<p>Once registered, CSV PropertyTable provides 2 ways for the users to play with (i.e. GraphCSV and RIOT):</p>
-<h3 id="graphcsv">GraphCSV</h3>
+<h3 id="graphcsv">GraphCSV<a class="headerlink" href="#graphcsv" title="Permanent link">¶</a></h3>
<p><a href="https://github.com/apache/jena/tree/master/jena-csv/src/main/java/org/apache/jena/propertytable/graph/GraphCSV.java">GraphCSV</a> wrappers a CSV file as a Graph, which makes a Model for SPARQL query:</p>
<div class="codehilite"><pre><span class="n">Model</span> <span class="n">model</span> <span class="p">=</span> <span class="n">ModelFactory</span><span class="p">.</span><span class="n">createModelForGraph</span><span class="p">(</span><span class="n">new</span> <span class="n">GraphCSV</span><span class="p">(</span>"<span class="n">data</span><span class="p">.</span><span class="n">csv</span>"<span class="p">))</span> <span class="p">;</span>
<span class="n">QueryExecution</span> <span class="n">qExec</span> <span class="p">=</span> <span class="n">QueryExecutionFactory</span><span class="p">.</span><span class="n">create</span><span class="p">(</span><span class="n">query</span><span class="p">,</span> <span class="n">model</span><span class="p">)</span> <span class="p">;</span>
@@ -185,7 +196,7 @@
<p>You can also find the full examples from <a href="https://github.com/apache/jena/tree/master/jena-csv/src/test/java/org/apache/jena/propertytable/graph/GraphCSVTest.java">GraphCSVTest</a>.</p>
<p>In short, for Jena ARQ, a CSV table is actually a Graph (i.e. GraphCSV), without any differences from other types of Graphs when using it from the Jena ARQ API.</p>
-<h3 id="riot">RIOT</h3>
+<h3 id="riot">RIOT<a class="headerlink" href="#riot" title="Permanent link">¶</a></h3>
<p>When LangCSV is registered into RIOT, CSV PropertyTable adds a new RDF syntax of '.csv' with the content type of "text/csv".
You can read ".csv" files into Model following the standard RIOT usages:</p>
<div class="codehilite"><pre><span class="c1">// Usage 1: Direct reading through Model</span>
@@ -199,7 +210,7 @@ You can read ".csv" files into Model fol
<p>For more information, see <a href="http://jena.apache.org/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>
+<h2 id="command-line-tool">Command Line Tool<a class="headerlink" href="#command-line-tool" title="Permanent link">¶</a></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.
The script calls the <code>csv2rdf</code> java program in the <code>riotcmd</code> package in this way:</p>
<div class="codehilite"><pre><span class="n">java</span> <span class="o">-</span><span class="n">cp</span> <span class="p">...</span> <span class="n">riotcmdx</span><span class="p">.</span><span class="n">csv2rdf</span> <span class="n">inputFile</span> <span class="p">...</span>
Modified: websites/staging/jena/trunk/content/documentation/csv/implementation.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/csv/implementation.html (original)
+++ websites/staging/jena/trunk/content/documentation/csv/implementation.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,9 +144,20 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">CSV PropertyTable - Implementation</h1>
- <h2 id="propertytable-implementations">PropertyTable Implementations</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="propertytable-implementations">PropertyTable Implementations<a class="headerlink" href="#propertytable-implementations" title="Permanent link">¶</a></h2>
<p>There're 2 implementations for <code>PropertyTable</code>. The pros and cons are summarised in the following table: </p>
-<table>
+<table class="table">
<thead>
<tr>
<th>PropertyTable Implementation</th>
@@ -181,7 +192,7 @@ Here is an example:</p>
</pre></div>
-<h2 id="stagegenerator-optimization-for-graphpropertytable">StageGenerator Optimization for GraphPropertyTable</h2>
+<h2 id="stagegenerator-optimization-for-graphpropertytable">StageGenerator Optimization for GraphPropertyTable<a class="headerlink" href="#stagegenerator-optimization-for-graphpropertytable" title="Permanent link">¶</a></h2>
<p>Accessing from SPARQL via <code>Graph.find()</code> will work, but it's not ideal. Some optimizations can be done for processing a SPARQL basic graph pattern. More explicitly, in the method of <code>OpExecutor.execute(OpBGP, ...)</code>, when the target for the query is a <code>GraphPropertyTable</code>, it can get a whole <code>Row</code>, or <code>Rows</code>, of the table data and match the pattern with the bindings.</p>
<p>The optimization of querying a whole <code>Row</code> in the PropertyTable are supported now.
The following query pattern can be transformed into a <code>Row</code> querying, without generating triples:</p>
Modified: websites/staging/jena/trunk/content/documentation/csv/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/csv/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/csv/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">CSV PropertyTable</h1>
- <p>This module is about getting CSVs into a form that is amenable to Jena SPARQL processing, and doing so in a way that is not specific to CSV files.
+ <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>This module is about getting CSVs into a form that is amenable to Jena SPARQL processing, and doing so in a way that is not specific to CSV files.
It includes getting the right architecture in place for regular table shaped data, using the core abstraction of PropertyTable.</p>
<p><em>Illustration</em></p>
<p>This module involves the basic mapping of CSV to RDF using a fixed algorithm, including interpreting data as numbers or strings.</p>
@@ -193,7 +204,7 @@ Multiple CSVs files can be multiple grap
<p>What's more, we make some room for future extension through <code>PropertyTable</code>.
The <a href="design.html">architecture</a> is designed to be able to accommodate any table-like data sources, such as relational databases, Microsoft Excel, etc.</p>
-<h2 id="documentation">Documentation</h2>
+<h2 id="documentation">Documentation<a class="headerlink" href="#documentation" title="Permanent link">¶</a></h2>
<ul>
<li><a href="get_started.html">Get Started</a></li>
<li><a href="design.html">Design</a></li>
Modified: websites/staging/jena/trunk/content/documentation/extras/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/extras/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/extras/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,9 +144,20 @@
<div class="col-md-12">
<div id="breadcrumbs"></div>
<h1 class="title">Jena Extras - Extra packages for Jena development.</h1>
- <p>Jena Extra modules are modules that provide utilities and larger packages that make Apache Jena
+ <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>Jena Extra modules are modules that provide utilities and larger packages that make Apache Jena
development or usage easier but that do not fall within the standard Jena framework.</p>
-<h2 id="sub-packages">Sub Packages</h2>
+<h2 id="sub-packages">Sub Packages<a class="headerlink" href="#sub-packages" title="Permanent link">¶</a></h2>
<ul>
<li><a href="querybuilder/index.html">Query Builder</a></li>
</ul>
Modified: websites/staging/jena/trunk/content/documentation/extras/querybuilder/index.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/extras/querybuilder/index.html (original)
+++ websites/staging/jena/trunk/content/documentation/extras/querybuilder/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">Jena Query Builder - A query builder for Jena.</h1>
- <p>Query Builder for Jena. Implementations of Ask, Construct and Select builders that allow
+ <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>Query Builder for Jena. Implementations of Ask, Construct and Select builders that allow
developers to create queries without resorting to StringBuilders or similar solutions.</p>
<p>Each of the builders has a series of methods to define the query. Each method returns the
builder for easy chaining. The example:</p>
@@ -163,7 +174,7 @@ builder for easy chaining. The example
</pre></div>
-<h1 id="template-usage">Template Usage</h1>
+<h1 id="template-usage">Template Usage<a class="headerlink" href="#template-usage" title="Permanent link">¶</a></h1>
<p>In addition to making it easier to build valid queries the QueryBuilder has a clone method.<br />
Using this a developer can create as "Template" query and add to it as necessary.</p>
<p>for example using the above query as the "template" the this code:</p>
@@ -183,7 +194,7 @@ Using this a developer can create as "Te
</pre></div>
-<h1 id="prepared-statement-usage">Prepared Statement Usage</h1>
+<h1 id="prepared-statement-usage">Prepared Statement Usage<a class="headerlink" href="#prepared-statement-usage" title="Permanent link">¶</a></h1>
<p>The query builders have the ability to replace variables with other values. This can be </p>
<div class="codehilite"><pre><span class="n">SelectBuilder</span> <span class="n">sb</span> <span class="p">=</span> <span class="n">new</span> <span class="n">SelectBuilder</span><span class="p">()</span>
<span class="p">.</span><span class="n">addVar</span><span class="p">(</span> "<span class="o">*</span>" <span class="p">)</span>
Modified: websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.html (original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-configuration.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="configuring-fuseki">Configuring 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="configuring-fuseki">Configuring Fuseki<a class="headerlink" href="#configuring-fuseki" title="Permanent link">¶</a></h1>
<p>Configuration consists of defining the data services (data and actions available on the data) together with configuring the server. Explicitly configuring the server is often unnecessary.</p>
<p>The data services configuration can come from:</p>
<ol>
@@ -154,10 +165,10 @@
<li>The command line, if not running as a web application from a .war file.</li>
</ol>
<p><code>FUSEKI_BASE</code> is the location of the <a href="#fuseki-layout.html">Fuseki run area</a>.</p>
-<h2 id="data-service-assembler">Data Service assembler</h2>
+<h2 id="data-service-assembler">Data Service assembler<a class="headerlink" href="#data-service-assembler" title="Permanent link">¶</a></h2>
<p>See <a href="fuseki-data-services.html">Fuseki Data Services</a> for the architecture of data services.</p>
<p>See <a href="fuseki-security.html">Fuseki Security</a> for more information on security.</p>
-<h2 id="fuseki-configuration-file">Fuseki Configuration File</h2>
+<h2 id="fuseki-configuration-file">Fuseki Configuration File<a class="headerlink" href="#fuseki-configuration-file" title="Permanent link">¶</a></h2>
<p>A Fuseki server can be set up using a configuration file. The
command-line arguments for publishing a single dataset are a short
cut that, internally, builds a default configuration based on the
@@ -167,7 +178,7 @@ description, with a number of services,
number of endpoints over a dataset.</p>
<p>The example below is all one file (RDF graph in Turtle syntax)
split to allow for commentary.</p>
-<h3 id="prefix-declarations">Prefix declarations</h3>
+<h3 id="prefix-declarations">Prefix declarations<a class="headerlink" href="#prefix-declarations" title="Permanent link">¶</a></h3>
<p>Some useful prefix declarations:</p>
<div class="codehilite"><pre><span class="p">@</span><span class="n">prefix</span> <span class="n">fuseki</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">jena</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">fuseki</span>#<span class="o">></span> <span class="p">.</span>
<span class="p">@</span><span class="n">prefix</span> <span class="n">rdf</span><span class="p">:</span> <span class="o"><</span><span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">www</span><span class="p">.</span><span class="n">w3</span><span class="p">.</span><span class="n">org</span><span class="o">/</span>1999<span class="o">/</span>02<span class="o">/</span>22<span class="o">-</span><span class="n">rdf</span><span class="o">-</span><span class="n">syntax</span><span class="o">-</span><span class="n">ns</span>#<span class="o">></span> <span class="p">.</span>
@@ -178,12 +189,12 @@ split to allow for commentary.</p>
</pre></div>
-<h3 id="assembler-initialization">Assembler Initialization</h3>
+<h3 id="assembler-initialization">Assembler Initialization<a class="headerlink" href="#assembler-initialization" title="Permanent link">¶</a></h3>
<p>All datasets are described by
<a href="../assembler/index.html">assembler descriptions</a>.
Assemblers provide an extensible way of describing many kinds of
objects. </p>
-<h3 id="defining-the-service-name-and-endpoints-available">Defining the service name and endpoints available</h3>
+<h3 id="defining-the-service-name-and-endpoints-available">Defining the service name and endpoints available<a class="headerlink" href="#defining-the-service-name-and-endpoints-available" title="Permanent link">¶</a></h3>
<p>Each data service assembler defines:</p>
<ul>
<li>The base name</li>
@@ -210,7 +221,7 @@ Store protocol, as well as file upload.<
<p><code><#dataset></code> refers to a dataset description in the same file.</p>
-<h3 id="read-only-service">Read-only service</h3>
+<h3 id="read-only-service">Read-only service<a class="headerlink" href="#read-only-service" title="Permanent link">¶</a></h3>
<p>This example offers only read-only endpoints (SPARQL Query and HTTP GET
SPARQl Graph Store protocol).</p>
<p>This service offers read-only access to a dataset with a single
@@ -224,8 +235,8 @@ graph of data.</p>
</pre></div>
-<h3 id="dataset">Dataset</h3>
-<h4 id="in-memory">In-memory</h4>
+<h3 id="dataset">Dataset<a class="headerlink" href="#dataset" title="Permanent link">¶</a></h3>
+<h4 id="in-memory">In-memory<a class="headerlink" href="#in-memory" title="Permanent link">¶</a></h4>
<p>An in-memory dataset, with data in the default graph taken from a local file.</p>
<div class="codehilite"><pre><span class="o"><</span>#<span class="n">books</span><span class="o">></span> <span class="n">rdf</span><span class="p">:</span><span class="n">type</span> <span class="n">ja</span><span class="p">:</span><span class="n">RDFDataset</span>Â <span class="p">;</span>
<span class="n">rdfs</span><span class="p">:</span><span class="n">label</span> "<span class="n">Books</span>"Â <span class="p">;</span>
@@ -238,7 +249,7 @@ graph of data.</p>
</pre></div>
-<h4 id="tdb">TDB</h4>
+<h4 id="tdb">TDB<a class="headerlink" href="#tdb" title="Permanent link">¶</a></h4>
<div class="codehilite"><pre><span class="o"><</span>#<span class="n">dataset</span><span class="o">></span> <span class="n">rdf</span><span class="p">:</span><span class="n">type</span> <span class="n">tdb</span><span class="p">:</span><span class="n">DatasetTDB</span>Â <span class="p">;</span>
<span class="n">tdb</span><span class="p">:</span><span class="n">location</span> "<span class="n">DB</span>"Â <span class="p">;</span>
# <span class="n">Query</span> <span class="n">timeout</span> <span class="n">on</span> <span class="n">this</span> <span class="n">dataset</span> <span class="p">(</span>1<span class="n">s</span><span class="p">,</span> 1000 <span class="n">milliseconds</span><span class="p">)</span>
@@ -249,17 +260,17 @@ graph of data.</p>
</pre></div>
-<h4 id="inference">Inference</h4>
+<h4 id="inference">Inference<a class="headerlink" href="#inference" title="Permanent link">¶</a></h4>
<blockquote>
<p>@@</p>
</blockquote>
-<h2 id="server-configuration">Server Configuration</h2>
+<h2 id="server-configuration">Server Configuration<a class="headerlink" href="#server-configuration" title="Permanent link">¶</a></h2>
<p>If you need to load additional classes, or set global parameters, then these go in
<code>FUSEKI_BASE/config.ttl</code>.</p>
<p>Additional classes can not be loaded if running as a <code>.war</code> file. You will
need to create a custom <code>.war</code> file consisting of the contents of the Fuseki
web application and the additional classes</p>
-<h3 id="server-section">Server Section</h3>
+<h3 id="server-section">Server Section<a class="headerlink" href="#server-section" title="Permanent link">¶</a></h3>
<div class="codehilite"><pre><span class="p">[]</span> <span class="n">rdf</span><span class="p">:</span><span class="n">type</span> <span class="n">fuseki</span><span class="p">:</span><span class="n">Server</span>Â <span class="p">;</span>
# <span class="n">Server</span><span class="o">-</span><span class="n">wide</span> <span class="n">context</span> <span class="n">parameters</span> <span class="n">can</span> <span class="n">be</span> <span class="n">given</span> <span class="n">here</span><span class="p">.</span>
# <span class="n">For</span> <span class="n">example</span><span class="p">,</span> <span class="n">to</span> <span class="n">set</span> <span class="n">query</span> <span class="n">timeouts</span><span class="p">:</span> <span class="n">on</span> <span class="n">a</span> <span class="n">server</span><span class="o">-</span><span class="n">wide</span> <span class="n">basis</span><span class="p">:</span>
@@ -274,7 +285,7 @@ web application and the additional class
</pre></div>
-<h2 id="compatibility-with-fuseki-1-configuration">Compatibility with Fuseki 1 configuration</h2>
+<h2 id="compatibility-with-fuseki-1-configuration">Compatibility with Fuseki 1 configuration<a class="headerlink" href="#compatibility-with-fuseki-1-configuration" title="Permanent link">¶</a></h2>
<p>Configurations from Fuseki 1, where all dataset and server setup is in a
single configuration file, will still work. It is less flexible
(you can't restart these services after stopping them in a running server)