On 4/9/15 4:24 PM, Markus Krötzsch wrote:
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 http://milenio.dcc.uchile.cl/sparql? 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
SPARQL URLs should work across SPARQL endpoints. Basically, you should only change the host part of the URL to execute the same query across different endpoints.
Examples:
1. http://lod.openlinksw.com/sparql?default-graph-uri=&query=PREFIX+%3A+%3C... -- LOD Cloud SPARQL Query Results URL
2. http://milenio.dcc.uchile.cl/sparql?default-graph-uri=&query=PREFIX+%3A+... -- Center of Semantic Web Research in Chile SPARQL Query Results URL
3. http://wikisparql.org/sparql?default-graph-uri=&query=PREFIX+%3A+%3Chttp... -- WikiSPARQL Results.
In addition to the approach above, you can use SPARQL-FED to distribute query patterns (in the SPARQL query body) across SPARQL Endpoints.
This is fundamentally what SPARQL is all about. You can use a structured query language to exploit relations across data spaces, on an HTTP network.
Kingsley
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/ent...
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.o...
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
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l