Hannah Bast

> Quick question here, it's hard as a user to see which features are not currently supported if they are all in a single issue. What about using a query...

@WolfgangFahl I don't think it make sense to have an issue for every minor feature that is missing at this point. Especially since the missing features come in large groups...

@WolfgangFahl I agree that the error message poorly describes what it should describe. What is should describe is that the query has two parts which are not connected. That, however,...

@WolfgangFahl QLever currently requires { ... } around subqueries. That is, the following equivalent query works: https://qlever.cs.uni-freiburg.de/wikidata/9DIJOj Background information: QLever already uses a proper parser generator (ANTLR) for a part...

@WolfgangFahl Just omit the two (...) in the VALUES clause and it works: https://qlever.cs.uni-freiburg.de/wikidata/7UCU23

@tuukka Do you have an example query? We are currently still working on full expression support. The basic machinery is in place (that was the hard part of the work),...

Ok, those are easy: 1. For the first query, you can replace `FILTER NOT EXISTS` by `MINUS`: https://qlever.cs.uni-freiburg.de/wikidata/ZuEUiK 2. For the second query, you can replace `FILTER(!BOUND(?article))` by `FILTER(?article >...

> EDIT: If a guide for porting queries from WDQS does not exist yet, that might be a nice way to document the current differences? @tuukka @WolfgangFahl @joka921 I have...

Yes, we understand and we will do that. In the meantime, let me clarify the following: 1. One can simply use `cat`, `xzcat`, or `bzcat` to pipe several files into...

@JervenBolleman Here is my log of a recent build for the complete UniProt data: https://github.com/ad-freiburg/qlever/wiki/Using-QLever-for-UniProt