Hi Holger
Thank you for confirming our hypothesis
Yes, in general we can materialize the triples, or rewrite the queries.
One use case stands: sometimes we work with structured, encoded data.
This is not the real use case, but along the lines:
subj
myCodedAttribute: "AA-xyz-1234"
which can
Correct, filtering on inferred values is very inefficient, because there is no
general "inverse" of sh:values rules.
Best to be avoided by asserting the inferences or querying the asserted triples
that are the base of the rules.
What sort of inferences do you need to query? Maybe there is a
Hi Holger, Michael,
I have a related question. In the following query:
query myQuery($id : ID, $value: String) {
myClass(
uri: $id
inferred: $value
) {
label
}
}
if "inferred" is a property with an inference rule, is it possible that the
inference
is executed for all
We have not already done this, but will give it a try.
Michael
On Monday, February 5, 2024 at 10:49:19 AM UTC-6 Holger Knublauch wrote:
> Quite possibly yes. For these properties, the engine will look both for
> asserted and inferred values.
>
> Have you tried removing the sh:values rules
Quite possibly yes. For these properties, the engine will look both for
asserted and inferred values.
Have you tried removing the sh:values rules (temporarily) and run the same
queries, comparing the execution time?
If you assert them anyway, would it make sense for you to have these sh:values
