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 2023/01/03 12:25:18 UTC
[jena-site] branch asf-site updated: Updated site from main (97ca20b8184f5594f5874ff769491351f7e0e25b)
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 09298a19b Updated site from main (97ca20b8184f5594f5874ff769491351f7e0e25b)
09298a19b is described below
commit 09298a19bdf1f0bd87b6a7ff58b02a37173c0490
Author: jenkins <bu...@apache.org>
AuthorDate: Tue Jan 3 12:25:14 2023 +0000
Updated site from main (97ca20b8184f5594f5874ff769491351f7e0e25b)
---
.../fuseki2/fuseki-server-protocol.html | 7 +++++
content/documentation/index.xml | 22 ++++++++--------
content/documentation/io/rdf-input.html | 30 ++++++++++++++++++++--
content/documentation/query/lateral-join.html | 12 ++++++---
.../rdf-patch/{__index.html => index.html} | 22 +++++-----------
content/index.xml | 22 ++++++++--------
content/sitemap.xml | 18 ++++++-------
7 files changed, 81 insertions(+), 52 deletions(-)
diff --git a/content/documentation/fuseki2/fuseki-server-protocol.html b/content/documentation/fuseki2/fuseki-server-protocol.html
index 54c1aaf2c..535c4aa2e 100644
--- a/content/documentation/fuseki2/fuseki-server-protocol.html
+++ b/content/documentation/fuseki2/fuseki-server-protocol.html
@@ -433,6 +433,13 @@ See <a href="fuseki-server-info.html">Fuseki Server Information</a> for details
useful for managing the files externally.</p>
<p>The returned JSON object will have the form <code>{ backups: [ ... ] }</code> where the <code>[]</code> array is
a list of file names.</p>
+<p>Since 4.7.0 backups are written to a temporary file in the same directory and renamed on completion.
+In case of server crash, it will not be renamed.
+This guarantees backups are complete.
+Cleanup of incomplete backups can be done by users on application / container start: remove all incomplete files.g</p>
+<h3 id="backup-policies">Backup policies</h3>
+<p>Users can use the backup api <a href="/documentation/fuseki2/fuseki-server-protocol.html#backup">the Fuseki HTTP Administration Protocol</a> to build backup policies.
+See issue for more information <a href="https://github.com/apache/jena/issues/1500">https://github.com/apache/jena/issues/1500</a> .</p>
<h3 id="compact">Compact</h3>
<p>Pattern: <code>/$/compact/{name}</code></p>
<p>This operations initiates a database compaction task and returns a JSON object with the task Id in it.</p>
diff --git a/content/documentation/index.xml b/content/documentation/index.xml
index a42400a98..991e9db9a 100644
--- a/content/documentation/index.xml
+++ b/content/documentation/index.xml
@@ -10,17 +10,6 @@
<atom:link href="https://jena.apache.org/documentation/index.xml" rel="self" type="application/rss+xml" />
- <item>
- <title></title>
- <link>https://jena.apache.org/documentation/rdf-patch/__index.html</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://jena.apache.org/documentation/rdf-patch/__index.html</guid>
- <description>f&mdash; title: RDF Patch slug: index This page describes RDF Patch. An RDF Patch is a set of changes to an RDF dataset. The change are for triples, quads and prefixes.
-Changes to triples involving blank nodes are handled by using their system identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank nodes are not generated afresh each time the document is parsed.
-Example This example ensures certain prefixes are in the dataset and adds some basic triples for a new subclass of &lt;http://example/SUPER_CLASS&gt;.</description>
- </item>
-
<item>
<title>A brief guide to Jena Eyeball</title>
<link>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</link>
@@ -1276,6 +1265,17 @@ Binary formats are faster to process - they do not incur the parsing costs of te
Outline RDFConnection provides a number of different styles for working with RDF data in Java.</description>
</item>
+ <item>
+ <title>RDF Patch</title>
+ <link>https://jena.apache.org/documentation/rdf-patch/</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://jena.apache.org/documentation/rdf-patch/</guid>
+ <description>This page describes RDF Patch. An RDF Patch is a set of changes to an RDF dataset. The change are for triples, quads and prefixes.
+Changes to triples involving blank nodes are handled by using their system identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank nodes are not generated afresh each time the document is parsed.
+Example This example ensures certain prefixes are in the dataset and adds some basic triples for a new subclass of &lt;http://example/SUPER_CLASS&gt;.</description>
+ </item>
+
<item>
<title>RDF/XML Handling in Jena</title>
<link>https://jena.apache.org/documentation/io/arp.html</link>
diff --git a/content/documentation/io/rdf-input.html b/content/documentation/io/rdf-input.html
index c18d03324..a0176db05 100644
--- a/content/documentation/io/rdf-input.html
+++ b/content/documentation/io/rdf-input.html
@@ -460,15 +460,41 @@ this is useful when you don’t want to go to the trouble of writing a full
logic in normal iterator style.</p>
<p>To do this you use <code>AsyncParser.asyncParseTriples</code> which parses the input on
another thread:</p>
-<pre><code> Iterator<Triple> iter = AsyncParser.asyncParseTriples(filename);
+<pre><code> IteratorCloseable<Triple> iter = AsyncParser.asyncParseTriples(filename);
iter.forEachRemaining(triple->{
// Do something with triple
});
</code></pre>
-<p>For N-Triples and N-Quads, you can use
+<p>Calling the iterator’s close method stops parsing and closes the involved resources.
+For N-Triples and N-Quads, you can use
<code>RiotParsers.createIteratorNTriples(input)</code> which parses the input on the
calling thread.</p>
<p><a href="https://github.com/apache/jena/blob/main/jena-examples/src/main/java/arq/examples/riot/ExRIOT9_AsyncParser.java">RIOT example 9</a>.</p>
+<p>Additional control over parsing is provided by the <code>AsyncParser.of(...)</code> methods which return <code>AsyncParserBuilder</code> instances.
+The builder features a fluent API that allows for fine-tuning internal buffer sizes as well as eventually obtaining
+a standard Java <code>Stream</code>. Calling the stream’s close method stops parsing and closes the involved resources.
+Therefore, these streams are best used in conjunction with try-with-resources blocks:</p>
+<pre><code> try (Stream<Triple> stream = AsyncParser.of(filename)
+ .setQueueSize(2).setChunkSize(100).streamTriples().limit(1000)) {
+ // Do something with the stream
+ }
+</code></pre>
+<p>The AsyncParser also supports parsing RDF into a stream of <code>EltStreamRDF</code> elements. Each element can hold a triple, quad, prefix, base IRI or exception.
+For all <code>Stream</code>-based methods there also exist <code>Iterator</code>-based versions:</p>
+<pre><code> IteratorCloseable<EltStreamRDF> it = AsyncParser.of(filename).asyncParseElements();
+ try {
+ while (it.hasNext()) {
+ EltStreamRDF elt = it.next();
+ if (elt.isTriple()) {
+ // Do something with elt.getTriple();
+ } else if (elt.isPrefix()) {
+ // Do something with elt.getPrefix() and elt.getIri();
+ }
+ }
+ } finally {
+ Iter.close(it);
+ }
+</code></pre>
<h3 id="filter-the-output-of-parsing">Filter the output of parsing</h3>
<p>When working with very large files, it can be useful to
process the stream of triples or quads produced
diff --git a/content/documentation/query/lateral-join.html b/content/documentation/query/lateral-join.html
index ead2401f9..309487df0 100644
--- a/content/documentation/query/lateral-join.html
+++ b/content/documentation/query/lateral-join.html
@@ -251,7 +251,10 @@ inner <code>?s</code> is not joined to the outer <code>?s</code> but instead is
</code></pre><p>The inner <code>?s</code> in the <code>SELECT ?label</code> is not the outer <code>?s</code> because the <code>SELECT ?label</code> does not pass out <code>?s</code>. As a sub-query the <code>?s</code> could be any name except
<code>?label</code> for the same results.</p>
<h3 id="notes">Notes</h3>
-<p>There is a similarity to filter <code>NOT EXISTS</code>/<code>EXISTS</code> expressed as the non-legal <code>FILTER ( ASK { pattern } )</code> where the variables of the row being filtered are available to “pattern”. This is similar to an SQL <a href="https://en.wikipedia.org/wiki/Correlated_subquery">correlated subquery</a>.</p>
+<p>There is a similarity to filter <code>NOT EXISTS</code>/<code>EXISTS</code> expressed as the non-legal
+<code>FILTER ( ASK { pattern } )</code> where the variables of the row being filtered are
+available to “pattern”. This is similar to an SQL
+<a href="https://en.wikipedia.org/wiki/Correlated_subquery">correlated subquery</a>.</p>
<h2 id="sparql-specification-additional-material">SPARQL Specification Additional Material</h2>
<h3 id="syntax-1">Syntax</h3>
<p><code>LATERAL</code> is added to the SPARQL grammar at rule <code>[[56] GraphPatternNotTriples](https://www.w3.org/TR/sparql11-query/#rGraphPatternNotTriples)</code>. As a syntax form, it is similar to <code>OPTIONAL</code>.</p>
@@ -289,9 +292,10 @@ Lateral(Ω, P) = { μ | union of Ω1 where
Ω1 = eval(D(G), pattern2)
result Ω1
}
-</code></pre><p>where <code>inject</code> is the <a href="https://afs.github.io/substitute.html">corrected <code>substitute</code></a> operation.</p>
-<p>An alternative style is to define Lateral more like “evaluate P such that μ is in-scope” in some
-way, rather than rely on <code>inject</code> which is a mechanism.</p>
+</code></pre><p>where <code>inject</code> is the <a href="https://afs.github.io/substitute.html">corrected <code>substitute</code></a>
+operation.</p>
+<p>An alternative style is to define Lateral more like “evaluate P such that μ is
+in-scope” in some way, rather than rely on <code>inject</code> which is a mechanism.</p>
<pre><code>Definition: Evaluation of Lateral
eval(D(G), Lateral(P1, P2) = Lateral(eval(D(G), P1), P2)
diff --git a/content/documentation/rdf-patch/__index.html b/content/documentation/rdf-patch/index.html
similarity index 97%
rename from content/documentation/rdf-patch/__index.html
rename to content/documentation/rdf-patch/index.html
index ea17419d1..2da1b1554 100644
--- a/content/documentation/rdf-patch/__index.html
+++ b/content/documentation/rdf-patch/index.html
@@ -3,7 +3,7 @@
<head>
- <title>Apache Jena - </title>
+ <title>Apache Jena - RDF Patch</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -142,6 +142,9 @@
+
+
+
<ol class="breadcrumb">
@@ -160,15 +163,7 @@
- <li><a href='/documentation/rdf-patch'>RDF PATCH</a></li>
-
-
-
-
-
-
-
- <li class="active">INDEX</li>
+ <li class="active">RDF PATCH</li>
@@ -180,12 +175,9 @@
</div>
- <h1 class="title"></h1>
+ <h1 class="title">RDF Patch</h1>
- <h2 id="slug-index">f—
-title: RDF Patch
-slug: index</h2>
-<p>This page describes RDF Patch. An RDF Patch is a set of changes to an
+ <p>This page describes RDF Patch. An RDF Patch is a set of changes to an
<a href="https://www.w3.org/TR/rdf11-concepts/#section-dataset">RDF dataset</a>.
The change are for triples, quads and prefixes.</p>
<p>Changes to triples involving blank nodes are handled by using their system
diff --git a/content/index.xml b/content/index.xml
index 3f91493e4..4f8ac74b6 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -10,17 +10,6 @@
<atom:link href="https://jena.apache.org/index.xml" rel="self" type="application/rss+xml" />
- <item>
- <title></title>
- <link>https://jena.apache.org/documentation/rdf-patch/__index.html</link>
- <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
-
- <guid>https://jena.apache.org/documentation/rdf-patch/__index.html</guid>
- <description>f&mdash; title: RDF Patch slug: index This page describes RDF Patch. An RDF Patch is a set of changes to an RDF dataset. The change are for triples, quads and prefixes.
-Changes to triples involving blank nodes are handled by using their system identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank nodes are not generated afresh each time the document is parsed.
-Example This example ensures certain prefixes are in the dataset and adds some basic triples for a new subclass of &lt;http://example/SUPER_CLASS&gt;.</description>
- </item>
-
<item>
<title>A brief guide to Jena Eyeball</title>
<link>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</link>
@@ -1443,6 +1432,17 @@ Binary formats are faster to process - they do not incur the parsing costs of te
Outline RDFConnection provides a number of different styles for working with RDF data in Java.</description>
</item>
+ <item>
+ <title>RDF Patch</title>
+ <link>https://jena.apache.org/documentation/rdf-patch/</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://jena.apache.org/documentation/rdf-patch/</guid>
+ <description>This page describes RDF Patch. An RDF Patch is a set of changes to an RDF dataset. The change are for triples, quads and prefixes.
+Changes to triples involving blank nodes are handled by using their system identifier which uniquely identifies a blank node. Unlike RDF syntaxes, blank nodes are not generated afresh each time the document is parsed.
+Example This example ensures certain prefixes are in the dataset and adds some basic triples for a new subclass of &lt;http://example/SUPER_CLASS&gt;.</description>
+ </item>
+
<item>
<title>RDF/XML Handling in Jena</title>
<link>https://jena.apache.org/documentation/io/arp.html</link>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 652ffd822..58d201715 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -2,11 +2,6 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
- <url>
- <loc>https://jena.apache.org/documentation/rdf-patch/__index.html</loc>
- <lastmod>2022-11-16T13:22:32+00:00</lastmod>
- </url>
-
<url>
<loc>https://jena.apache.org/documentation/archive/eyeball/eyeball-guide.html</loc>
<lastmod>2020-06-28T16:59:07+01:00</lastmod>
@@ -199,7 +194,7 @@
<url>
<loc>https://jena.apache.org/documentation/query/lateral-join.html</loc>
- <lastmod>2022-11-21T20:29:57+00:00</lastmod>
+ <lastmod>2023-01-03T12:22:38+00:00</lastmod>
</url>
<url>
@@ -339,7 +334,7 @@
<url>
<loc>https://jena.apache.org/documentation.html</loc>
- <lastmod>2022-11-21T20:29:57+00:00</lastmod>
+ <lastmod>2023-01-03T12:22:38+00:00</lastmod>
</url>
<url>
@@ -409,7 +404,7 @@
<url>
<loc>https://jena.apache.org/documentation/fuseki2/fuseki-server-protocol.html</loc>
- <lastmod>2022-07-27T16:28:14+02:00</lastmod>
+ <lastmod>2022-09-13T12:11:16+03:00</lastmod>
</url>
<url>
@@ -697,6 +692,11 @@
<lastmod>2022-06-15T14:52:32+02:00</lastmod>
</url>
+ <url>
+ <loc>https://jena.apache.org/documentation/rdf-patch/</loc>
+ <lastmod>2023-01-03T12:22:38+00:00</lastmod>
+ </url>
+
<url>
<loc>https://jena.apache.org/documentation/io/arp.html</loc>
<lastmod>2020-02-28T13:09:12+01:00</lastmod>
@@ -714,7 +714,7 @@
<url>
<loc>https://jena.apache.org/documentation/io/rdf-input.html</loc>
- <lastmod>2022-08-26T15:49:37+01:00</lastmod>
+ <lastmod>2022-08-24T16:11:32+02:00</lastmod>
</url>
<url>