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 2021/09/05 08:56:30 UTC
[jena-site] branch asf-staging updated: Staged site from jsonld11
(8c58a53b6a296c2660647db9272ff52f1a67b6dd)
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/jena-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new c928d13 Staged site from jsonld11 (8c58a53b6a296c2660647db9272ff52f1a67b6dd)
c928d13 is described below
commit c928d13a632e73796ea0dde64c85b15521d45117
Author: jenkins <bu...@apache.org>
AuthorDate: Sun Sep 5 08:56:27 2021 +0000
Staged site from jsonld11 (8c58a53b6a296c2660647db9272ff52f1a67b6dd)
---
.../documentation/geosparql/geosparql-fuseki.html | 40 ++++-
content/documentation/index.xml | 22 ++-
content/documentation/io/index.html | 2 +
.../io/{index.html => json-ld-11.html} | 173 ++++++---------------
content/documentation/shacl/index.html | 18 +--
content/index.xml | 22 ++-
content/sitemap.xml | 13 +-
7 files changed, 125 insertions(+), 165 deletions(-)
diff --git a/content/documentation/geosparql/geosparql-fuseki.html b/content/documentation/geosparql/geosparql-fuseki.html
index 357ef13..68df1e8 100644
--- a/content/documentation/geosparql/geosparql-fuseki.html
+++ b/content/documentation/geosparql/geosparql-fuseki.html
@@ -179,18 +179,38 @@
<p>This application provides a HTTP server compliant with the GeoSPARQL standard.
It uses the embedded server Fuseki and provides additional parameters for dataset loading.</p>
-<p>The project uses the GeoSPARQL implementation from the <a href="index">GeoSPARQL Jena project</a>.
-Currently, there is no GUI interface as provided in the Fuseki distribution.</p>
+<p>The project uses the GeoSPARQL implementation from the <a href="index">GeoSPARQL Jena module</a>, which includes a range of functions in addition to those from the GeoSPARQL standard.</p>
+<p>Currently, <strong>there is no GUI interface</strong> as provided in the Fuseki distribution.</p>
+<p>The intended usage is to specify a TDB folder (either TDB1 or TDB2, created if required) for persistent storage of the dataset. File loading, inferencing and data conversion operations can also be specified to load and manipulate data into the dataset. When the server is restarted these conversion operations are not required again (as they have been stored in the dataset) unless there are relevant changes. The TDB dataset can also be prepared and manipulated programatically using the [...]
+<p>Updates can be made to the dataset while the Fuseki server is running. However, these changes will not be applied to inferencing and spatial indexes until the server restarts (any default or specified spatial index file must not exists to trigger building). This is due to the current implementation of RDFS inferencing in Jena (and is required in any Fuseki server with inferencing) and the selected spatial index.</p>
<p>A subset of the EPSG spatial/coordinate reference systems are included by default from the Apache SIS project (<a href="http://sis.apache.org">http://sis.apache.org</a>).
The full EPSG dataset is not distributed due to the EPSG terms of use being incompatible with the Apache Licence.
Several options are available to include the EPSG dataset by setting the <code>SIS_DATA</code> environment variable (<a href="http://sis.apache.org/epsg.html)">http://sis.apache.org/epsg.html)</a>.</p>
-<p>It is expected that at least one Geometry Literal or Geo Predicate is present in a dataset.
+<p>It is expected that at least one Geometry Literal or Geo Predicate is present in a dataset (otherwise a standard Fuseki server can be used).
A spatial index is created and new data cannot be added to the index once built.
The spatial index can optionally be stored for future usage and needs to removed from a TDB folder if the index is to rebuilt.</p>
+<h2 id="clarifications-on-geosparql">Clarifications on GeoSPARQL</h2>
+<h3 id="geographic-markup-language-gml">Geographic Markup Language (GML)</h3>
+<p>GeoSPARQL refers to the Geographic Markup Language (GML) as one format for <code>GeometryLiterals</code>. This does not mean that GML is part of the GeoSPARQL standard. Instead a subset of geometry encodings from the GML standards are permitted (specifically the <code>GML 2.0 Simple Features Profile (10-100r3)</code> is supported by GeoSPARQL Jena). The expected encoding of data is in RDF triples and can be loaded from any RDF file format supported by Apache Jena. Conversion of GML to [...]
+<h3 id="geo-predicates-latlon">Geo Predicates Lat/Lon</h3>
+<p>Historically, geopsatial data has frequently been encoded as Latitude/Longitude coordinates in the WGS84 coordinate reference system. The GeoSPARQL standard specifically chooses not to adopt this approach and instead uses the more versatile <code>GeomtryLiteral</code>, which permits multiple encoding formats that support multiple coordinate reference systems and geometry shapes. Therefore, Lat/Lon Geo Predicates are not part of the GeoSPARQL standard. However, GeoSPARQL Jena provides [...]
+<ul>
+<li>
+<ol>
+<li>Conversion of Geo Predicates to the GeoSPARQL data structure (encoding the Lat/Lon as a Point geometry).</li>
+</ol>
+</li>
+<li>
+<ol start="2">
+<li>Spatial extension which provides property and filter functions accepting Lat/Lon arguments.</li>
+</ol>
+</li>
+</ul>
+<p>The Spatial extension functions (documented in the <a href="index">GeoSPARQL Jena module</a>) support triples in either GeoSPARQL data structure or Geo Predicates. Therefore, converting a dataset to GeoSPARQL will not lose functionality. By converting to the GeoSPARQL data structure, datasets can include a broader range of geospatial data.</p>
<h2 id="getting-started">Getting Started</h2>
<p>GeoSPARQL Fuseki can be accessed as an embedded server using Maven etc. from Maven Central or run from the command line.
SPARQL queries directly on Jena Datasets and Models can be done using
-the <a href="index">GeoSPARQL Jena project</a>.</p>
+the <a href="index">GeoSPARQL Jena module</a>.</p>
<pre><code><dependency>
<groupId>org.apache.jena</groupId>
<artifactId>fuseki-geosparql</artifactId>
@@ -293,7 +313,7 @@ Release v1.0.6 and earlier use the form “–option true”.</p>
<h3 id="5-tdb-folder">5) TDB folder</h3>
<pre><code>--tdb, -t
</code></pre>
-<p>An existing or new TDB folder used for the dataset. Default set to memory dataset.
+<p>An existing or new TDB folder used to persist the dataset. Default set to memory dataset.
If accessing a dataset for the first time with GeoSPARQL then consider the <code>--inference</code>, <code>--default_geometry</code> and <code>--validate</code> options. These operations may add additional statements to the dataset. TDB1 Dataset will be used by default, use <code>-t <folder_path> -t2</code> options for TDB2 Dataset.</p>
<h3 id="6-load-rdf-file-into-dataset">6) Load RDF file into dataset</h3>
<pre><code>--rdf_file, -rf
@@ -301,6 +321,7 @@ If accessing a dataset for the first time with GeoSPARQL then consider the <code
<p>Comma separated list of [RDF file path#graph name&RDF format] to load into dataset. Graph name is optional and will use default graph. RDF format is optional (default: ttl) or select from one of the following: json-ld, json-rdf, nt, nq, thrift, trig, trix, ttl, ttl-pretty, xml, xml-plain, xml-pretty.
e.g. <code>test.rdf#test&xml,test2.rdf</code> will load <em>test.rdf</em> file into <em>test</em> graph as <em>RDF/XML</em> and <em>test2.rdf</em> into <em>default</em> graph as <em>TTL</em>.</p>
<p>Consider the <code>--inference</code>, <code>--default_geometry</code> and <code>--validate</code> options. These operations may add additional statements to the dataset.</p>
+<p>The combination of specifying <code>-t</code> TDB folder and <code>-rf</code> loading RDF file will store the triples in the persistent TDB dataset. Therefore, loading the RDF file would only be required once.</p>
<h3 id="7-load-tabular-file-into-dataset">7) Load Tabular file into dataset</h3>
<pre><code>--tabular_file, -tf
</code></pre>
@@ -308,14 +329,17 @@ e.g. <code>test.rdf#test&xml,test2.rdf</code> will load <em>test.rdf</em> fi
e.g. <code>test.rdf#test|TAB,test2.rdf</code> will load <em>test.rdf</em> file into <em>test</em> graph as <em>TAB</em> delimited and <em>test2.rdf</em> into <em>default</em> graph as <em>COMMA</em> delimited.</p>
<p>See RDF Tables project (<a href="https://github.com/galbiston/rdf-tables">https://github.com/galbiston/rdf-tables</a>) for more details on tabular format.</p>
<p>Consider the <code>--inference</code>, <code>--default_geometry</code> and <code>--validate</code> options. These operations may add additional statements to the dataset.</p>
+<p>The combination of specifying <code>-t</code> TDB folder and <code>-tf</code> loading tabular file will store the triples in the persistent TDB dataset. Therefore, loading the tabular file would only be required once.</p>
<h3 id="8-geosparql-rdfs-inference">8) GeoSPARQL RDFS inference</h3>
<pre><code>--inference, -i
</code></pre>
<p>Enable GeoSPARQL RDFS schema and inferencing (class and property hierarchy). Inferences will be applied to the dataset. Updates to dataset may require server restart. Default: false</p>
+<p>The combination of specifying <code>-t</code> TDB folder and <code>-i</code> GeoSPARQL RDFS inference will store the triples in the persistent TDB dataset. Therefore, the GeoSPARL RDFS inference option would only be required when there is a change to the dataset.</p>
<h3 id="9-apply-hasdefaultgeometry">9) Apply hasDefaultGeometry</h3>
<pre><code>--default_geometry, -dg
</code></pre>
<p>Apply hasDefaultGeometry to single Feature hasGeometry Geometry statements. Additional properties will be added to the dataset. Default: false</p>
+<p>The combination of specifying <code>-t</code> TDB folder and <code>-dg</code> apply hasDefaultGeometry will modify the triples in the persistent TDB dataset. Therefore, applying hasDefaultGeometry would only be required when there is a change to the dataset.</p>
<h3 id="10-validate-geometry-literals">10) Validate Geometry Literals</h3>
<pre><code>--validate, -v
</code></pre>
@@ -324,10 +348,12 @@ e.g. <code>test.rdf#test|TAB,test2.rdf</code> will load <em>test.rdf</em> file i
<pre><code>--convert_geo, -c
</code></pre>
<p>Convert Geo predicates in the data to Geometry with WKT WGS84 Point GeometryLiteral. Default: false</p>
+<p>The combination of specifying <code>-t</code> TDB folder and <code>-c</code> convert Geo predicates will modify the triples in the persistent TDB dataset. Therefore, converting the Geo predicates would only be required once.</p>
<h3 id="12--remove-geo-predicates">12) Remove Geo predicates</h3>
<pre><code>--remove_geo, -rg
</code></pre>
-<p>Remove Geo predicates in the data after combining to Geometry.</p>
+<p>Remove Geo predicates in the data after combining to Geometry. Default: false</p>
+<p>The combination of specifying <code>-t</code> TDB folder and <code>-rg</code> remove Geo predicates will modify the triples in the persistent TDB dataset. Therefore, removing the Geo predicates would only be required once.</p>
<h3 id="13-query-rewrite-enabled">13) Query Rewrite enabled</h3>
<pre><code>--rewrite, -r
</code></pre>
@@ -348,7 +374,7 @@ See <a href="index">GeoSPARQL Jena project</a> for more details.</p>
<h3 id="17-spatial-index-file">17) Spatial Index file</h3>
<pre><code>--spatial_index, -si
</code></pre>
-<p>File to load or store the spatial index. Default to “spatial.index” in TDB folder if using TDB and not set. Otherwise spatial index is not stored.</p>
+<p>File to load or store the spatial index. Default to “spatial.index” in TDB folder if using TDB option and this option is not set. Otherwise spatial index is not stored and rebuilt at start up. The spatial index file must not exist for the index to be built (e.g. following changes to the dataset).</p>
<h3 id="18-properties-file">18) Properties File</h3>
<p>Supply the above parameters as a file:</p>
<pre><code>$ java Main @/tmp/parameters
diff --git a/content/documentation/index.xml b/content/documentation/index.xml
index 7523046..fb03ac7 100644
--- a/content/documentation/index.xml
+++ b/content/documentation/index.xml
@@ -147,9 +147,8 @@ The sequence from core to TDB should be executed before application components.
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://jena.apache.org/documentation/shacl/</guid>
- <description>jena-shacl is an implementation of the W3C Shapes Constraint Language (SHACL). It implements SHACL Core and SHACL SPARQL Constraints.
-In addition, it provides:
- SHACL Compact Syntax SPARQL-based targets Command line The command shacl introduces shacl operations; it takes a sub-command argument.
+ <description>jena-shacl is an implementation of the W3C Shapes Constraint Language (SHACL). It implements SHACL Core and SHACL SPARQL Constraints. It also provides a reader and writer for SHACL Compact Syntax.
+Command line The command shacl introduces shacl operations; it takes a sub-command argument.
To validate:
shacl validate --shapes SHAPES.ttl --data DATA.ttl shacl v -s SHAPES.ttl -d DATA.ttl The shapes and data files can be the same; the --shapes is optional and defaults to the same as --data.</description>
</item>
@@ -835,8 +834,9 @@ The relevant SPARQL standards are:
<guid>https://jena.apache.org/documentation/geosparql/geosparql-fuseki.html</guid>
<description>This application provides a HTTP server compliant with the GeoSPARQL standard. It uses the embedded server Fuseki and provides additional parameters for dataset loading.
-The project uses the GeoSPARQL implementation from the GeoSPARQL Jena project. Currently, there is no GUI interface as provided in the Fuseki distribution.
-A subset of the EPSG spatial/coordinate reference systems are included by default from the Apache SIS project (http://sis.apache.org). The full EPSG dataset is not distributed due to the EPSG terms of use being incompatible with the Apache Licence.</description>
+The project uses the GeoSPARQL implementation from the GeoSPARQL Jena module, which includes a range of functions in addition to those from the GeoSPARQL standard.
+Currently, there is no GUI interface as provided in the Fuseki distribution.
+The intended usage is to specify a TDB folder (either TDB1 or TDB2, created if required) for persistent storage of the dataset.</description>
</item>
<item>
@@ -1216,6 +1216,18 @@ xml:lang is fully supported, both in RDF/XML and any document embedding RDF/XML.
</item>
<item>
+ <title>Reading JSON-LD 1.1</title>
+ <link>https://jena.apache.org/documentation/io/json-ld-11.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://jena.apache.org/documentation/io/json-ld-11.html</guid>
+ <description>See &ldquo;Reading RDF&rdquo; for details of Jena&rsquo;s support JSON-LD v1.0 using the jsonld-java project for both reading and writing. This is the principle support for JSON-LD.
+This page details support for reading JSON-LD 1.1 using Titanium JSON-LD.
+While Titanium is licensed under the Apache License, it has a dependency on the Eclipse Jakarta JSON Processing API, which is licensed under the Eclipse Public License 2.0.
+Additional Dependencies The Titanium engine (com.</description>
+ </item>
+
+ <item>
<title>Reading RDF in Apache Jena</title>
<link>https://jena.apache.org/documentation/io/rdf-input.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
diff --git a/content/documentation/io/index.html b/content/documentation/io/index.html
index 9b51bb8..2f674ae 100644
--- a/content/documentation/io/index.html
+++ b/content/documentation/io/index.html
@@ -197,6 +197,8 @@ can be integrated into both the parser and writer registries.</p>
</ul>
<p>RDF/JSON is different from JSON-LD - it is a direct encoding of RDF triples in JSON.
See the <a href="rdf-json.html">description of RDF/JSON</a>.</p>
+<p>See “<a href="json-ld-11.html">Reading JSON-LD 1.1</a>” for additional setup and use for
+reading JSON-LD 1.1. JSON-LD 1.0 is the current default in Jena.</p>
<p>RDF Binary is a binary encoding of RDF (graphs and datasets) that can be useful
for fast parsing. See <a href="rdf-binary.html">RDF Binary using Apache Thrift</a>.</p>
<h2 id="command-line-tools">Command line tools</h2>
diff --git a/content/documentation/io/index.html b/content/documentation/io/json-ld-11.html
similarity index 67%
copy from content/documentation/io/index.html
copy to content/documentation/io/json-ld-11.html
index 9b51bb8..a560c02 100644
--- a/content/documentation/io/index.html
+++ b/content/documentation/io/json-ld-11.html
@@ -3,7 +3,7 @@
<head>
- <title>Apache Jena - Reading and Writing RDF in Apache Jena</title>
+ <title>Apache Jena - Reading JSON-LD 1.1</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -120,7 +120,7 @@
</ul>
</li>
- <li id="edit"><a href="https://github.com/apache/jena-site/edit/main/source/documentation/io/__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/main/source/documentation/io/json-ld-11.md" title="Edit this page on GitHub"><span class="glyphicon glyphicon-pencil"></span> Edit this page</a></li>
</ul>
</div>
</div>
@@ -137,9 +137,6 @@
-
-
-
<ol class="breadcrumb">
@@ -158,7 +155,15 @@
- <li class="active">IO</li>
+ <li><a href='/documentation/io'>IO</a></li>
+
+
+
+
+
+
+
+ <li class="active">JSON LD 11</li>
@@ -170,133 +175,43 @@
</div>
- <h1 class="title">Reading and Writing RDF in Apache Jena</h1>
+ <h1 class="title">Reading JSON-LD 1.1</h1>
- <p>This page details the setup of RDF I/O technology (RIOT).</p>
+ <p>See “<a href="./rdf-input.html">Reading RDF</a>” for details of Jena’s support JSON-LD v1.0
+using the
+<a href="https://github.com/jsonld-java/jsonld-java">jsonld-java project</a>
+for both reading and writing. This is the principle support for JSON-LD.</p>
+<p>This page details support for reading JSON-LD 1.1 using
+<a href="https://github.com/filip26/titanium-json-ld/">Titanium JSON-LD</a>.</p>
+<p>While Titanium is licensed under the Apache License, it has a dependency on
+the Eclipse Jakarta JSON Processing API, which is licensed under the Eclipse
+Public License 2.0.</p>
+<h2 id="additional-dependencies">Additional Dependencies</h2>
+<p>The Titanium engine (<code>com.apicatalog:titanium-json-ld</code>) uses the Eclispe Jakarta JSON Processing
+licnesed under the
+<a href="https://www.eclipse.org/legal/epl-2.0/">Eclipse Public License 2.0</a> with dependencies:</p>
<ul>
-<li><a href="#formats">Formats</a></li>
-<li><a href="#command-line-tools">Commands</a></li>
-<li><a href="rdf-input.html">Reading RDF in Jena</a></li>
-<li><a href="rdf-output.html">Writing RDF in Jena</a></li>
-<li><a href="streaming-io.html">Working with RDF Streams</a></li>
-<li><a href="rdfxml_howto.html">Additional details on working with RDF/XML</a></li>
+<li>jakarta.json:jakarta.json-api</li>
+<li>org.glassfish:jakarta.json</li>
</ul>
-<h2 id="formats">Formats</h2>
-<p>The following RDF formats are supported by Jena. In addition, other syntaxes
-can be integrated into both the parser and writer registries.</p>
-<ul>
-<li>Turtle</li>
-<li>RDF/XML</li>
-<li>N-Triples</li>
-<li>JSON-LD</li>
-<li>RDF/JSON</li>
-<li>TriG</li>
-<li>N-Quads</li>
-<li>TriX</li>
-<li>RDF Binary</li>
-</ul>
-<p>RDF/JSON is different from JSON-LD - it is a direct encoding of RDF triples in JSON.
-See the <a href="rdf-json.html">description of RDF/JSON</a>.</p>
-<p>RDF Binary is a binary encoding of RDF (graphs and datasets) that can be useful
-for fast parsing. See <a href="rdf-binary.html">RDF Binary using Apache Thrift</a>.</p>
-<h2 id="command-line-tools">Command line tools</h2>
-<p>There are scripts in Jena download to run these commands.</p>
-<ul>
-<li><code>riot</code> - parse, guessing the syntax from the file extension.
-Assumes N-Quads/N-Triples from stdin.</li>
-<li><code>turtle</code>, <code>ntriples</code>, <code>nquads</code>, <code>trig</code>, <code>rdfxml</code> - parse a particular language</li>
-</ul>
-<p>These can be called directly as Java programs:</p>
-<p>The file extensions understood are:</p>
-<table>
-<thead>
-<tr>
-<th> Extension </th>
-<th> Language </th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td><code>.ttl</code></td>
-<td>Turtle</td>
-</tr>
-<tr>
-<td><code>.nt</code></td>
-<td>N-Triples</td>
-</tr>
-<tr>
-<td><code>.nq</code></td>
-<td>N-Quads</td>
-</tr>
-<tr>
-<td><code>.trig</code></td>
-<td>TriG</td>
-</tr>
-<tr>
-<td><code>.rdf</code></td>
-<td>RDF/XML</td>
-</tr>
-<tr>
-<td><code>.owl</code></td>
-<td>RDF/XML</td>
-</tr>
-<tr>
-<td><code>.jsonld</code></td>
-<td>JSON-LD</td>
-</tr>
-<tr>
-<td><code>.trdf</code></td>
-<td>RDF Thrift</td>
-</tr>
-<tr>
-<td><code>.rt</code></td>
-<td>RDF Thrift</td>
-</tr>
-<tr>
-<td><code>.rj</code></td>
-<td>RDF/JSON</td>
-</tr>
-<tr>
-<td><code>.trix</code></td>
-<td>TriX</td>
-</tr>
-</tbody>
-</table>
-<p><code>.n3</code> is supported but only as a synonym for Turtle.</p>
-<p>The <a href="trix.html">TriX</a> support is for the core TriX format.</p>
-<p>In addition, if the extension is <code>.gz</code> the file is assumed to be gzip
-compressed. The file name is examined for an inner extension. For
-example, <code>.nt.gz</code> is gzip compressed N-Triples.</p>
-<p>These scripts call java programs in the <code>riotcmd</code> package. For example:</p>
-<pre><code>java -cp ... riotcmd.riot file.ttl
-</code></pre>
-<p>This can be a mixture of files in different syntaxes when file extensions
-are used to determine the file syntax type.</p>
-<p>The scripts all accept the same arguments (type <code>"riot --help"</code> to
-get command line reminders):</p>
-<ul>
-<li><code>--syntax=NAME</code>; Explicitly set the input syntax for all files.</li>
-<li><code>--validate</code>: Checking mode: same as <code>--strict --sink --check=true</code>.</li>
-<li><code>--check=true/false</code>: Run with checking of literals and IRIs either on or off.</li>
-<li><code>--time</code>: Output timing information.</li>
-<li><code>--sink</code>: No output.</li>
-<li><code>--output=FORMAT</code>: Output in a given syntax (streaming if possible).</li>
-<li><code>--formatted=FORMAT</code>: Output in a given syntax, using pretty printing.</li>
-<li><code>--stream=FORMAT</code>: Output in a given syntax, streaming (not all syntaxes can be streamed).</li>
-</ul>
-<p>To aid in checking for errors in UTF8-encoded files, there is a
-utility which reads a file of bytes as UTF8 and checks the encoding.</p>
-<ul>
-<li><code>utf8</code> – read bytes as UTF8</li>
-</ul>
-<h2 id="inference">Inference</h2>
-<p>RIOT support creation of inferred triples during the parsing
-process:</p>
-<pre><code>riotcmd.infer --rdfs VOCAB FILE FILE ...
+<p>Failure to add these dependencies will result in <code>UnsupportedOperationException</code></p>
+<pre><code>Need both titanium-json-ld (1.1.0 or later) and org.glassfish:jakarta on the classpath
+</code></pre><h2 id="usage">Usage</h2>
+<p>Jena currently (from version 4.2.0) offers both JSON-LD 1.0 and also JSON-LD 1.1.</p>
+<p>The file extension for JSONLD 1.1 is <code>.jsonld11</code>.</p>
+<p>If not reading from a file with this file extension, the application needs to
+force the language choice to be JSON-LD 1.1 with
+<a href="https://jena.apache.org/documentation/javadoc/arq/org/apache/jena/riot/RDFParser.html"><code>RDFParser</code></a>
+using <code>forceLang(Lang.JSONLD11)</code>:</p>
+<pre><code>RDFParser.source(...)
+ .forceLang(Lang.JSONLD11)
+ ...
+ .build()
+</code></pre><p>or short-cut form:</p>
+<pre><code>RDFParser.source(URL or InputStream)
+ .forceLang(Lang.JSONLD11)
+ .parse(dataset);
</code></pre>
-<p>Output will contain the base data and triples inferred based on
-RDF subclass, subproperty, domain and range declarations.</p>
-
</div>
</div>
diff --git a/content/documentation/shacl/index.html b/content/documentation/shacl/index.html
index 4370d09..6c74ac8 100644
--- a/content/documentation/shacl/index.html
+++ b/content/documentation/shacl/index.html
@@ -174,12 +174,9 @@
<p><code>jena-shacl</code> is an implementation of the
W3C <a href="https://www.w3.org/TR/shacl/">Shapes Constraint Language (SHACL)</a>.
-It implements SHACL Core and SHACL SPARQL Constraints.</p>
-<p>In addition, it provides:</p>
-<ul>
-<li><a href="https://w3c.github.io/shacl/shacl-compact-syntax/">SHACL Compact Syntax</a></li>
-<li><a href="https://w3c.github.io/shacl/shacl-af/#SPARQLTarget">SPARQL-based targets</a></li>
-</ul>
+It implements SHACL Core and SHACL SPARQL Constraints.
+It also provides a reader and writer for
+<a href="https://w3c.github.io/shacl/shacl-compact-syntax/">SHACL Compact Syntax</a>.</p>
<h2 id="command-line">Command line</h2>
<p>The command <code>shacl</code> introduces shacl operations; it takes a sub-command
argument.</p>
@@ -277,15 +274,6 @@ When outputting SHACL-C, SHACL shapes not expressible in SHACL-C will cause an
exception and data in the RDF graph that is not relevant will not be output. In
other words, SHACL-C is a lossy format for RDF.</p>
<p>The Jena SHACL-C writer will output any valid SHACL-C document.</p>
-<p>Extensions:</p>
-<ul>
-<li>The <code>constraint</code> grammar rule allows a shape reference to a node shape.</li>
-<li>The <code>propertyParam</code> grammar rule provides “group”, “order”, “name”,
-“description” and “defaultValue” to align with <code>nodeParam</code>.</li>
-<li>The <code>nodeParam</code> grammar rule supports “targetClass” (normally written
-with the shorthand <code>-></code>) as well as the defined
-“targetNode”, “targetObjectsOf”, “targetSubjectsOf”</li>
-</ul>
</div>
diff --git a/content/index.xml b/content/index.xml
index c1c217c..6e8a221 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -198,9 +198,8 @@ Download Mirrors [if-any logo] [end] The currently selected mirror is [preferred
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://jena.apache.org/documentation/shacl/</guid>
- <description>jena-shacl is an implementation of the W3C Shapes Constraint Language (SHACL). It implements SHACL Core and SHACL SPARQL Constraints.
-In addition, it provides:
- SHACL Compact Syntax SPARQL-based targets Command line The command shacl introduces shacl operations; it takes a sub-command argument.
+ <description>jena-shacl is an implementation of the W3C Shapes Constraint Language (SHACL). It implements SHACL Core and SHACL SPARQL Constraints. It also provides a reader and writer for SHACL Compact Syntax.
+Command line The command shacl introduces shacl operations; it takes a sub-command argument.
To validate:
shacl validate --shapes SHAPES.ttl --data DATA.ttl shacl v -s SHAPES.ttl -d DATA.ttl The shapes and data files can be the same; the --shapes is optional and defaults to the same as --data.</description>
</item>
@@ -895,8 +894,9 @@ The relevant SPARQL standards are:
<guid>https://jena.apache.org/documentation/geosparql/geosparql-fuseki.html</guid>
<description>This application provides a HTTP server compliant with the GeoSPARQL standard. It uses the embedded server Fuseki and provides additional parameters for dataset loading.
-The project uses the GeoSPARQL implementation from the GeoSPARQL Jena project. Currently, there is no GUI interface as provided in the Fuseki distribution.
-A subset of the EPSG spatial/coordinate reference systems are included by default from the Apache SIS project (http://sis.apache.org). The full EPSG dataset is not distributed due to the EPSG terms of use being incompatible with the Apache Licence.</description>
+The project uses the GeoSPARQL implementation from the GeoSPARQL Jena module, which includes a range of functions in addition to those from the GeoSPARQL standard.
+Currently, there is no GUI interface as provided in the Fuseki distribution.
+The intended usage is to specify a TDB folder (either TDB1 or TDB2, created if required) for persistent storage of the dataset.</description>
</item>
<item>
@@ -1390,6 +1390,18 @@ xml:lang is fully supported, both in RDF/XML and any document embedding RDF/XML.
</item>
<item>
+ <title>Reading JSON-LD 1.1</title>
+ <link>https://jena.apache.org/documentation/io/json-ld-11.html</link>
+ <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
+
+ <guid>https://jena.apache.org/documentation/io/json-ld-11.html</guid>
+ <description>See &ldquo;Reading RDF&rdquo; for details of Jena&rsquo;s support JSON-LD v1.0 using the jsonld-java project for both reading and writing. This is the principle support for JSON-LD.
+This page details support for reading JSON-LD 1.1 using Titanium JSON-LD.
+While Titanium is licensed under the Apache License, it has a dependency on the Eclipse Jakarta JSON Processing API, which is licensed under the Eclipse Public License 2.0.
+Additional Dependencies The Titanium engine (com.</description>
+ </item>
+
+ <item>
<title>Reading RDF in Apache Jena</title>
<link>https://jena.apache.org/documentation/io/rdf-input.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index d6d08e7..c890d66 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -99,7 +99,7 @@
<url>
<loc>https://jena.apache.org/documentation/shacl/</loc>
- <lastmod>2021-06-28T10:19:22+01:00</lastmod>
+ <lastmod>2021-02-19T15:39:55+13:00</lastmod>
</url>
<url>
@@ -319,7 +319,7 @@
<url>
<loc>https://jena.apache.org/documentation.html</loc>
- <lastmod>2021-06-28T10:19:22+01:00</lastmod>
+ <lastmod>2021-08-06T23:10:22+01:00</lastmod>
</url>
<url>
@@ -429,7 +429,7 @@
<url>
<loc>https://jena.apache.org/documentation/geosparql/geosparql-fuseki.html</loc>
- <lastmod>2020-10-20T20:10:23+01:00</lastmod>
+ <lastmod>2021-07-16T18:35:45+01:00</lastmod>
</url>
<url>
@@ -674,7 +674,12 @@
<url>
<loc>https://jena.apache.org/documentation/io/</loc>
- <lastmod>2021-05-08T10:08:50+01:00</lastmod>
+ <lastmod>2021-08-06T23:10:22+01:00</lastmod>
+ </url>
+
+ <url>
+ <loc>https://jena.apache.org/documentation/io/json-ld-11.html</loc>
+ <lastmod>2021-08-06T23:10:22+01:00</lastmod>
</url>
<url>