Hello, Group. I have two questions re: the Fuseki reasoner (we’re using v.3.14.0 but the questions are, I think, version-agnostic):
1. Five or so years ago, Andy wrote<https://users.jena.apache.narkive.com/rqCd9MTM/rdfs-inference-in-fuseki-w-tdb> re: persisting entailments for performance gains that "[i]n the current codebase the only two options are using [the] in-memory reasoner or forward-chaining the data when it is loaded." Is it still the case that the reasoner can only be in-memory? 1. Via tdb2.tdbquery –explain, I was hoping to be able to be able to get some insights into how the reasoner might affect the query plan of a query against TDB2-based data, but according to this<https://users.jena.apache.narkive.com/Gq5M7ZCT/inference-on-tdbquery>, “inference results are purely in memory and not part of the TDB data.” Does this mean there’s no way to see/report the effect of the inferencer’s entailments on a given query (outside of writing Java ModelFactory code)? The task at hand is, beginning with a fairly elaborate extant ontology, prune it down to the bare minimum required by the application that’ll use it. This process will be iterative, with repeated testing of different combinations of the ontology’s extent and the right reasoner among those supported by Fuseki, e.g., OWLMicroFBRuleReasoner. Thank you. --Jeff
