You are correct, enabling reasoning locally will cause an issue, similar to how it was describe in this post: Behaviour with federation and reasoning.
A workaround was to ask the service to do the reasoning remotely. Let re-use the queries in my previous post.
If I do a virtual import in database example3, I can use the following
SELECT *
{
{
SERVICE <http://admin:admin@localhost:5820/example3/query/reasoning> {
?s a vcard:Individual
}
}
}
Reasoning works because I added /reasoning at the end of my service endpoint. It done on the remote endpoint but that fine.
My question is, is there a way to achieve the same thing within a virtual add graph? I understand the performance would probably be impacted, but only looking at using T-box type of inferencing.
no worries, Was hoping there an undocumented option.