One thing I really liked about Kasabi was that it had a simple interface for people to enter queries and share them with people.  The "Information Workbench" from fluidOps does something similar although I never seen it open to the public.  A database of queries also is a great tool for testing both the code and the documentation,  both of the reference and cookbook kind.

I see no reason why one instance of Blazegraph is having all the fun.  With a good RDF dump,  people should be loading Wikidata into all sorts of triple stores and since Wikidata is not that terribly big at this time,  "alternative" endpoints ought to be cheap and easy to run

On Mon, Oct 26, 2015 at 11:31 AM, Kingsley Idehen <> wrote:
On 10/25/15 10:51 AM, James Heald wrote:
Hi Gerard.  Blazegraph is the name of the open-source SPARQL engine being used to provide the Wikidata SPARQL service.

So Blazegraph *is* available to all of us, at , via both the query editor, and the SPARQL API endpoint.

It's convenient to talk describe some issues with the SPARQL service being "Blazegraph issues", if the issues appear to lie with the query engine.

Other query engines that other people be running might be running might have other specific issues, eg "Virtuoso issues".  But it is Blazegraph that the Discovery team and Wikidata have decided to go with.

The beauty of SPARQL is that you can use URLs to show query results (and even query definitions). Ultimately, engine aside, there is massive utility in openly sharing queries and then determining what might the real problem.

Let's use open standards to work in as open a fashion as is possible.


Kingsley Idehen	      
Founder & CEO 
OpenLink Software     
Company Web:
Personal Weblog 1:
Personal Weblog 2:
Twitter Profile:
Google+ Profile:
LinkedIn Profile:
Personal WebID:

Wikidata mailing list

Paul Houle

Applying Schemas for Natural Language Processing, Distributed Systems, Classification and Text Mining and Data Lakes

(607) 539 6254    paul.houle on Skype

:BaseKB -- Query Freebase Data With SPARQL

Legal Entity Identifier Lookup

Join our Data Lakes group on LinkedIn