On 11.02.2016 15:01, Gerard Meijssen wrote:
What I hear is that the intentions were wrong in that you did not
anticipate people to get actual meaningful requests out of it.
When you state "we have two choices", you imply that it is my choice as
well. It is not. The answer that I am looking for is yes, it does not
function as we would like, we are working on it and in the mean time we
will ensure that toolkit is available on Labs for the more complex
Wikidata is a service and the service is in need of being better.
Gerard, do you realise how far away from technical reality your wishes
are? We are far ahead of the state of the art in what we already have
for Wikidata: two powerful live query services + a free toolkit for
batch analyses + several Web APIs for live lookups. I know of no site
of this scale that is anywhere near this in terms of functionality.
You can always ask for more, but you should be a bit reasonable too,
or people will just ignore you.
Markus and others interested in this matter,
What about using OFFSET and LIMIT to address this problem? That's what
we advice users of the DBpedia endpoint (and others we publish) to do.
We have to educate people about query implications and options. Even
after that, you have the issue of timeouts (which aren't part of the
SPARQL spec) that can be used to produce partial results (notified via
HTTP headers), but that's something that comes after the basic scrolling
functionality of OFFSET and LIMIT are understood.
Founder & CEO