You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by gi...@apache.org on 2020/07/09 20:38:01 UTC
[jena-site] branch asf-site updated: Updated site from master
(1309e0970ea601f7f74b488a9b703a140b4d41eb)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e1c5dcf Updated site from master (1309e0970ea601f7f74b488a9b703a140b4d41eb)
e1c5dcf is described below
commit e1c5dcf2800a2d7254a23c4179073b51388f28ad
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Jul 9 20:37:57 2020 +0000
Updated site from master (1309e0970ea601f7f74b488a9b703a140b4d41eb)
---
.../eyeball}/eyeball-getting-started.html | 12 ++-
.../{tools => archive/eyeball}/eyeball-guide.html | 12 ++-
.../{tools => archive/eyeball}/eyeball-manual.html | 12 ++-
.../documentation/{ => archive}/larq/index.html | 10 ++-
.../documentation/assembler/assembler-howto.html | 2 +-
content/documentation/index.xml | 37 ++++-----
content/documentation/inference/index.html | 14 ++--
content/documentation/io/rdf-input.html | 66 ++++++++--------
content/documentation/io/rdfxml_howto.html | 49 ++++++------
content/documentation/notes/index.html | 2 +-
.../{file-manager.html => stream-manager.html} | 88 +++++++++-------------
.../documentation/notes/system-initialization.html | 2 +-
content/documentation/query/extension.html | 2 +-
content/documentation/rdfstar/index.html | 24 +++++-
content/documentation/shacl/index.html | 5 ++
content/index.xml | 37 ++++-----
content/sitemap.xml | 54 ++++++-------
content/tutorials/rdf_api.html | 22 +++---
content/tutorials/rdf_api_pt.html | 14 ++--
content/tutorials/sparql_datasets.html | 5 --
content/tutorials/sparql_datasets_pt.html | 3 -
21 files changed, 251 insertions(+), 221 deletions(-)
diff --git a/content/documentation/tools/eyeball-getting-started.html b/content/documentation/archive/eyeball/eyeball-getting-started.html
similarity index 96%
rename from content/documentation/tools/eyeball-getting-started.html
rename to content/documentation/archive/eyeball/eyeball-getting-started.html
index 21ce072..cc66685 100644
--- a/content/documentation/tools/eyeball-getting-started.html
+++ b/content/documentation/archive/eyeball/eyeball-getting-started.html
@@ -118,7 +118,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/tools/eyeball-getting-started.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
+ <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/archive/eyeball/eyeball-getting-started.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -153,7 +153,15 @@
- <li><a href='/documentation/tools'>TOOLS</a></li>
+ <li><a href='/documentation/archive'>ARCHIVE</a></li>
+
+
+
+
+
+
+
+ <li><a href='/documentation/archive/eyeball'>EYEBALL</a></li>
diff --git a/content/documentation/tools/eyeball-guide.html b/content/documentation/archive/eyeball/eyeball-guide.html
similarity index 98%
rename from content/documentation/tools/eyeball-guide.html
rename to content/documentation/archive/eyeball/eyeball-guide.html
index 578cd29..ab14df8 100644
--- a/content/documentation/tools/eyeball-guide.html
+++ b/content/documentation/archive/eyeball/eyeball-guide.html
@@ -118,7 +118,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/tools/eyeball-guide.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
+ <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/archive/eyeball/eyeball-guide.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -153,7 +153,15 @@
- <li><a href='/documentation/tools'>TOOLS</a></li>
+ <li><a href='/documentation/archive'>ARCHIVE</a></li>
+
+
+
+
+
+
+
+ <li><a href='/documentation/archive/eyeball'>EYEBALL</a></li>
diff --git a/content/documentation/tools/eyeball-manual.html b/content/documentation/archive/eyeball/eyeball-manual.html
similarity index 99%
rename from content/documentation/tools/eyeball-manual.html
rename to content/documentation/archive/eyeball/eyeball-manual.html
index b115e7a..7b50739 100644
--- a/content/documentation/tools/eyeball-manual.html
+++ b/content/documentation/archive/eyeball/eyeball-manual.html
@@ -118,7 +118,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/tools/eyeball-manual.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
+ <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/archive/eyeball/eyeball-manual.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -153,7 +153,15 @@
- <li><a href='/documentation/tools'>TOOLS</a></li>
+ <li><a href='/documentation/archive'>ARCHIVE</a></li>
+
+
+
+
+
+
+
+ <li><a href='/documentation/archive/eyeball'>EYEBALL</a></li>
diff --git a/content/documentation/larq/index.html b/content/documentation/archive/larq/index.html
similarity index 98%
rename from content/documentation/larq/index.html
rename to content/documentation/archive/larq/index.html
index 34c5c0d..67a9f17 100644
--- a/content/documentation/larq/index.html
+++ b/content/documentation/archive/larq/index.html
@@ -118,7 +118,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/larq/__index.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
+ <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/archive/larq/__index.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -156,6 +156,14 @@
+ <li><a href='/documentation/archive'>ARCHIVE</a></li>
+
+
+
+
+
+
+
<li class="active">LARQ</li>
diff --git a/content/documentation/assembler/assembler-howto.html b/content/documentation/assembler/assembler-howto.html
index 8ad7841..4a6242c 100644
--- a/content/documentation/assembler/assembler-howto.html
+++ b/content/documentation/assembler/assembler-howto.html
@@ -228,7 +228,7 @@ this document, we will usually leave out inferrable types.</p>
<p>We can construct our example model from the specification like this
(you may need to tweak the filename to make this work in your
environment):</p>
-<pre><code>Model spec = FileManager.get().loadModel( "examples.ttl" );
+<pre><code>Model spec = RDFDataMgr.loadModel( "examples.ttl" );
Resource root = spec.createResource( spec.expandPrefix( "eg:opening-example" ) );
Model m = Assembler.general.openModel( root );
</code></pre>
diff --git a/content/documentation/index.xml b/content/documentation/index.xml
index 81a2a7e..83b0d32 100644
--- a/content/documentation/index.xml
+++ b/content/documentation/index.xml
@@ -12,10 +12,10 @@
<item>
<title>A brief guide to Jena Eyeball</title>
- <link>https://jena.apache.org/documentation/tools/eyeball-guide.html</link>
+ <link>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/tools/eyeball-guide.html</guid>
+ <guid>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</guid>
<description>This page is historical &ldquo;for information only&rdquo; - there is no Apache release of Eyeball and the code has not been updated for Jena3.
The original source code is available.
So you&rsquo;ve got Eyeball installed and you&rsquo;ve run it on one of your files, and Eyeball doesn&rsquo;t like it. You&rsquo;re not sure why, or what to do about it. Here&rsquo;s what&rsquo;s going on.
@@ -118,7 +118,8 @@ It implements the six Conformance Classes described in the GeoSPARQL document:
<guid>https://jena.apache.org/documentation/notes/system-initialization.html</guid>
<description>Jena has a simple initialization sequence that is used to setup components available at runtime.
Application code is welcome to also use this mechanism. This must be done with care. Java initialization can lead to visibility of uninitialized data.
-The standard initialization sequence is Core -&gt; RIOT -&gt; ARQ -&gt; TDB -&gt; other (SDB, jena text, jena spatial)
+The standard initialization sequence is
+Core -&gt; RIOT -&gt; ARQ -&gt; TDB -&gt; other (SDB, jena text, jena spatial)
The sequence from core to TDB should be executed before application components. See below for how to control the order.</description>
</item>
@@ -613,10 +614,10 @@ Optimization in ARQ proceeds on two levels. After the query is parsed, the SPARQ
<item>
<title>Eyeball - checking RDF/OWL for common problems</title>
- <link>https://jena.apache.org/documentation/tools/eyeball-getting-started.html</link>
+ <link>https://jena.apache.org/documentation/archive/eyeball/eyeball-getting-started.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/tools/eyeball-getting-started.html</guid>
+ <guid>https://jena.apache.org/documentation/archive/eyeball/eyeball-getting-started.html</guid>
<description>Eyeball is a Jena-based tool for checking RDF models (including OWL) for common problems. It is user-extensible using plugins.
This page is historical &ldquo;for information only&rdquo; - there is no Apache release of Eyeball and the code has not been updated for Jena3.
The original source code is available.
@@ -775,7 +776,7 @@ The relevant SPARQL standards are:
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://jena.apache.org/documentation/notes/</guid>
- <description> Dataset Transactions Concurrency how-to Handling concurrent access to Jena models Event handler how-to Responding to events File manager how-to Convenient access to RDF files Model factory Creating Jena models of various kinds RDF frames Viewing RDF statements as frame-like objects Reification API support for RDF reification Typed literals Creating and extracting RDF typed literals SSE SPARQL Syntax Expressions Repacking Jena jars Jena Initialization </description>
+ <description> Dataset Transactions Concurrency how-to Handling concurrent access to Jena models Event handler how-to Responding to events Stream manager how-to Redirecting URLs to local files Model factory Creating Jena models of various kinds RDF frames Viewing RDF statements as frame-like objects Reification API support for RDF reification Typed literals Creating and extracting RDF typed literals SSE SPARQL Syntax Expressions Repacking Jena jars Jena Initialization </description>
</item>
<item>
@@ -874,10 +875,10 @@ Sub Packages Query Builder </description>
<item>
<title>Jena Eyeball manual</title>
- <link>https://jena.apache.org/documentation/tools/eyeball-manual.html</link>
+ <link>https://jena.apache.org/documentation/archive/eyeball/eyeball-manual.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/tools/eyeball-manual.html</guid>
+ <guid>https://jena.apache.org/documentation/archive/eyeball/eyeball-manual.html</guid>
<description>This page is historical &ldquo;for information only&rdquo; - there is no Apache release of Eyeball and the code has not been updated for Jena3.
The original source code is available.
This document describes Eyeball, an &ldquo;RDF lint&quot;. See the release notes for descriptions of changes from previous versions. Eyeball was a part of the Jena family of RDF/OWL tools.
@@ -1045,10 +1046,10 @@ Read transactions These are used for SPARQL queries and code using the Jena API
<item>
<title>LARQ - adding free text searches to SPARQL</title>
- <link>https://jena.apache.org/documentation/larq/</link>
+ <link>https://jena.apache.org/documentation/archive/larq/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/larq/</guid>
+ <guid>https://jena.apache.org/documentation/archive/larq/</guid>
<description>As of Jena 2.11.0, LARQ is replaced by jena-text
jena-text includes use of Apache Solr as a shared, search server, or Apache Lucene as a local text index. From Fuseki 0.2.7, jena-text is built into Fuseki.
LARQ is not compatible with jena-text; the index format has changed and the integration with SPARQL is different.
@@ -1182,9 +1183,9 @@ xml:lang is fully supported, both in RDF/XML and any document embedding RDF/XML.
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://jena.apache.org/documentation/io/rdf-input.html</guid>
- <description>This page details the setup of RDF I/O technology (RIOT) for input introduced in Jena 2.10.
+ <description>This page details the setup of RDF I/O technology (RIOT) for Apache Jena.
See Writing RDF for details of the RIOT Writer system.
- API Determining the RDF syntax Example 1 : Common usage Example 2 : Using the RDFDataMgr Example 3 : Using RDFParser Logging The StreamManager and LocationMapper Configuring a StreamManager Configuring a LocationMapper Advanced examples Iterating over parser output Filtering the output of parsing Add a new language Full details of operations are given in the javadoc.</description>
+ API Determining the RDF syntax Example 1 : Using the RDFDataMgr Example 2 : Model usage Example 3 : Using RDFParser Logging The StreamManager and LocationMapper Configuring a StreamManager Configuring a LocationMapper Advanced examples Iterating over parser output Filtering the output of parsing Add a new language Full details of operations are given in the javadoc.</description>
</item>
<item>
@@ -1789,15 +1790,15 @@ DatasetGraph - the interface DatasetGraphBase DatasetGraphBaseFind DatasetGraphC
</item>
<item>
- <title>The Jena FileManager and LocationMapper</title>
- <link>https://jena.apache.org/documentation/notes/file-manager.html</link>
+ <title>The Jena StreamManager and LocationMapper</title>
+ <link>https://jena.apache.org/documentation/notes/stream-manager.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/notes/file-manager.html</guid>
- <description>The FileManager is a utility to find and read files into models. There is a standard global FileManager and applications may also define specific ones by constructing addition FileManagers.
+ <guid>https://jena.apache.org/documentation/notes/stream-manager.html</guid>
+ <description>The StreamManager is a utility to find and read files into models. There is a standard global StreamManager and applications may also define specific ones by constructing additional StreamManagers.
The LocationMapper provides alternative locations for RDF data.
-The File Manager Files are named by a string, according to the conventions of their storage system. Typically this is by URI. There are a number of storage system adapters provided:
- File locator (with own current directory) URL locator Class loader locator Zip file locator The global file manager has a file location, a URL locator and a class loader (tried in that order).</description>
+The Stream Manager Files are named by a string, according to the conventions of their storage system. Typically this is by URI. There are a number of storage system adapters provided:
+ File locator (with own current directory) URL locator (HTTP and FTP) Class loader locator Zip file locator The global stream manager has a file location, a URL locator and a class loader (tried in that order).</description>
</item>
<item>
diff --git a/content/documentation/inference/index.html b/content/documentation/inference/index.html
index 0eaedf7..82452bb 100644
--- a/content/documentation/inference/index.html
+++ b/content/documentation/inference/index.html
@@ -435,7 +435,7 @@ InfModel inf = ModelFactory.createInfModel(boundReasoner, data);
which can be used for programmatic handling of the violations.</p>
<p>For example, to check a data set and list any problems one could do something
like:</p>
-<pre><code>Model data = FileManager.get().loadModel(fname);
+<pre><code>Model data = RDFDataMgr.loadModel(fname);
InfModel infmodel = ModelFactory.createRDFSModel(data);
ValidityReport validity = infmodel.validate();
if (validity.isValid()) {
@@ -772,8 +772,8 @@ Reasoner reasoner = RDFSRuleReasonerFactory.theInstance()Create(config);
<p>Then the following code fragment can be used to read files containing these
definitions, create an inference model and query it for information on the <code>rdf:type</code>
of <code>colin</code> and the <code>rdf:type</code> of <code>Person</code>:</p>
-<pre><code>Model schema = FileManager.get().loadModel("file:data/rdfsDemoSchema.rdf");
-Model data = FileManager.get().loadModel("file:data/rdfsDemoData.rdf");
+<pre><code>Model schema = RDFDataMgr.loadModel("file:data/rdfsDemoSchema.rdf");
+Model data = RDFDataMgr.loadModel("file:data/rdfsDemoData.rdf");
InfModel infmodel = ModelFactory.createRDFSModel(schema, data);
Resource colin = infmodel.getResource("urn:x-hp:eg/colin");
@@ -1163,8 +1163,8 @@ configuration still leaves something to be desired and will the subject of futur
and "<code>bigName42</code>".</p>
<p>We can create an instance of the OWL reasoner, specialized to the demo schema
and then apply that to the demo data to obtain an inference model, as follows:</p>
-<pre><code>Model schema = FileManager.get().loadModel("file:data/owlDemoSchema.owl");
-Model data = FileManager.get().loadModel("file:data/owlDemoData.rdf");
+<pre><code>Model schema = RDFDataMgr.loadModel("file:data/owlDemoSchema.owl");
+Model data = RDFDataMgr.loadModel("file:data/owlDemoData.rdf");
Reasoner reasoner = ReasonerRegistry.getOWLReasoner();
reasoner = reasoner.bindSchema(schema);
InfModel infmodel = ModelFactory.createInfModel(reasoner, data);
@@ -1988,7 +1988,7 @@ configuration.addProperty(ReasonerVocabulary.PROPruleSet, “data/demo.rule
<p>// Create an instance of such a reasoner
Reasoner reasoner = GenericRuleReasonerFactory.theInstance().create(configuration);</p>
<p>// Load test data
-Model data = FileManager.get().loadModel(“file:data/demoData.rdf”);
+Model data = RDFDataMgr.loadModel(“file:data/demoData.rdf”);
InfModel infmodel = ModelFactory.createInfModel(reasoner, data);</p>
<p>// Query for all things related to “a” by “p”
Property p = data.getProperty(demoURI, “p”);
@@ -2059,7 +2059,7 @@ System.out.println(” - " + PrintUtil.print(i.nextStatement()));
should be forward, all the inferences which need all of the results of the RDFS/OWL rules
should be backward. Note that the RDFS and OWL rulesets assume certain settings
for the GenericRuleReasoner so a typical configuration is:</p>
-<pre><code>Model data = FileManager.get().loadModel("file:data.n3");
+<pre><code>Model data = RDFDataMgr.loadModel("file:data.n3");
List rules = Rule.rulesFromURL("myrules.rules");
GenericRuleReasoner reasoner = new GenericRuleReasoner(rules);
diff --git a/content/documentation/io/rdf-input.html b/content/documentation/io/rdf-input.html
index 31feb9e..30218e7 100644
--- a/content/documentation/io/rdf-input.html
+++ b/content/documentation/io/rdf-input.html
@@ -175,16 +175,15 @@
</div>
<h1 class="title">Reading RDF in Apache Jena</h1>
- <p>This page details the setup of RDF I/O technology (RIOT) for input
-introduced in Jena 2.10.</p>
+ <p>This page details the setup of RDF I/O technology (RIOT) for Apache Jena.</p>
<p>See <a href="rdf-output.html">Writing RDF</a> for details of the RIOT Writer system.</p>
<ul>
<li><a href="#api">API</a>
<ul>
<li><a href="#determining-the-rdf-syntax">Determining the RDF syntax</a></li>
-<li><a href="#example-1-common-usage">Example 1 : Common usage</a></li>
-<li><a href="#example-2-using-the-rdfdatamgr">Example 2 : Using the RDFDataMgr</a></li>
-<li><a href="#example-3-using-rdfparser">Example 3 : Using RDFParser</a></li>
+<li><a href="#using-rdfdatamgr">Example 1 : Using the RDFDataMgr</a></li>
+<li><a href="#model-usage">Example 2 : Model usage</a></li>
+<li><a href="#using-rdfparser">Example 3 : Using RDFParser</a></li>
</ul>
</li>
<li><a href="#logging">Logging</a></li>
@@ -318,19 +317,9 @@ AddType application/n-quads .nq
AddType application/trix+xml .trix
AddType application/rdf+thrift .trdf
</code></pre>
-<h3 id="example-1--common-usage">Example 1 : Common usage</h3>
-<p>In this example, a file in the current directory is read as Turtle.</p>
-<pre><code>Model model = ModelFactory.createDefaultModel() ;
-model.read("data.ttl") ;
-</code></pre>
-<p>If the syntax is not as the file extension, a language can be declared:</p>
-<pre><code>model.read("data.foo", "TURTLE") ;
-</code></pre>
-<h3 id="example-2--using-the-rdfdatamgr">Example 2 : Using the RDFDataMgr</h3>
-<p>In versions of Jena prior to 2.10.0, the <code>FileManager</code> provided some of
-this functionality. It was more basic, and not properly web enabled.
-The API <code>RDFDataMgr</code> supercedes the <code>FileManager</code>.</p>
-<p>`RDFDataMgr “load*” operations create an
+<h3 id="using-rdfdatamgr">Example 1 : Using the RDFDataMgr</h3>
+<p><code>RDFDataMgr</code> provides operations to load, read and write models and datasets.</p>
+<p><code>RDFDataMgr</code> “load” operations create an
in-memory container (model, or dataset as appropriate); “read” operations
add data into an existing model or dataset.</p>
<pre><code>// Create a model and read into it from file
@@ -344,8 +333,16 @@ Dataset dataset = RDFDataMgr.loadDataset("data.trig") ;
// Read into an existing Model
RDFDataMgr.read(model, "data2.ttl") ;
</code></pre>
-<h3 id="example-3--using-rdfparser">Example 3 : Using RDFParser</h3>
-<p>Detail control over the setup of the parsing process is provided by
+<h3 id="model-usage">Example 2 : Common usage</h3>
+<p>The original Jena Model API operation for <code>read</code> and <code>write</code> provide another way to the same machinery:</p>
+<pre><code>Model model = ModelFactory.createDefaultModel() ;
+model.read("data.ttl") ;
+</code></pre>
+<p>If the syntax is not as the file extension, a language can be declared:</p>
+<pre><code>model.read("data.foo", "TURTLE") ;
+</code></pre>
+<h3 id="using-rdfparser">Example 3 : Using RDFParser</h3>
+<p>Detailed control over the setup of the parsing process is provided by
<code>RDFParser</code> which provides a builder pattern. It has many options - see
<a href="/documentation/javadoc/arq/org/apache/jena/riot/RDFParser.html">the javadoc for all details</a>.</p>
<p>For example, to read Trig data, and set the error handler specially,</p>
@@ -363,13 +360,24 @@ RDFDataMgr.read(model, "data2.ttl") ;
<p>The parsers log to a logger called <code>org.apache.jena.riot</code>. To avoid <code>WARN</code>
messages, set this to <code>ERROR</code> in the logging system of the application.</p>
<h2 id="streammanager-and-locationmapper">StreamManager and LocationMapper</h2>
+<p>Operations to read RDF data can be redirected to local copies and to other URLs.
+This is useful to provide local copies of remote resources.</p>
<p>By default, the <code>RDFDataMgr</code> uses the global <code>StreamManager</code> to open typed
-InputStreams. This is available to applications via <code>RDFDataMgr.open</code> as well as directly
-using a <code>StreamManager</code>.</p>
-<p>The <code>StreamManager</code> is chosen based on the <code>Context</code> object for the
+InputStreams. The <code>StreamManager</code> can be set using the <code>RDFParser</code> builder:</p>
+<pre><code> // Create a copy of the global default StreamManager.
+ StreamManager sm = StreamManager.get().clone();
+ // Add directory "/tmp" as a place to look for files
+ sm.addLocator(new LocatorFile("/tmp"));
+
+ RDFParser.create()
+ .streamManager(sm)
+ .source("data.ttl")
+ .parse(...);
+</code></pre>
+<p>It can also be set in a <code>Context</code> object given the the RDFParser for the
operation, but normally this defaults to the global <code>Context</code> available via
-<code>Context.get()</code>. The constant <code>RDFDataMgr.streamManagerSymbol</code>, which is
-<code>http://jena.apache.org/riot/streamManager</code> is used.</p>
+<code>Context.get()</code>. The constant <code>SysRIOT.sysStreamManager</code>, which is
+<code>http://jena.apache.org/riot/streamManager</code>, is used.</p>
<p>Specialized StreamManagers can be configured with specific locators for
data:</p>
<ul>
@@ -384,7 +392,7 @@ files. The default configuration used for the global <code>StreamManager</code>
a file access class, where the current directory is that of the java
process, a URL accessor for reading from the web, and a
class loader-based accessor. Different setups can be built and used
-either as the global set up,</p>
+either as the global set up, or on a per request basis.</p>
<p>There is also a <code>LocationMapper</code> for rewriting file names and URLs before
use to allow placing known names in different places (e.g. having local
copies of import http resources).</p>
@@ -435,12 +443,6 @@ contain ‘:'.</p>
<p>Applications can also set mappings programmatically. No
configuration file is necessary.</p>
<p>The base URI for reading models will be the original URI, not the alternative location.</p>
-<h3 id="debugging">Debugging</h3>
-<p>Set the logging level of the classes:</p>
-<ul>
-<li>org.apache.jena.riot.stream.StreamManager</li>
-<li>org.apache.jena.riot.stream.LocationMapper</li>
-</ul>
<h2 id="advanced-examples">Advanced examples</h2>
<p>Example code may be found in <a href="https://github.com/apache/jena/tree/master/jena-arq/src-examples/arq/examples/riot/">jena-arq/src-examples</a>.</p>
<h3 id="iterating-over-parser-output">Iterating over parser output</h3>
diff --git a/content/documentation/io/rdfxml_howto.html b/content/documentation/io/rdfxml_howto.html
index c2936a1..085270f 100644
--- a/content/documentation/io/rdfxml_howto.html
+++ b/content/documentation/io/rdfxml_howto.html
@@ -605,25 +605,25 @@ method. This changes the properties for writing RDF/XML.</p>
<table>
<tr><th>Property Name</th><th>Description</th><th>Value class</th><th>Legal Values</th></tr>
<tr>
-<td>`xmlbase`</td>
+<td><tt>xmlbase</tt></td>
<td>The value to be included for an xml:base attribute on the root element in the file.</td>
-<td>`String`</td>
+<td><tt>String</tt></td>
<td>A URI string, or null (default)</td>
</tr>
<tr>
-<td>`longId`</td>
+<td><tt>longId</tt></td>
<td>Whether to use long or short id's for anon resources. Short id's are easier to read and are the default, but can run out of memory on very large models.</td>
-<td>`String` or `Boolean`</td>
-<td>`"true"`, `"false"` (default)</td>
+<td><tt>String</tt> or <tt>Boolean</tt></td>
+<td><tt>"true"</tt>, <tt>"false"</tt> (default)</td>
</tr>
<tr>
-<td>`allowBadURIs`</td>
+<td><tt>allowBadURIs</tt></td>
<td>URIs in the graph are, by default, checked prior to serialization.</td>
-<td>`String` or `Boolean`</td>
-<td>`"true"`, `"false"` (default)</td>
+<td><tt>String</tt> or <tt>Boolean</tt></td>
+<td><tt>"true"</tt>, <tt>"false"</tt> (default)</td>
</tr>
<tr>
-<td>`relativeURIs`</td>
+<td><tt>relativeURIs</tt></td>
<td>What sort of relative URIs should be used. A comma separated list of options:
<ul>
<li><em>same-document</em><br />
@@ -647,7 +647,7 @@ has been specified.</td></p>
<td> </td>
</tr>
<tr>
-<td>`showXmlDeclaration`</td>
+<td><tt>showXmlDeclaration</tt></td>
<td>
If true, an XML Declaration is included in the output, if false no XML declaration is included.
The default behaviour only gives an XML Declaration when asked to write to an `OutputStreamWriter`
@@ -660,11 +660,11 @@ XML declaration. To ensure that the encoding attribute is shown in the XML decla
<code>write(Model,OutputStream,String)</code>.</li>
</ul>
</td>
-<td>`true`, `"true"`, `false`, `"false"` or `"default"`</td>
+<td><tt>true</tt>, <tt>"true"</tt>, <tt>false</tt>, <tt>"false"</tt> or <tt>"default"</tt></td>
<td>can be true, false or "default" (null)</td>
</tr>
<tr>
-<td>`showDoctypeDeclaration`</td>
+<td><tt>showDoctypeDeclaration</tt></td>
<td>
If true, an XML Doctype declaration is included in the output. This
declaration includes a `!ENTITY` declaration for each prefix mapping
@@ -672,23 +672,23 @@ in the model, and any attribute value that starts with the URI of
that mapping is written as starting with the corresponding entity
invocation.
</td>
-<td>`String` or `Boolean`</td>
-<td>`true`, `false`, `"true"`, `"false"`</td>
+<td><tt>String</tt> or <tt>Boolean</tt></td>
+<td><tt>true</tt>, <tt>false</tt>, <tt>"true"</tt>, <tt>"false"</tt></td>
</tr>
<tr>
-<td>`tab`</td>
+<td><tt>tab</tt></td>
<td>The number of spaces with which to indent XML child elements.</td>
-<td>`String` or `Integer`</td>
+<td><tt>String</tt> or <tt>Integer</tt></td>
<td>positive integer "2" is the default</td>
</tr>
<tr>
-<td>`attributeQuoteChar`</td>
+<td><tt>attributeQuoteChar</tt></td>
<td>How to write XML attributes.</td>
-<td>`String`</td>
-<td>`"\""` or `"'"`</td>
+<td><tt>String</tt></td>
+<td><tt>"\""</tt> or <tt>"'"</tt></td>
</tr>
<tr>
-<td>`blockRules`</td>
+<td><tt>blockRules</tt></td>
<td>
A list of `Resource` or a `String` being a comma separated list of
fragment IDs from [http://www.w3.org/TR/rdf-syntax-grammar](http://www.w3.org/TR/rdf-syntax-grammar)
@@ -722,24 +722,23 @@ is blocked. For the basic writer (RDF/XML) only
has any effect, since none of the other rules are implemented by
that writer.</p>
</td>
-<td>`Resource[]` or `String`</td>
+<td><tt>Resource[]</tt> or <tt>String</tt></td>
<td></td>
</tr>
<tr>
-<td>`prettyTypes`</td>
+<td><tt>prettyTypes</tt></td>
<td>
Only for the RDF/XML-ABBREV writer. This is a list of the types of
the principal objects in the model. The writer will tend to create
RDF/XML with resources of these types at the top level.
</td>
<td>
-`Resource[]`
+<tt>Resource[]</tt>
</td>
<td></td>
</tr>
</table>
-
-As an example,
+<p>As an example,</p>
<pre><code>RDFWriter w = m.getWriter("RDF/XML-ABBREV");
w.setProperty("attributeQuoteChar","'");
w.setProperty("showXMLDeclaration","true");
diff --git a/content/documentation/notes/index.html b/content/documentation/notes/index.html
index cddf673..cb01624 100644
--- a/content/documentation/notes/index.html
+++ b/content/documentation/notes/index.html
@@ -174,7 +174,7 @@
<li><a href="/documentation/txn/transactions_api.html">Dataset Transactions</a></li>
<li><a href="concurrency-howto.html">Concurrency how-to</a> Handling concurrent access to Jena models</li>
<li><a href="event-handler-howto.html">Event handler how-to</a> Responding to events</li>
-<li><a href="file-manager.html">File manager how-to</a> Convenient access to RDF files</li>
+<li><a href="stream-manager.html">Stream manager how-to</a> Redirecting URLs to local files</li>
<li><a href="model-factory.html">Model factory</a> Creating Jena models of various kinds</li>
<li><a href="rdf-frames.html">RDF frames</a> Viewing RDF statements as frame-like objects</li>
<li><a href="reification.html">Reification</a> API support for RDF reification</li>
diff --git a/content/documentation/notes/file-manager.html b/content/documentation/notes/stream-manager.html
similarity index 77%
rename from content/documentation/notes/file-manager.html
rename to content/documentation/notes/stream-manager.html
index 7bfe77c..ad6d4f6 100644
--- a/content/documentation/notes/file-manager.html
+++ b/content/documentation/notes/stream-manager.html
@@ -3,7 +3,7 @@
<head>
- <title>Apache Jena - The Jena FileManager and LocationMapper</title>
+ <title>Apache Jena - The Jena StreamManager and LocationMapper</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -118,7 +118,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/notes/file-manager.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
+ <li id="edit"><a href="https://github.com/apache/jena-site/edit/master/source/documentation/notes/stream-manager.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -161,7 +161,7 @@
- <li class="active">FILE MANAGER</li>
+ <li class="active">STREAM MANAGER</li>
@@ -173,60 +173,39 @@
</div>
- <h1 class="title">The Jena FileManager and LocationMapper</h1>
+ <h1 class="title">The Jena StreamManager and LocationMapper</h1>
- <p>The FileManager is a utility to find and read files into models.
-There is a standard global FileManager and applications may also
-define specific ones by constructing addition FileManagers.</p>
+ <p>The StreamManager is a utility to find and read files into models.
+There is a standard global StreamManager and applications may also
+define specific ones by constructing additional StreamManagers.</p>
<p>The LocationMapper provides alternative locations for RDF data.</p>
-<h2 id="the-file-manager">The File Manager</h2>
+<h2 id="the-stream-manager">The Stream Manager</h2>
<p>Files are named by a string, according to the conventions of their
storage system. Typically this is by URI. There are a number of
storage system adapters provided:</p>
<ul>
<li>File locator (with own current directory)</li>
-<li>URL locator</li>
+<li>URL locator (HTTP and FTP)</li>
<li>Class loader locator</li>
<li>Zip file locator</li>
</ul>
-<p>The global file manager has a file location, a URL locator and a
-class loader (tried in that order).
-A FileManager can have an associated LocationMapper that transforms
+<p>The global stream manager has a file location, a URL locator and a
+class loader (tried in that order).</p>
+<p>A StreamManager can have an associated LocationMapper that transforms
names before use. This means local copies of documents can be used
transparently to the rest of the application.</p>
-<p>There are two categories of operations: loadModel, readModel. Load
-operations fetch and parse the data into a new memory model. Read
-operations fetch and parse the data into an existing model. For
-more complex ways to create a new model see
-<a href="../assembler/index.html">the Assembler documentation</a>.</p>
-<p>Each FileManager has an optional in-memory cache of models. When
-on, loading models will look in the cache first and return a cached
-model if possible. This cached model is not copied - updates <em>will</em>
-change the cached version. The default is that cache is off.</p>
-<p>In fetching and parsing a file, the file manager will attempt to
-guess the serialization format, if not explicitly supplied. This is
-by name extension:</p>
-<ul>
-<li><code>.rdf</code> and <code>.owl</code> : RDF/XML</li>
-<li><code>.n3</code> : N3</li>
-<li><code>.nt</code> : N-Triples</li>
-<li>Anything else: RDF/XML</li>
-</ul>
+<p>A StreamManager provides an “open” operation to get an <code>InputStream</code>
+to the resource.</p>
<h2 id="the-locationmapper-configuration-file">The LocationMapper configuration file</h2>
-<p>This example uses the RDF subset of
-<a href="http://www.w3.org/2000/10/swap/Primer">N3</a>. Jena has an RDF reader
-and RDF writer for N3. This is nearly the same as
-<a href="http://www.ilrt.bris.ac.uk/discovery/2004/01/turtle/">Turtle</a> but
-allowing international characters and some restrictions due to N3.</p>
-<p>Location mapping files are RDF - they may be written in RDF/XML, N3
-(file suffix <code>.n3</code>) or N-Triples (file suffix <code>.nt</code>). The default
+<p>Location mapping files are RDF - they may be written in RDF/XML, Turtle
+(file suffix <code>.ttl</code>) or N-Triples (file suffix <code>.nt</code>). The default
is RDF/XML unless one of these suffices is found.</p>
<pre><code>@prefix lm: <http://jena.hpl.hp.com/2004/08/location-mapping#> .
[] lm:mapping
- [ lm:name "file:foo.n3" ; lm:altName "file:etc/foo.n3" ] ,
- [ lm:prefix "file:etc/" ; lm:altPrefix "file:ETC/" ] ,
- [ lm:name "file:etc/foo.n3" ; lm:altName "file:DIR/foo.n3" ]
+ [ lm:name "file:foo.ttl" ; lm:altName "file:etc/foo.ttl" ] ,
+ [ lm:prefix "file:etc/" ; lm:altPrefix "file:ETC/" ] ,
+ [ lm:name "file:etc/foo.ttl" ; lm:altName "file:DIR/foo.ttl" ]
.
</code></pre>
<p>There are two types of location mapping: exact match renaming and
@@ -236,8 +215,8 @@ the LocationMapper will search for the longest matching prefix. If
two are the same length, there is no guarantee on order tried;
there is no implied order in a location mapper configuration file
(it sets up two hash tables).</p>
-<p>In the example above, <code>file:etc/foo.n3</code> becomes <code>file:DIR/foo.n3</code>
-because that is an exact match. The prefix match of file:/etc/ is
+<p>In the example above, <code>file:etc/foo.ttl</code> becomes <code>file:DIR/foo.ttl</code>
+because that is an exact match. The prefix match of file:etc/ is
ignored.</p>
<p>All string tests are done case sensitively because the primary use
is for URLs.</p>
@@ -254,30 +233,31 @@ equivalent to the original.</li>
<p>A LocationMapper finds its configuration file by looking for the
following files, in order:</p>
<ul>
-<li><code>file:location-mapping.rdf</code></li>
-<li><code>file:location-mapping.n3</code></li>
-<li><code>file:etc/location-mapping.rdf</code></li>
-<li><code>file:etc/location-mapping.n3</code></li>
+<li><code>location-mapping.ttl</code></li>
+<li><code>location-mapping.rdf</code></li>
+<li><code>etc/location-mapping.rdf</code></li>
+<li><code>etc/location-mapping.ttl</code></li>
</ul>
-<p>This is a specified as a path - note the path separator is always
+<p>This is specified as a path - note the path separator is always
the character ‘;’ regardless of operating system because URLs
contain ‘:'.</p>
-<p>Applications can also set mappings programmatically. No
-configuration file is necessary.</p>
-<p>The base URI for reading models with the FileManager will be the
+<p><code>location-mapping.ttl;location-mapping.rdf;etc/location-mapping.rdf;etc/location-mapping.ttl</code></p>
+<p>Applications can also set mappings programmatically.
+No configuration file is necessary.</p>
+<p>The base URI for reading models with the StreamManager will be the
original URI, not the alternative location.</p>
<h3 id="debugging">Debugging</h3>
<p>If log4j2, set the logging level of the classes:</p>
-<pre><code>logger.filemanager.name = org.apache.jena.util.FileManager
+<pre><code>logger.filemanager.name = org.apache.jena.riot.system.stream.StreamManager
logger.filemanager.level = ALL
-logger.location-manager.name = org.apache.jena.util.LocationManager
+logger.location-manager.name = org.apache.jena.riot.system.stream.LocationMapper
logger.location-manager.level = ALL
</code></pre>
<h3 id="see-also">See also</h3>
<p>Javadoc:</p>
<ul>
-<li><a href="/documentation/javadoc/jena/org/apache/jena/util/FileManager.html">FileManager</a></li>
-<li><a href="/documentation/javadoc/jena/org/apache/jena/util/LocationMapper.html">LocationMapper</a></li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/riot/system/stream/StreamManager.html">StreamManager</a></li>
+<li><a href="/documentation/javadoc/arq/org/apache/jena/riot/system/stream/LocationMapper.html">LocationMapper</a></li>
</ul>
diff --git a/content/documentation/notes/system-initialization.html b/content/documentation/notes/system-initialization.html
index a6c859f..fa7a09b 100644
--- a/content/documentation/notes/system-initialization.html
+++ b/content/documentation/notes/system-initialization.html
@@ -180,7 +180,7 @@ used to setup components available at runtime.</p>
<p>Application code is welcome to also use this mechanism. This
must be done with care. Java initialization can lead to
visibility of uninitialized data.</p>
-<p>The standard initialization sequence is<br/>
+<p>The standard initialization sequence is<br>
Core -> RIOT -> ARQ -> TDB -> other (SDB, jena text, jena spatial)</p>
<p>The sequence from core to TDB should be executed before application
components. See below for how to control the order.</p>
diff --git a/content/documentation/query/extension.html b/content/documentation/query/extension.html
index 59a2b52..f73d339 100644
--- a/content/documentation/query/extension.html
+++ b/content/documentation/query/extension.html
@@ -199,7 +199,7 @@ functionality and remain within SPARQL. ARQ has a
<a href="library-propfunc.html">property function library</a>. Applications
can
<a href="writing_propfuncs.html">write and register their own property functions</a>.</p>
-<p>The <a href="/documentation/larq/">free text support in ARQ</a> is provided by
+<p>The <a href="/documentation/query/text-query.html/">free text support in ARQ</a> is provided by
<a href="http://lucene.apache.org/java/docs/index.html">Lucene</a>, using
property functions.</p>
<h2 id="filter-functions">Filter Functions</h2>
diff --git a/content/documentation/rdfstar/index.html b/content/documentation/rdfstar/index.html
index 083ed37..2fcff67 100644
--- a/content/documentation/rdfstar/index.html
+++ b/content/documentation/rdfstar/index.html
@@ -178,17 +178,15 @@ a way for one triple to refer to another triple. Another resource about RDF* is
</span></code></pre></div><p>The part <code><< :john foaf:name "John Smith" >></code> is a triple term and refers to the triple with subject <code>:john</code>, property <code>foaf:name</code> and object <code>"John Smith"</code>.</p>
<p>Triple terms can be in the subject or object position.</p>
<p>Jena provides support for RDF* and the related SPARQL*.</p>
-<p>Support for RDF* is experimentation in Jena 3.15.0 (released May 2020):</p>
<ul>
<li>Turtle, N-Triples, TriG and N-Quads extended for Triple Terms syntax. There is no output in RDF/XML.</li>
<li>SPARQL extended with Triple Term syntax for graph matching (in code, use <code>Syntax.syntaxARQ</code>).</li>
<li>SPARQL Result formats for JSON and XML extended to support Triple Terms in results.</li>
-<li>Support in memory-based storage (graphs and datasets).</li>
<li>Support in the Model API.</li>
</ul>
<p>All this is active by default in Fuseki.</p>
-<p>This support is experimental and subject to change. The aim is to follow the definition of RDF* as well as emerging _de facto_ consensus in other implementations.</p>
-<p>Later releases will extend support to persistent storage in <a href="/documentation/tdb">TDB1</a> and <a href="/documentation/tdb2/">TDB2</a>.</p>
+<p>The aim is to follow the definition of RDF* as well as emerging _de facto_ consensus in other implementations.</p>
+<p>Storage in databases <a href="/documentation/tdb">TDB1</a> and <a href="/documentation/tdb2/">TDB2</a> is supported as of Jena 3.16.0.</p>
<h2 id="rdf">RDF*</h2>
<p>RDF* syntax for triple terms is added to the parsers for Turtle, N-Triples, TriG and N-Quads.</p>
<p>Datasets may have graphs that have triple terms that refer to triples anywhere, not just in the same graph.</p>
@@ -235,6 +233,24 @@ is a prefix for <code><http://jena.apache.org/ARQ/function#></code>.</p>
</tr>
</tbody>
</table>
+<h3 id="sparql-property-functions-related-to-triple-terms">SPARQL Property Functions related to triple terms</h3>
+<p><code>apf:</code> is a prefix for <code><http://jena.apache.org/ARQ/property#></code>.</p>
+<table>
+<thead>
+<tr>
+<th>Property Function</th>
+<th>Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code><< s p o >> apf:find t</code> .</td>
+<td>Match the triple term. Any <code>s</code>, <code>p</code>, <code>o</code>, and <code>t</code> can be RDF terms or variables.</td>
+</tr>
+</tbody>
+</table>
+<p><code>apf:find</code> will result in all the variables being set according to the match,
+If <code>t</code> is a variable, <code>?t</code>, it is bound to a triple term for the match of <code><<s p o>></code>.</p>
<h3 id="sparql-results">SPARQL results</h3>
<p>The syntaxes for SPARQL results from a SELECT query, <code>application/sparql-results+json</code>,
<code>application/sparql-results+xml</code> are extended to include triple terms:</p>
diff --git a/content/documentation/shacl/index.html b/content/documentation/shacl/index.html
index f566617..5517802 100644
--- a/content/documentation/shacl/index.html
+++ b/content/documentation/shacl/index.html
@@ -249,6 +249,11 @@ shows validation and printing of the validation report in a text form and in RDF
<a href="https://github.com/apache/jena/tree/master/jena-shacl/src/main/java/org/apache/jena/shacl/examples/Shacl02_validateTransaction.java"><code>Shacl02_validateTransaction</code></a>
shows how to update a graph only if, after the changes, the graph is validated
according to the shapes provided.</p>
+<h2 id="shacl-compact-syntax">SHACL Compact Syntax</h2>
+<p>Jena can read <a href="https://w3c.github.io/shacl/shacl-compact-syntax/">SHACL Compact Syntax</a>. The file extensions are <code>.shc</code> and <code>.shaclc</code> and a registered language constant is <code>SHACLC.langShacl</code>.</p>
+<pre><code>RDFDataMgr.load("shapes.shc");
+
+RDFDataMgr.read("file:compactShapes", SHACLC.langShacl);</code></pre>
</div>
diff --git a/content/index.xml b/content/index.xml
index ed26898..e8a9c85 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -12,10 +12,10 @@
<item>
<title>A brief guide to Jena Eyeball</title>
- <link>https://jena.apache.org/documentation/tools/eyeball-guide.html</link>
+ <link>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/tools/eyeball-guide.html</guid>
+ <guid>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</guid>
<description>This page is historical &ldquo;for information only&rdquo; - there is no Apache release of Eyeball and the code has not been updated for Jena3.
The original source code is available.
So you&rsquo;ve got Eyeball installed and you&rsquo;ve run it on one of your files, and Eyeball doesn&rsquo;t like it. You&rsquo;re not sure why, or what to do about it. Here&rsquo;s what&rsquo;s going on.
@@ -148,7 +148,8 @@ It implements the six Conformance Classes described in the GeoSPARQL document:
<guid>https://jena.apache.org/documentation/notes/system-initialization.html</guid>
<description>Jena has a simple initialization sequence that is used to setup components available at runtime.
Application code is welcome to also use this mechanism. This must be done with care. Java initialization can lead to visibility of uninitialized data.
-The standard initialization sequence is Core -&gt; RIOT -&gt; ARQ -&gt; TDB -&gt; other (SDB, jena text, jena spatial)
+The standard initialization sequence is
+Core -&gt; RIOT -&gt; ARQ -&gt; TDB -&gt; other (SDB, jena text, jena spatial)
The sequence from core to TDB should be executed before application components. See below for how to control the order.</description>
</item>
@@ -664,10 +665,10 @@ Optimization in ARQ proceeds on two levels. After the query is parsed, the SPARQ
<item>
<title>Eyeball - checking RDF/OWL for common problems</title>
- <link>https://jena.apache.org/documentation/tools/eyeball-getting-started.html</link>
+ <link>https://jena.apache.org/documentation/archive/eyeball/eyeball-getting-started.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/tools/eyeball-getting-started.html</guid>
+ <guid>https://jena.apache.org/documentation/archive/eyeball/eyeball-getting-started.html</guid>
<description>Eyeball is a Jena-based tool for checking RDF models (including OWL) for common problems. It is user-extensible using plugins.
This page is historical &ldquo;for information only&rdquo; - there is no Apache release of Eyeball and the code has not been updated for Jena3.
The original source code is available.
@@ -835,7 +836,7 @@ The relevant SPARQL standards are:
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://jena.apache.org/documentation/notes/</guid>
- <description> Dataset Transactions Concurrency how-to Handling concurrent access to Jena models Event handler how-to Responding to events File manager how-to Convenient access to RDF files Model factory Creating Jena models of various kinds RDF frames Viewing RDF statements as frame-like objects Reification API support for RDF reification Typed literals Creating and extracting RDF typed literals SSE SPARQL Syntax Expressions Repacking Jena jars Jena Initialization </description>
+ <description> Dataset Transactions Concurrency how-to Handling concurrent access to Jena models Event handler how-to Responding to events Stream manager how-to Redirecting URLs to local files Model factory Creating Jena models of various kinds RDF frames Viewing RDF statements as frame-like objects Reification API support for RDF reification Typed literals Creating and extracting RDF typed literals SSE SPARQL Syntax Expressions Repacking Jena jars Jena Initialization </description>
</item>
<item>
@@ -996,10 +997,10 @@ Sub Packages Query Builder </description>
<item>
<title>Jena Eyeball manual</title>
- <link>https://jena.apache.org/documentation/tools/eyeball-manual.html</link>
+ <link>https://jena.apache.org/documentation/archive/eyeball/eyeball-manual.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/tools/eyeball-manual.html</guid>
+ <guid>https://jena.apache.org/documentation/archive/eyeball/eyeball-manual.html</guid>
<description>This page is historical &ldquo;for information only&rdquo; - there is no Apache release of Eyeball and the code has not been updated for Jena3.
The original source code is available.
This document describes Eyeball, an &ldquo;RDF lint&quot;. See the release notes for descriptions of changes from previous versions. Eyeball was a part of the Jena family of RDF/OWL tools.
@@ -1199,10 +1200,10 @@ If you wish your contribution to appear on this page, please raise a Jira issue
<item>
<title>LARQ - adding free text searches to SPARQL</title>
- <link>https://jena.apache.org/documentation/larq/</link>
+ <link>https://jena.apache.org/documentation/archive/larq/</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/larq/</guid>
+ <guid>https://jena.apache.org/documentation/archive/larq/</guid>
<description>As of Jena 2.11.0, LARQ is replaced by jena-text
jena-text includes use of Apache Solr as a shared, search server, or Apache Lucene as a local text index. From Fuseki 0.2.7, jena-text is built into Fuseki.
LARQ is not compatible with jena-text; the index format has changed and the integration with SPARQL is different.
@@ -1356,9 +1357,9 @@ xml:lang is fully supported, both in RDF/XML and any document embedding RDF/XML.
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://jena.apache.org/documentation/io/rdf-input.html</guid>
- <description>This page details the setup of RDF I/O technology (RIOT) for input introduced in Jena 2.10.
+ <description>This page details the setup of RDF I/O technology (RIOT) for Apache Jena.
See Writing RDF for details of the RIOT Writer system.
- API Determining the RDF syntax Example 1 : Common usage Example 2 : Using the RDFDataMgr Example 3 : Using RDFParser Logging The StreamManager and LocationMapper Configuring a StreamManager Configuring a LocationMapper Advanced examples Iterating over parser output Filtering the output of parsing Add a new language Full details of operations are given in the javadoc.</description>
+ API Determining the RDF syntax Example 1 : Using the RDFDataMgr Example 2 : Model usage Example 3 : Using RDFParser Logging The StreamManager and LocationMapper Configuring a StreamManager Configuring a LocationMapper Advanced examples Iterating over parser output Filtering the output of parsing Add a new language Full details of operations are given in the javadoc.</description>
</item>
<item>
@@ -2099,15 +2100,15 @@ DatasetGraph - the interface DatasetGraphBase DatasetGraphBaseFind DatasetGraphC
</item>
<item>
- <title>The Jena FileManager and LocationMapper</title>
- <link>https://jena.apache.org/documentation/notes/file-manager.html</link>
+ <title>The Jena StreamManager and LocationMapper</title>
+ <link>https://jena.apache.org/documentation/notes/stream-manager.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
- <guid>https://jena.apache.org/documentation/notes/file-manager.html</guid>
- <description>The FileManager is a utility to find and read files into models. There is a standard global FileManager and applications may also define specific ones by constructing addition FileManagers.
+ <guid>https://jena.apache.org/documentation/notes/stream-manager.html</guid>
+ <description>The StreamManager is a utility to find and read files into models. There is a standard global StreamManager and applications may also define specific ones by constructing additional StreamManagers.
The LocationMapper provides alternative locations for RDF data.
-The File Manager Files are named by a string, according to the conventions of their storage system. Typically this is by URI. There are a number of storage system adapters provided:
- File locator (with own current directory) URL locator Class loader locator Zip file locator The global file manager has a file location, a URL locator and a class loader (tried in that order).</description>
+The Stream Manager Files are named by a string, according to the conventions of their storage system. Typically this is by URI. There are a number of storage system adapters provided:
+ File locator (with own current directory) URL locator (HTTP and FTP) Class loader locator Zip file locator The global stream manager has a file location, a URL locator and a class loader (tried in that order).</description>
</item>
<item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 4fe2ba2..3db195f 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -8,8 +8,8 @@
</url>
<url>
- <loc>https://jena.apache.org/documentation/tools/eyeball-guide.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <loc>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</loc>
+ <lastmod>2020-06-28T16:59:07+01:00</lastmod>
</url>
<url>
@@ -29,7 +29,7 @@
<url>
<loc>https://jena.apache.org/tutorials/rdf_api.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -74,7 +74,7 @@
<url>
<loc>https://jena.apache.org/documentation/notes/system-initialization.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-06-29T18:06:08+01:00</lastmod>
</url>
<url>
@@ -89,7 +89,7 @@
<url>
<loc>https://jena.apache.org/documentation/shacl/</loc>
- <lastmod>2020-05-11T15:00:20+01:00</lastmod>
+ <lastmod>2020-06-28T17:01:55+01:00</lastmod>
</url>
<url>
@@ -299,7 +299,7 @@
<url>
<loc>https://jena.apache.org/documentation.html</loc>
- <lastmod>2020-06-26T14:59:03+01:00</lastmod>
+ <lastmod>2020-06-29T18:06:08+01:00</lastmod>
</url>
<url>
@@ -319,12 +319,12 @@
<url>
<loc>https://jena.apache.org/documentation/query/extension.html</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
- <loc>https://jena.apache.org/documentation/tools/eyeball-getting-started.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <loc>https://jena.apache.org/documentation/archive/eyeball/eyeball-getting-started.html</loc>
+ <lastmod>2020-06-28T16:59:07+01:00</lastmod>
</url>
<url>
@@ -399,7 +399,7 @@
<url>
<loc>https://jena.apache.org/documentation/notes/</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -469,7 +469,7 @@
<url>
<loc>https://jena.apache.org/documentation/assembler/assembler-howto.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -493,8 +493,8 @@
</url>
<url>
- <loc>https://jena.apache.org/documentation/tools/eyeball-manual.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <loc>https://jena.apache.org/documentation/archive/eyeball/eyeball-manual.html</loc>
+ <lastmod>2020-06-28T16:59:07+01:00</lastmod>
</url>
<url>
@@ -519,7 +519,7 @@
<url>
<loc>https://jena.apache.org/documentation/ontology/</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -554,7 +554,7 @@
<url>
<loc>https://jena.apache.org/documentation/io/rdfxml_howto.html</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -588,8 +588,8 @@
</url>
<url>
- <loc>https://jena.apache.org/documentation/larq/</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <loc>https://jena.apache.org/documentation/archive/larq/</loc>
+ <lastmod>2020-06-28T16:59:07+01:00</lastmod>
</url>
<url>
@@ -659,12 +659,12 @@
<url>
<loc>https://jena.apache.org/documentation/io/rdf-input.html</loc>
- <lastmod>2020-05-11T15:00:20+01:00</lastmod>
+ <lastmod>2020-06-29T18:06:08+01:00</lastmod>
</url>
<url>
<loc>https://jena.apache.org/documentation/inference/</loc>
- <lastmod>2020-05-11T15:00:20+01:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -829,12 +829,12 @@
<url>
<loc>https://jena.apache.org/tutorials/sparql_datasets.html</loc>
- <lastmod>2020-02-28T13:09:12+01:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
<loc>https://jena.apache.org/tutorials/sparql_datasets_pt.html</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -864,7 +864,7 @@
<url>
<loc>https://jena.apache.org/documentation/rdfstar/</loc>
- <lastmod>2020-05-18T21:50:48+01:00</lastmod>
+ <lastmod>2020-06-29T18:06:08+01:00</lastmod>
</url>
<url>
@@ -998,8 +998,8 @@
</url>
<url>
- <loc>https://jena.apache.org/documentation/notes/file-manager.html</loc>
- <lastmod>2020-05-11T15:00:20+01:00</lastmod>
+ <loc>https://jena.apache.org/documentation/notes/stream-manager.html</loc>
+ <lastmod>2020-06-29T18:06:08+01:00</lastmod>
</url>
<url>
@@ -1049,7 +1049,7 @@
<url>
<loc>https://jena.apache.org/tutorials.html</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -1064,7 +1064,7 @@
<url>
<loc>https://jena.apache.org/tutorials/rdf_api_pt.html</loc>
- <lastmod>2020-05-01T11:11:56+12:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
<url>
@@ -1109,7 +1109,7 @@
<url>
<loc>https://jena.apache.org/documentation/io/rdf-output.html</loc>
- <lastmod>2020-05-30T12:01:08+02:00</lastmod>
+ <lastmod>2020-06-28T16:59:39+01:00</lastmod>
</url>
</urlset>
\ No newline at end of file
diff --git a/content/tutorials/rdf_api.html b/content/tutorials/rdf_api.html
index 769c6a9..85197d7 100644
--- a/content/tutorials/rdf_api.html
+++ b/content/tutorials/rdf_api.html
@@ -409,7 +409,8 @@ model in RDF XML form to the standard output stream. The code again, is
very simple: <code>model.write</code> can take an <code>OutputStream</code>
argument.</p>
<pre>// now write the model in XML form to a file
-model.write(System.out);</pre>
+model.write(System.out);
+</pre>
<p>The output should look something like this:</p>
<pre><rdf:RDF
xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'
@@ -424,7 +425,8 @@ model.write(System.out);</pre>
<vcard:Family>Smith</vcard:Family>
</rdf:Description>
</rdf:RDF></pre>
-<p></p>
+<p>
+</p>
<p>The RDF specifications specify how to represent RDF as XML. The RDF
XML syntax is quite complex. The reader is referred to the <a
href="http://www.w3.org/TR/rdf-primer/">primer</a> being developed by the
@@ -456,10 +458,10 @@ correctly. It gives a URI to each blank node, making it no longer blank.</p>
<p>Jena has an extensible interface which allows new writers for different
serialization languages for RDF to be easily plugged in. The above call
invoked the standard 'dumb' writer. Jena also includes a more sophisticated
-RDF/XML writer which can be invoked by specifying another argument to the
-<code>write()</code> method call:</p>
-<pre>// now write the model in XML form to a file
-model.write(System.out, "RDF/XML-ABBREV");
+RDF/XML writer which can be invoked by using
+<code>RDFDataMgr.write</code> function call:</p>
+<pre>// now write the model in a pretty form
+RDFDataMgr.write(System.out, model, Lang.RDFXML);
</pre>
<p>This writer, the so called PrettyWriter, takes advantage of features of
the RDF/XML abbreviated syntax to write a Model more compactly. It is also
@@ -467,8 +469,8 @@ able to preserve blank nodes where that is possible. It is however, not
suitable for writing very large Models, as its performance is unlikely to be
acceptable. To write large files and preserve blank nodes, write in
N-Triples format:</p>
-<pre>// now write the model in N-TRIPLES form to a file
-model.write(System.out, "N-TRIPLES");
+<pre>// now write the model in N-TRIPLES form
+RDFDataMgr.write(System.out, model, Lang.NTRIPLES);
</pre>
<p>This will produce output similar to that of tutorial 3 which conforms to
the N-Triples specification.</p>
@@ -482,8 +484,8 @@ run, the input file must be in the current directory.</em></p>
// create an empty model
Model model = ModelFactory.createDefaultModel();
- // use the FileManager to find the input file
- InputStream in = FileManager.get().open( inputFileName );
+ // use the RDFDataMgr to find the input file
+ InputStream in = RDFDataMgr.open( inputFileName );
if (in == null) {
throw new IllegalArgumentException(
"File: " + inputFileName + " not found");
diff --git a/content/tutorials/rdf_api_pt.html b/content/tutorials/rdf_api_pt.html
index f63f4b5..12dd85d 100644
--- a/content/tutorials/rdf_api_pt.html
+++ b/content/tutorials/rdf_api_pt.html
@@ -340,13 +340,13 @@ model.write(System.out);</pre>
<p>O elemento <vcard:N> é um recurso. Neste caso, o recurso é representado por uma referência URI relativa. RDF o converte para uma referência URI absoluta concatenando com o URI base do documento.</p>
<p>Há um erro nesse RDF XML: ele não representa exatamente o modelo que criamos. Foi dado uma URI ao blank node do modelo. Ele não é mais um blank node portanto. A sintaxe RDF/XML não é capaz de representar todos os modelos RDF; por exemplo, ela não pode representar um blank node que é o objeto de duas sentenças. O escritor que usamos para escrever este RDF/XML não é capaz de escrever corretamente o subconjunto de modelos que podem ser escritos corretamente. Ele dá uma URI a cada blank n [...]
<p>Jena possui uma interface extensível que permite novos escritores para diferentes linguagens de serialização RDF. Jena possuem também um escritor RDF/XML mais sofisticado que pode ser invocado ao especificar outro argumento à chamada de método
-<code>write()</code>:</p>
-<pre>// now write the model in XML form to a file
-model.write(System.out, "RDF/XML-ABBREV");
- </pre>
+<code>RDFDataMgr.write</code>:</p>
+<pre>// now write the model in a pretty form
+RDFDataMgr.write(System.out, model, Lang.RDFXML);
+</pre>
<p>Este escritor, chamado também de PrettyWriter, ganha vantagem ao usar as particularidades da sintaxe abreviada de RDF/XML ao criar um modelo mais compacto. Ele também é capaz de preservar os blank nodes onde é possível. Entretanto, não é recomendável para escrever modelos muito grandes, já que sua desempenho deixa a desejar. Para escrever grandes arquivos e preservar os blank nodes, escreva no formato de N-Triplas:</p>
<pre>// now write the model in XML form to a file
-model.write(System.out, "N-TRIPLE");
+RDFDataMgr.write(System.out, model, Lang.NTRIPLES);
</pre>
<p>Isso produzirá uma saída similar à do tutorial 3, que está em conformidade com a especificação de N-Triplas.</p>
<h2><a id="ch-Reading-RDF">Leitura de RDF</a></h2>
@@ -355,8 +355,8 @@ model.write(System.out, "N-TRIPLE");
// create an empty model
Model model = ModelFactory.createDefaultModel();
-// use the FileManager to find the input file
-InputStream in = FileManager.get().open( inputFileName );
+// use the RDFDataMgr to find the input file
+InputStream in = RDFDataMgr.open( inputFileName );
if (in == null) {
throw new IllegalArgumentException(
"File: " + inputFileName + " not found");
diff --git a/content/tutorials/sparql_datasets.html b/content/tutorials/sparql_datasets.html
index b9de541..c11c803 100644
--- a/content/tutorials/sparql_datasets.html
+++ b/content/tutorials/sparql_datasets.html
@@ -339,11 +339,6 @@ become the graph name.</p>
graph is given the name <em>url</em> and the data is read from that
location. Multiple <code>FROM NAMED</code> clauses cause multiple graphs to be
added to the dataset.</p>
-<p>Note that graphs are loaded with the Jena FileManager which
-includes the ability to provide alternative locations for files.
-For example, the query may have <code>FROM NAMED <http://example/data></code>,
-and the data actually be read from <code>file:local.rdf</code>. The name of
-the graph will be <a href="http://example/data%5C">http://example/data\</a> as in the query.</p>
<p>For example, the query to find all the triples in both default
graph and named graphs could be written as
(<a href="sparql_data/q-ds-5.rq">q-ds-5.rq</a>):</p>
diff --git a/content/tutorials/sparql_datasets_pt.html b/content/tutorials/sparql_datasets_pt.html
index 42536bb..5cc0df7 100644
--- a/content/tutorials/sparql_datasets_pt.html
+++ b/content/tutorials/sparql_datasets_pt.html
@@ -319,9 +319,6 @@ Como muitas clausulas FROM podem ser fornecidas, o dado pode ser lido de vários
mas nenhum deles se torna o nome do grafo.</p>
<p><code>FROM NAMED <i>url</i></code> é usado para identificar o grafo nomeado. Ao grafo é dado a url e o dado é lido daquela localização.
Múltiplas clausulas <code>FROM NAMED</code> causam em muitos grafos para serem adicionados ao dataset.</p>
-<p>Observe que os grafos são carregados com Jena FileManager que inclui a habilidade de prover localizações alternativas
-para os arquivos. Por exemplo, a consulta pode ter <code>FROM NAMED <http://example/data></code>,
-e o dado ser lido de <code>file:local.rdf</code>. O nome do grafo vai ser <a href="http://example/data%5C">http://example/data\</a> como na consulta.</p>
<p>Por exemplo, a consulta para buscar todas as triplas em ambos o grafo padrão e os grafos nomeados poderia ser escrita como
(<a href="sparql_data/q-ds-5.rq">q-ds-5.rq</a>):</p>
<pre><code>PREFIX xsd: <http://www.w3.org/2001/XMLSchema#>