P.S. Your interface is very nice, but as Paul remarked it seems that
some of the queries are a little slow. Could you maybe rewire the SPARQL
execution to our endpoint at
It
seems to be faster. Of course, I understand if you want to use it for
your own testing, but if your main interest is in the UI and not the
backend, this might be a nice cooperation.
Cheers,
Markus
On 09.04.2015 22:16, Markus Krötzsch wrote:
On 09.04.2015 01:11, Nicola Vitucci wrote:
...
Indeed. I made this temporary change on WikiSPARQL, so that links like
in Jean-Baptiste's examples may work "properly". If you try this:
http://wikisparql.org/sparql?query=DESCRIBE+%3Chttp%3A//www.wikidata.org/en…
and then click on the external link on any property, now you should be
redirected to the "right" wiki page.
Nice, here is a query to make good use of this:
"All properties used on Wikidata to connect too humans, ordered by the
number of times that they are used in this way"
http://wikisparql.org/sparql?query=PREFIX+%3A+%3Chttp%3A%2F%2Fwww.wikidata.…
Most of the properties with less than, say, 5 uses are probably errors
(one could do other queries to find out which humans have this
particular connection).
As soon as we have the explicit links to the property entities, it will
also be possible to create the (more useful) list of property labels.
By the way, if you can control the output UI completely, you may
consider adding this: instead of a property or item URI, always display
its label (in a selected language), and merely show the URI as a tooltip
or similar. This could be done after querying with Javascript so that
people don't need to do many join+filter parts in queries just to
retrieve the labels.
Markus