On 9/8/15 11:26 AM, Markus Kroetzsch wrote:
On 08.09.2015 16:48, Kingsley Idehen wrote:
On 9/8/15 8:56 AM, Markus Kroetzsch wrote:
The Wikimedia Foundation has just announced its official live query service, based on SPARQL. You can do many things with this, since the data is quite rich. Best start with some example queries, found at:
https://www.mediawiki.org/wiki/Wikibase/Indexing/SPARQL_Query_Examples
The data is based on the current content of Wikidata, so if you find an error or omission, you can directly edit it (I think there might be an update lag of about 1 min, depending on traffic).
Markus,
Great news!
A quick question, in regards to the excerpt above: can I use SPARQL query URLs against this service? In addition, can I use SPARQL FED along the following lines from other SPARQL Query service providers [1]:
select * where {service https://query.wikidata.org/ {select * where {?s a ?o} limit 10 } }
Yes, the UI we mostly advertise is not the plain SPARQL endpoint. What you want is https://query.wikidata.org/bigdata/namespace/wdq/sparql/
Your queries are [1] (text [2]) then.
Nonetheless, the recommended way to link to queries that users can then view and edit is to refer to https://query.wikidata.org like the examples do. Links to the plain endpoint query results (in various formats) should be included there. I think this is a known issue that will be fixed in due course.
Markus
[1] http://linkeddata.uriburner.com/sparql?default-graph-uri=&query=select+*...
[2] http://linkeddata.uriburner.com/sparql?default-graph-uri=&qtxt=select+*+...
Great!
One more thing, if you click on [1] and then click on the HTTP URIs in the solution, none of them resolve (bar schema.org). Is this an oversight re., Linked Data deployment?
Ideally, you want to have your SPARQL endpoint enable data exploration via HTTP URIs in the query solution, re., Linked Data.
Examples:
[1] http://id.nlm.nih.gov/mesh/query -- NIH Query Service [2] http://rdf.disgenet.org/sparql/ -- Disgenet Query Service [3] http://dbpedia.org/sparql -- DBpedia (which let's you explore via Class instances in the query solution).
Kingsley
[1] http://linkeddata.uriburner.com/sparql?default-graph-uri=&query=%0D%0Ase...
- Query
[2] http://linkeddata.uriburner.com/sparql?default-graph-uri=&qtxt=%0D%0Asel...
-- Query Text in Editor
Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
On 08.09.2015 18:22, Kingsley Idehen wrote: ...
Great!
One more thing, if you click on [1] and then click on the HTTP URIs in the solution, none of them resolve (bar schema.org). Is this an oversight re., Linked Data deployment?
Most of this should soon be fixed. The current ontology should definitely be available from http://wikiba.se/ontology soon, and it is also planned to publish archival versioned ontology files in addition.
Other URIs used in our results already do resolve, but the RDF is not up-to-date yet (see my recent question on the wikidata list). As I understand, most of this is a matter of deploying a variety of updates on a variety of server configurations on a variety of servers, so it may take a little until we have everything in place.
I don't know what the implementation status is for generated URIs like http://www.wikidata.org/value/8000228965cf554cf1baf641980f657d, since we cannot resolve them so easily. One way would be to redirect to a suitable DESCRIBE query result on the SPARQL endpoint. But this may require some more implementation work first. I think our main goal should be to have proper RDF replies for items and (all URI variants of) properties.
Markus
Ideally, you want to have your SPARQL endpoint enable data exploration via HTTP URIs in the query solution, re., Linked Data.
Examples:
[1] http://id.nlm.nih.gov/mesh/query -- NIH Query Service [2] http://rdf.disgenet.org/sparql/ -- Disgenet Query Service [3] http://dbpedia.org/sparql -- DBpedia (which let's you explore via Class instances in the query solution).
Kingsley
[1] http://linkeddata.uriburner.com/sparql?default-graph-uri=&query=%0D%0Ase...
- Query
[2] http://linkeddata.uriburner.com/sparql?default-graph-uri=&qtxt=%0D%0Asel...
-- Query Text in Editor
Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 9/8/15 12:34 PM, Markus Kroetzsch wrote:
On 08.09.2015 18:22, Kingsley Idehen wrote: ...
Great!
One more thing, if you click on [1] and then click on the HTTP URIs in the solution, none of them resolve (bar schema.org). Is this an oversight re., Linked Data deployment?
Most of this should soon be fixed. The current ontology should definitely be available from http://wikiba.se/ontology soon, and it is also planned to publish archival versioned ontology files in addition.
Other URIs used in our results already do resolve, but the RDF is not up-to-date yet (see my recent question on the wikidata list). As I understand, most of this is a matter of deploying a variety of updates on a variety of server configurations on a variety of servers, so it may take a little until we have everything in place.
I don't know what the implementation status is for generated URIs like http://www.wikidata.org/value/8000228965cf554cf1baf641980f657d, since we cannot resolve them so easily. One way would be to redirect to a suitable DESCRIBE query result on the SPARQL endpoint.
Yes, that's what's required.
But this may require some more implementation work first. I think our main goal should be to have proper RDF replies for items and (all URI variants of) properties.
If you solve the issue I am raising it will help with other data cleansing related tasks too :)
Kingsley
Markus
Ideally, you want to have your SPARQL endpoint enable data exploration via HTTP URIs in the query solution, re., Linked Data.
Examples:
[1] http://id.nlm.nih.gov/mesh/query -- NIH Query Service [2] http://rdf.disgenet.org/sparql/ -- Disgenet Query Service [3] http://dbpedia.org/sparql -- DBpedia (which let's you explore via Class instances in the query solution).
Kingsley
[1] http://linkeddata.uriburner.com/sparql?default-graph-uri=&query=%0D%0Ase...
- Query
[2] http://linkeddata.uriburner.com/sparql?default-graph-uri=&qtxt=%0D%0Asel...
-- Query Text in Editor
Dbpedia-discussion mailing list Dbpedia-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Hi!
I don't know what the implementation status is for generated URIs like http://www.wikidata.org/value/8000228965cf554cf1baf641980f657d, since we cannot resolve them so easily. One way would be to redirect to a suitable DESCRIBE query result on the SPARQL endpoint. But this may require some more implementation work first. I think our main goal should be to have proper RDF replies for items and (all URI variants of) properties.
That's an interesting idea, did not think about it this way. I'll try and see if it will work.
Hi!
One more thing, if you click on [1] and then click on the HTTP URIs in the solution, none of them resolve (bar schema.org). Is this an oversight re., Linked Data deployment?
It's not oversight in the meaning we know about it, we just didn't do it yet. See: https://phabricator.wikimedia.org/T97195