I noticed the following bug/behavior in Stardog which is related to IRI
When the IRI has a "/" before the "#" it is causing unusual response time when the reasoning is activated by query.
Any ideas what is going on?
example-ok.rdf (18.0 KB)
example.rdf (18.1 KB)
select ?a ?Name
?a a <http://www.example.com#PhysicalLocation>.
?a <http://www.example.com#hasName> ?Name. }
Do you have some data that you could share that would reproduce the problem? Can you include the two query plans? (
stardog query explain)
Unfortunatly I can’t share the data, but you can try it out on any data set you have
change the ontology namespace to “/#” by adding an extra “/” before the “#”
You will see during inference, there is a lot of delay compared to when there is no extra “/” before the “#”.
There is nothing in reasoning that is sensitive to the characters inside IRIs. Different IRIs would change hashcodes and iteration order for some internal operations but it is unlikely to have a significant difference due to that.
Is it possible that making the change in the IRIs changes how definitions in your ontology interact with each other or with the instances? If you can share the query plans for the slow and fast versions that would help us to understand what might be wrong.