geograpy3 queries as "real world" example

[WolfgangFahl]

see somnathrakshit/geograpy3#48

[WolfgangFahl]

see https://github.com/somnathrakshit/geograpy3/blob/5973e2df1f856b238c88701cd508ff7f6593c338/geograpy/wikidata.py#L79

[joka921]

Hi,
You have posted another github thread which seems to be a discussion about whether some other software should support other languages than german, and some python script. Could you please elaborate how this is connected to QLever and what the concrete issue with Qlever is here?

[WolfgangFahl]

@joka921 -there are some concrete SPARQL queries in the source code that need to be checked for compatibilty with the QLever engine. To make this easier we'll externalize the queries as "named queries" so that they can be easiliy tested e.g. with the sparqlquery command line feature of pyLodStorage. This is IMHO a good example for how systematic tests for SPARQL compatbility in projects that could potentially use QLever could be implemented. E.g. if this is successfull the CI of geograpy3 would run this test nightly/regularly.

[WolfgangFahl]

I'all also document the concrete queries here as part of working on this issue .

[joka921]

So is your issue something like the following:
"geography3 is a system that does describe the useful work and internally uses SPARQL queries on Wikidata. Here is a list of Queries that geography3 uses, but which are currently not supported by QLever.
As soon as QLever supports these queries, it can be used as the backend of geography3 with possibly great performance benefits.

[WolfgangFahl]

yes -it is even the case that the queries currently timeout since the timeout setting of the wikidata query service have been set more tightly. We have trouble getting cities into the query that are referenced via hierarchy levels > 5 that is e.g. england and bavaria.

[joka921]

I will close this for now as there is no concrete request to the QLever team. You have stated on multiple occasions that you want to create a set of queries that are relevant for your own projects and systematically test, which of them work on QLever, and then send us a list, or break the failing ones down to minimal cases to find out, which of the bugs have already been reported in the #614 issue.