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 rules disabled for the runtime system?
>
> Holger
>
>
> On 5 Feb 2024, at 5:08 pm, Michael Panzer wrote:
>
Hi,
does anybody know if, given a sh:values rule that is materialized, the
GraphQL engine still does on-the-fly inferencing of values (even though the
triples are in the graph)?
My hunch is that it does. We are seeing very slow performance from GraphQL
queries and trying to narrow down if this
at if we allow arbitrary URI schemes, as the system would then
> basically allow any prefixed name even if no prefix is declared. The only
> solution I could think of would be for us to add a configuration option to
> enumerate the other URI schemes. Do you have a better idea?
>
> Hol
Hi,
I am currently trying to use DIDs (https://www.w3.org/TR/did-core/) as
identifiers for instances in TopBraid.
Example:
The interface complains because it interprets the did: as a prefix instead
of an URI scheme. I assume the same would happen with other URI schemes
like ark:, etc. We
