Bart Hanssens

Finding a well-supported Java library for ODF, with a suitable license can be a problem (ODF Toolkit ODFDOM-API is the best bet IMHO) Luckily ODF is easier to produce than...

Could also be interesting for signing RDF graphs ...

FWIW it is unfortunately a known limitation of the BeST-Address source: we only get geo-coordinates for addresses from the official sources of the 3 Regions, not for streets (for which...

Several options I guess, e.g. - try to use Spring Boot to generate a fat jar - or replace the current Spring thingies with e.g. something implementing Eclipse MicroProfile -...

(yet) another somewhat related idea from the gitter chat: using jetty instead of tomcat for the war (https://www.baeldung.com/deploy-to-jetty)

GraalVM starts to look a bit more interesting since Oracle is contributing the community edition to openjdk, and Spring (6 ?) is actively working on fully supporting it. That being...

Well, you could use embedded Jetty for the server (workbench has an issue with 10/11/12, server should work IMHO) or something microprofile-based, but nowadays springboot-in-a-docker-in-the-cloud seems to be "the" way...

Hmz, what about keeping the name of setting, but just make it a plain Object instead of a com.github.jsonldjava.core.DocumentLoader ? That way both the old and the new JSON-LD parser...

Also the other way round: the shacl/dcat-ap-SHACL explicitly checks if e.g. accessURL is an rdfs:Resource, while the html/shacl/shapes.ttl does not (nor does html/shacl/ranges.ttl)

Well, I also prefer separate files, but one big file is also fine with me... But at least the results should be the same :-)