Like I mentioned in the other post, I declared main:Dan as both an instance of main:Man and main:Citizen.
I also declared main:ManCitizen as an intersection of main:Man and main:Citizen.
The main issue is, the explorer is not showing the rdfs:subClassOf relation between main:ManCitizen and the main:Man and main:Citizen classes, even though if I click to see the details of main:ManCitizen or I right-click and navigate to expand node by instances, the knowledge graph is aware that main:Dan is indeed a main:ManCitizen.
At this time, Stardog Explorer supports a limited set of OWL. If developing your data model in Stardog Designer, we will support all Stardog Designer capabilities.
For the latest information on what Explorer supports, please see our documentation.
“The Model setting is limited to your Stardog Server’s reasoning schemas and allows you to specify a specific reasoning schema. By default, Explorer uses the default reasoning schema.”
And afaik, the default reasoning schema is OWL SL which supports EL and thus supports equivalence axioms.
main:Dan is in fact being inferred as an instance of main:ManCitizen, but only if I expand by instance.
Maybe I’m missing something, but, why is it properly displayed as an instance if I expand, but not being displayed as an instance visually?
The "default reasoning schema" actually refers to a named graph within your database [1]. If you're using Stardog 10, that named graph is tag:stardog:api:context:schema (whereas before it defaulted to all local graphs, including the default/no graph). If you load your ontology in there (or somewhere else with an updated reasoning.schema.graphs setting), you should see Explorer reflect it.
In that case, how could I configure my schema and my OWL profile, so that Explorer shows the inferred equivalence relations I mentioned?
Afaik, OWL SL (the default reasoning profile) supports OWL 2 EL, which in turn supports equivalence inference.
This is also confirmed when performing a SPARQL query in Stardog Studio for an inferred relationship and receiving the expected response.
The issue is present in Stardog Explorer, where the inferred relation is working for detail views, but not showing the arrows for the relationships in the canvas.