Hi, we've been experimenting with running rdf-delta in a Docker container, which ran fine until commit [bb2f9d2f5ea61fed37d5621ec3147dd01e9b0d5b](https://github.com/afs/rdf-delta/commit/bb2f9d2f5ea61fed37d5621ec3147dd01e9b0d5b) , after which the 2.0.0-SNAPSHOT version was reverted to 1.3.0-SNAPSHOT.
As soon as we move past that, we're getting errors about a missing librocksdbjni jar when running the rdf-delta server (this is a separate issue I suppose). So in https://github.com/Kurrawong/rdf-delta-container-image/blob/enable-geosparql/Dockerfile we build the version using the commit mentioned above, which runs fine. However, when I try to enable GeoSPARQL by including a [dependency patch](https://github.com/Kurrawong/rdf-delta-container-image/blob/enable-geosparql/patches/enable-geosparql.diff#L54-L60) for rdf-delta-fuseki-server, the images still build just fine, it just doesn't actually seem to enable GeoSPARQL. (note that this approach does work with the full version of fuseki, as we do [here](https://github.com/Kurrawong/fuseki-container-image)). With the rdf-delta version, the fuseki server complains with the following error message: > the (group) Assembler > org.apache.jena.assembler.assemblers.AssemblerGroup$PlainAssemblerGroup@2e2f720 > cannot construct the object :spatial_dataset because it does not have an > implementation for the objects's most specific type geosparql:geosparqlDataset So I'm wondering if my [database config](https://github.com/Kurrawong/rdf-delta-container-image/blob/enable-geosparql/config.ttl) is wrong, or if the rdf-delta-fuseki-server package simply does not support GeoSPARQL? Thanks in advance for any insights into this! best regards, Tom
