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/04/05 22:00:01 UTC
[jena-site] branch asf-site updated: Updated site from main (cd14cb23a054360efcda774f88fe8ea5dc23c33a)
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 2a2e1a192 Updated site from main (cd14cb23a054360efcda774f88fe8ea5dc23c33a)
2a2e1a192 is described below
commit 2a2e1a19216f2f68e576b16fc07b9062fa60a673
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Apr 5 21:59:58 2023 +0000
Updated site from main (cd14cb23a054360efcda774f88fe8ea5dc23c33a)
---
.../fuseki2/fuseki-server-protocol.html | 65 +++++++++++++++++-----
content/documentation/geosparql/index.html | 27 ++++++---
content/help_and_support/index.html | 2 +-
content/sitemap.xml | 10 ++--
4 files changed, 75 insertions(+), 29 deletions(-)
diff --git a/content/documentation/fuseki2/fuseki-server-protocol.html b/content/documentation/fuseki2/fuseki-server-protocol.html
index 060c408cf..971cac381 100644
--- a/content/documentation/fuseki2/fuseki-server-protocol.html
+++ b/content/documentation/fuseki2/fuseki-server-protocol.html
@@ -199,6 +199,7 @@
</ul>
</li>
<li><a href="#tasks">Tasks</a></li>
+ <li><a href="#metrics">Metrics</a></li>
</ul>
</nav>
</aside>
@@ -239,7 +240,7 @@ Further operations may be added within this naming scheme.</p>
<tr>
<td><tt>GET</tt></td>
<td><code>/$/ping</code></td>
-<td></td>
+<td>Check if server is alive</td>
</tr>
<tr>
<td><tt>POST</tt></td>
@@ -249,7 +250,7 @@ Further operations may be added within this naming scheme.</p>
<tr>
<td><tt>GET</tt></td>
<td><code>/$/server</code></td>
-<td></td>
+<td>Get basic information (version, uptime, datasets…)</td>
</tr>
<tr>
<td><tt>POST</tt></td>
@@ -257,6 +258,11 @@ Further operations may be added within this naming scheme.</p>
<td></td>
</tr>
<tr>
+<td><tt>GET</tt></td>
+<td><code>/$/status</code></td>
+<td>Alias of <code>/$/server</code></td>
+</tr>
+<tr>
<td></td>
<td></td>
<td></td>
@@ -264,32 +270,32 @@ Further operations may be added within this naming scheme.</p>
<tr>
<td><tt>POST</tt></td>
<td><code>/$/datasets</code></td>
-<td></td>
+<td>Create a new dataset</td>
</tr>
<tr>
<td><tt>GET</tt></td>
<td><code>/$/datasets</code></td>
-<td></td>
+<td>Get a list of datasets</td>
</tr>
<tr>
<td><tt>DELETE</tt></td>
<td><code>/$/datasets/{name}</code></td>
-<td></td>
+<td>Remove a dataset</td>
</tr>
<tr>
<td><tt>GET</tt></td>
<td><code>/$/datasets/{name}</code></td>
-<td></td>
+<td>Get information about a dataset</td>
</tr>
<tr>
<td><tt>POST</tt></td>
<td><code>/$/datasets/{name}?state=offline</code></td>
-<td></td>
+<td>Switch state of dataset to offline</td>
</tr>
<tr>
<td><tt>POST</tt></td>
<td><code>/$/datasets/{name}?state=active</code></td>
-<td></td>
+<td>Switch state of dataset to online</td>
</tr>
<tr>
<td></td>
@@ -299,7 +305,7 @@ Further operations may be added within this naming scheme.</p>
<tr>
<td><tt>POST</tt></td>
<td><code>/$/server/shutdown</code></td>
-<td>Not yet implemented</td>
+<td>Not implemented yet</td>
</tr>
<tr>
<td></td>
@@ -309,12 +315,12 @@ Further operations may be added within this naming scheme.</p>
<tr>
<td><tt>GET</tt></td>
<td><code>/$/stats</code></td>
-<td></td>
+<td>Get request statistics for all datasets</td>
</tr>
<tr>
<td><tt>GET</tt></td>
<td><code>/$/stats/{name}</code></td>
-<td></td>
+<td>Get request statistics for a dataset</td>
</tr>
<tr>
<td></td>
@@ -327,6 +333,11 @@ Further operations may be added within this naming scheme.</p>
<td></td>
</tr>
<tr>
+<td><tt>POST</tt></td>
+<td><code>/$/backups/{name}</code></td>
+<td>Alias of <code>/$/backup/{name}</code></td>
+</tr>
+<tr>
<td><tt>GET</tt></td>
<td><code>/$/backups-list</code></td>
<td></td>
@@ -356,6 +367,26 @@ Further operations may be added within this naming scheme.</p>
<td><code>/$/tasks/{name}</code></td>
<td></td>
</tr>
+<tr>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td><tt>GET</tt></td>
+<td><code>/$/metrics</code></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td><tt>GET</tt></td>
+<td><code>/$/logs</code></td>
+<td>Not implemented yet</td>
+</tr>
</tbody>
</table>
<h2 id="ping">Ping</h2>
@@ -363,7 +394,7 @@ Further operations may be added within this naming scheme.</p>
<p>The URL <code>/$/ping</code> is a guaranteed low cost point to test whether a server
is running or not. It returns no other information other than to respond to the
request over <code>GET</code> or <code>POST</code> (to avoid any HTTP caching) with a 200 response.</p>
-<p>Return: empty body</p>
+<p>Return: current timestamp</p>
<h2 id="server-information">Server Information</h2>
<p>Pattern: <code>/$/server</code></p>
<p>The URL <code>/$/server</code> returns details about the server and it’s current status in JSON.</p>
@@ -431,9 +462,7 @@ is known about by the server but the dataset is not attached to the server. Whe
any persistent data can be manipulated outside the server.</p>
<p>Datasets are initially “active”. The transition from “active” to “offline” is graceful - all outstanding requests are completed.</p>
<h2 id="statistics">Statistics</h2>
-<blockquote>
-<p><strong><code>/$/stats/{name}</code></strong></p>
-</blockquote>
+<p>Pattern: <code>/$/stats/{name}</code></p>
<p>Statistics can be obtained for each dataset or all datasets in a single response.
<code>/$/stats</code> is treated as a container for this information.</p>
<blockquote>
@@ -505,6 +534,11 @@ Pattern: <code>/$/tasks/{taskId}</code> – A particular task.</p>
}
]
</code></pre><p>This is inside an array to make the format returned the same as <code>/$/tasks</code>.</p>
+<h2 id="metrics">Metrics</h2>
+<p>Pattern: <code>/$/metrics</code></p>
+<blockquote>
+<p><em>@@</em></p>
+</blockquote>
</article>
@@ -535,6 +569,7 @@ Pattern: <code>/$/tasks/{taskId}</code> – A particular task.</p>
</ul>
</li>
<li><a href="#tasks">Tasks</a></li>
+ <li><a href="#metrics">Metrics</a></li>
</ul>
</nav>
</aside>
diff --git a/content/documentation/geosparql/index.html b/content/documentation/geosparql/index.html
index f3b50c994..e396da078 100644
--- a/content/documentation/geosparql/index.html
+++ b/content/documentation/geosparql/index.html
@@ -955,19 +955,30 @@ implementation based on reviewing several alternatives.</p>
<tbody>
<tr>
<td>Implements all six components of the GeoSPARQL standard.</td>
-<td>Generally partially implement the Geometry Topology and Geometry Extensions. Do not implement the Query Rewrite</td>
+<td>Generally partially implement the Geometry Topology and Geometry Extensions. Do not implement the Query Rewrite Extension.</td>
</tr>
<tr>
-<td>Extension.</td>
-<td></td>
+<td>Pure Java and does not require a supporting relational database. Configuration requires a single line of code (although Apache SIS may need some setting up, see above).</td>
+<td>Require setting up a database, configuring a geospatial extension and setting environment variables.</td>
+</tr>
+<tr>
+<td>Uses Jena, which conforms to the W3C standards for RDF and SPARQL. New versions of the standards will quickly feed through.</td>
+<td>Not fully RDF and SPARQL compliant, e.g. RDFS/OWL inferencing or SPARQL syntax. Adding your own schema may not produce inferences.</td>
+</tr>
+<tr>
+<td>Automatically determines geometry properties and handles mixed cases of units or coordinate reference systems. The GeoSPARQL standard suggests this approach but does not require it.</td>
+<td>Tend to produce errors or no results in these situations.</td>
+</tr>
+<tr>
+<td>Performs indexing and caching on-demand which reduces set-up time and only performs calculations that are required.</td>
+<td>Perform indexing in the data loading phase and initialisation phase, which can lead to lengthy delays (even on relatively small datasets).</td>
+</tr>
+<tr>
+<td>Uses JTS which does not truncate coordinate precision and applies spatial equality.</td>
+<td>May truncate coordinate precision and apply lexical equality, which is quicker but does not comply with the GeoSPARQL standard.</td>
</tr>
</tbody>
</table>
-<p>Pure Java and does not require a supporting relational database. Configuration requires a single line of code (although Apache SIS may need some setting up, see above).|Require setting up a database, configuring a geospatial extension and setting environment variables.
-Uses Jena, which conforms to the W3C standards for RDF and SPARQL. New versions of the standards will quickly feed through.|Not fully RDF and SPARQL compliant, e.g. RDFS/OWL inferencing or SPARQL syntax. Adding your own schema may not produce inferences.
-Automatically determines geometry properties and handles mixed cases of units or coordinate reference systems. The GeoSPARQL standard suggests this approach but does not require it.|Tend to produce errors or no results in these situations.
-Performs indexing and caching on-demand which reduces set-up time and only performs calculations that are required.|Perform indexing in the data loading phase and initialisation phase, which can lead to lengthy delays (even on relatively small datasets).
-Uses JTS which does not truncate coordinate precision and applies spatial equality.|May truncate coordinate precision and apply lexical equality, which is quicker but does not comply with the GeoSPARQL standard.</p>
</article>
diff --git a/content/help_and_support/index.html b/content/help_and_support/index.html
index f44852bce..ce5b6ed6b 100644
--- a/content/help_and_support/index.html
+++ b/content/help_and_support/index.html
@@ -217,7 +217,7 @@ is often enough for you to figure out the problem yourself, which is always sati
</li>
<li>
<p><strong>Don’t re-post your question</strong> after only a few hours. People are busy, and may be in a different timezone
-to you. If you’re not sure if your question made it to the list, <a href="https://markmail.org/search/?q=list:org.apache.jena.*">look in the archive</a>.</p>
+to you. If you’re not sure if your question made it to the list, <a href="https://jena.markmail.org/search/?q=-list%3Aorg.apache.incubator.jena-commits">look in the archive</a>.</p>
</li>
<li>
<p><strong>Adding lots of exclamation marks</strong> or other punctuation will <strong>not</strong> move your question up the queue. Quite the
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 8ac792ff1..0cc2f7924 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -69,7 +69,7 @@
<url>
<loc>https://jena.apache.org/documentation/geosparql/</loc>
- <lastmod>2022-08-25T11:16:58+02:00</lastmod>
+ <lastmod>2023-04-05T21:33:27+02:00</lastmod>
</url>
<url>
@@ -334,7 +334,7 @@
<url>
<loc>https://jena.apache.org/documentation.html</loc>
- <lastmod>2023-03-03T14:31:22+01:00</lastmod>
+ <lastmod>2023-04-05T21:33:27+02:00</lastmod>
</url>
<url>
@@ -404,7 +404,7 @@
<url>
<loc>https://jena.apache.org/documentation/fuseki2/fuseki-server-protocol.html</loc>
- <lastmod>2022-09-13T12:11:16+03:00</lastmod>
+ <lastmod>2023-03-13T15:18:33+01:00</lastmod>
</url>
<url>
@@ -459,7 +459,7 @@
<url>
<loc>https://jena.apache.org/help_and_support/</loc>
- <lastmod>2022-12-21T14:55:40+01:00</lastmod>
+ <lastmod>2023-04-05T21:19:02+02:00</lastmod>
</url>
<url>
@@ -484,7 +484,7 @@
<url>
<loc>https://jena.apache.org/help_and_support.html</loc>
- <lastmod>2022-12-21T14:55:40+01:00</lastmod>
+ <lastmod>2023-04-05T21:19:02+02:00</lastmod>
</url>
<url>