You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by GitBox <gi...@apache.org> on 2021/12/27 20:38:54 UTC
[GitHub] [jena-site] kinow commented on a change in pull request #84: GeoSPARQL assembler documentation
kinow commented on a change in pull request #84:
URL: https://github.com/apache/jena-site/pull/84#discussion_r775637304
##########
File path: source/documentation/geosparql/geosparql-fuseki.md
##########
@@ -3,50 +3,86 @@ title: GeoSPARQL Fuseki
---
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 module](index), which includes a range of functions in addition to those from the GeoSPARQL standard.
+GEoSPARQL can also be ingtegrated with Fuseki using the
Review comment:
s/ingtegrated/integrated
##########
File path: source/documentation/geosparql/geosparql-fuseki.md
##########
@@ -3,50 +3,86 @@ title: GeoSPARQL Fuseki
---
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 module](index), which includes a range of functions in addition to those from the GeoSPARQL standard.
+GEoSPARQL can also be ingtegrated with Fuseki using the
+[GeoSPARQL assembler](#fuseki-assembler) with a general Fuseki server.
-Currently, **there is no GUI interface** as provided in the Fuseki distribution.
+## `jena-fuseki-geosparql` {#jena-fuseki-geosparql}
-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 Jena API.
-
-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.
+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 [GeoSPARQL Jena module](index.html).
-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.
-Several options are available to include the EPSG dataset by setting the `SIS_DATA` environment variable (http://sis.apache.org/epsg.html).
+ <dependency>
+ <groupId>org.apache.jena</groupId>
+ <artifactId>jena-fuseki-geosparql</artifactId>
+ <version>...</version>
+ </dependency>
-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.
+or download the binary from the
+[Maven central repository org/apache/jena/jena-fuseki-geosparql](https://repo1.maven.org/maven2/org/apache/jena/jena-fuseki-geosparql/)
+
+This uses the embedded server Fuseki and provides additional parameters for dataset loading.
+
+The project uses the GeoSPARQL implementation from the [GeoSPARQL Jena module](index.html), which includes a range of functions in addition to those from the GeoSPARQL standard.
+
+Currently, there is no GUI interface as provided with this server.
+
+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 Jena API.
+
+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.
+
+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. Several options are available to include the EPSG dataset
+by setting the `SIS_DATA` environment variable
+(http://sis.apache.org/epsg.html).
+
+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.
## Clarifications on GeoSPARQL
### Geographic Markup Language (GML)
-GeoSPARQL refers to the Geographic Markup Language (GML) as one format for `GeometryLiterals`. 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 `GML 2.0 Simple Features Profile (10-100r3)` 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 RDF is out of scope of the GeoSPARQL standard and Apache Jena.
-
-### Geo Predicates Lat/Lon
-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 `GeomtryLiteral`, 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 two methods to support users with geo predicates in their geosptail data.
-- 1) Conversion of Geo Predicates to the GeoSPARQL data structure (encoding the Lat/Lon as a Point geometry).
-- 2) Spatial extension which provides property and filter functions accepting Lat/Lon arguments.
+GeoSPARQL refers to the Geographic Markup Language (GML) as one format for
+`GeometryLiterals`. 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 `GML 2.0 Simple Features Profile (10-100r3)` 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 RDF is out of scope of the GeoSPARQL standard and Apache Jena.
-The Spatial extension functions (documented in the [GeoSPARQL Jena module](index)) 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.
+### Geo Predicates Lat/Lon
-## Getting Started
-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 [GeoSPARQL Jena module](index).
+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 `GeomtryLiteral`, which permits multiple encoding formats that support
Review comment:
s/`GeomtryLiteral`/`GeometryLiteral`
##########
File path: source/documentation/geosparql/geosparql-fuseki.md
##########
@@ -3,50 +3,86 @@ title: GeoSPARQL Fuseki
---
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 module](index), which includes a range of functions in addition to those from the GeoSPARQL standard.
+GEoSPARQL can also be ingtegrated with Fuseki using the
+[GeoSPARQL assembler](#fuseki-assembler) with a general Fuseki server.
-Currently, **there is no GUI interface** as provided in the Fuseki distribution.
+## `jena-fuseki-geosparql` {#jena-fuseki-geosparql}
-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 Jena API.
-
-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.
+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 [GeoSPARQL Jena module](index.html).
-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.
-Several options are available to include the EPSG dataset by setting the `SIS_DATA` environment variable (http://sis.apache.org/epsg.html).
+ <dependency>
+ <groupId>org.apache.jena</groupId>
+ <artifactId>jena-fuseki-geosparql</artifactId>
+ <version>...</version>
+ </dependency>
-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.
+or download the binary from the
+[Maven central repository org/apache/jena/jena-fuseki-geosparql](https://repo1.maven.org/maven2/org/apache/jena/jena-fuseki-geosparql/)
+
+This uses the embedded server Fuseki and provides additional parameters for dataset loading.
+
+The project uses the GeoSPARQL implementation from the [GeoSPARQL Jena module](index.html), which includes a range of functions in addition to those from the GeoSPARQL standard.
+
+Currently, there is no GUI interface as provided with this server.
+
+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 Jena API.
+
+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.
+
+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. Several options are available to include the EPSG dataset
+by setting the `SIS_DATA` environment variable
+(http://sis.apache.org/epsg.html).
+
+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.
## Clarifications on GeoSPARQL
### Geographic Markup Language (GML)
-GeoSPARQL refers to the Geographic Markup Language (GML) as one format for `GeometryLiterals`. 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 `GML 2.0 Simple Features Profile (10-100r3)` 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 RDF is out of scope of the GeoSPARQL standard and Apache Jena.
-
-### Geo Predicates Lat/Lon
-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 `GeomtryLiteral`, 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 two methods to support users with geo predicates in their geosptail data.
-- 1) Conversion of Geo Predicates to the GeoSPARQL data structure (encoding the Lat/Lon as a Point geometry).
-- 2) Spatial extension which provides property and filter functions accepting Lat/Lon arguments.
+GeoSPARQL refers to the Geographic Markup Language (GML) as one format for
+`GeometryLiterals`. 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 `GML 2.0 Simple Features Profile (10-100r3)` 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 RDF is out of scope of the GeoSPARQL standard and Apache Jena.
-The Spatial extension functions (documented in the [GeoSPARQL Jena module](index)) 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.
+### Geo Predicates Lat/Lon
-## Getting Started
-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 [GeoSPARQL Jena module](index).
+Historically, geopsatial data has frequently been encoded as Latitude/Longitude
Review comment:
s/geopsatial/geospatial
##########
File path: source/documentation/geosparql/geosparql-fuseki.md
##########
@@ -3,50 +3,86 @@ title: GeoSPARQL Fuseki
---
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 module](index), which includes a range of functions in addition to those from the GeoSPARQL standard.
+GEoSPARQL can also be ingtegrated with Fuseki using the
+[GeoSPARQL assembler](#fuseki-assembler) with a general Fuseki server.
-Currently, **there is no GUI interface** as provided in the Fuseki distribution.
+## `jena-fuseki-geosparql` {#jena-fuseki-geosparql}
-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 Jena API.
-
-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.
+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 [GeoSPARQL Jena module](index.html).
-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.
-Several options are available to include the EPSG dataset by setting the `SIS_DATA` environment variable (http://sis.apache.org/epsg.html).
+ <dependency>
+ <groupId>org.apache.jena</groupId>
+ <artifactId>jena-fuseki-geosparql</artifactId>
+ <version>...</version>
+ </dependency>
-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.
+or download the binary from the
+[Maven central repository org/apache/jena/jena-fuseki-geosparql](https://repo1.maven.org/maven2/org/apache/jena/jena-fuseki-geosparql/)
+
+This uses the embedded server Fuseki and provides additional parameters for dataset loading.
+
+The project uses the GeoSPARQL implementation from the [GeoSPARQL Jena module](index.html), which includes a range of functions in addition to those from the GeoSPARQL standard.
+
+Currently, there is no GUI interface as provided with this server.
+
+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 Jena API.
+
+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.
+
+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. Several options are available to include the EPSG dataset
+by setting the `SIS_DATA` environment variable
+(http://sis.apache.org/epsg.html).
+
+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.
## Clarifications on GeoSPARQL
### Geographic Markup Language (GML)
-GeoSPARQL refers to the Geographic Markup Language (GML) as one format for `GeometryLiterals`. 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 `GML 2.0 Simple Features Profile (10-100r3)` 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 RDF is out of scope of the GeoSPARQL standard and Apache Jena.
-
-### Geo Predicates Lat/Lon
-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 `GeomtryLiteral`, 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 two methods to support users with geo predicates in their geosptail data.
-- 1) Conversion of Geo Predicates to the GeoSPARQL data structure (encoding the Lat/Lon as a Point geometry).
-- 2) Spatial extension which provides property and filter functions accepting Lat/Lon arguments.
+GeoSPARQL refers to the Geographic Markup Language (GML) as one format for
+`GeometryLiterals`. 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 `GML 2.0 Simple Features Profile (10-100r3)` 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 RDF is out of scope of the GeoSPARQL standard and Apache Jena.
-The Spatial extension functions (documented in the [GeoSPARQL Jena module](index)) 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.
+### Geo Predicates Lat/Lon
-## Getting Started
-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 [GeoSPARQL Jena module](index).
+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 `GeomtryLiteral`, 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 two methods to support users with geo predicates in their geospatial
+data.
- <dependency>
- <groupId>org.apache.jena</groupId>
- <artifactId>fuseki-geosparql</artifactId>
- <version>...</version>
- </dependency>
+1. Conversion of Geo Predicates to the GeoSPARQL data structure (encoding the Lat/Lon as a Point geometry).
+2. Spatial extension which provides property and filter functions accepting Lat/Lon arguments.
-or download the binary from the
-[Maven central repository org/apache/jena/jena-fuseki-geosparql](http://central.maven.org/maven2/org/apache/jena/jena-fuseki-geosparql/)
+The Spatial extension functions (documented in the [GeoSPARQL Jena module](index)) 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.
Review comment:
>documented in the [GeoSPARQL Jena module](index))
Does it need to be index.html here?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org