Enrico Daga

I am not sure why this is still open, I think this was handled in #246 and #248

I think this seems ready to go, I will move it to v0.8.1

[like] Enrico.Daga reacted to your message: ________________________________ From: Justin Dowdy ***@***.***> Sent: Sunday, July 28, 2024 2:01:30 PM To: SPARQL-Anything/sparql.anything ***@***.***> Cc: Enrico.Daga ***@***.***>; Author ***@***.***> Subject: Re: [SPARQL-Anything/sparql.anything] Apache...

> This makes me question the usefulness of the cache. In the case of nested service clauses, this is sufficient to avoid multiple re-engineering of the same file, the RDF...

I forgot to mention the PySPARQL-Anything setting, where multiple executions are performed within the same runtime (and probably the same execution context -- but this should be verified).

> My fear is that the system caches (which has a cost) a lot of DatasetGraphs that will be used very rarely. Indeed.

> We may disable caching by default Let's first add the option to disable it so that we can experiment with the effects. The nested query use case is quite...

Quick analysis of the general options and their influence on caching: Property | Note | Cache Key -- | -- | -- location* | The URL of the data source....

> Including the format specific ones I don't know; maybe we look at each of them and decide. I think the may issue at the moment is that BGPs are...

Normally, RDF graphs are schema-less, so the query engine does not make any assumption on existing, non-existing, or constrained properties, classes, or data types. However, this is not true for...