On Sat, Oct 28, 2017 at 2:31 PM, Laura Morales <lauretas@mail.com> wrote:

> KBox is an alternative to other existing architectures for publishing KB such as SPARQL endpoints (e.g. LDFragments, Virtuoso), and Dump files.
> I should add that you can do federated query with KBox as as easier as you can do with SPARQL endpoints.

OK, but I still fail to see what is the value of this? What's the reason why I'd want to use it rather than just start a Fuseki endpoint, or use linked-fragments?

I agree that KBox is not indicated to all scenarios, rather, it fits to users that query frequently a KG,

plus do not want to spend time downloading and indexing dump files.

KBox bridge this cumbersome task, plus, it shift query execution to the client, so no scalability issues.

BTW, if you want to work with Javascript you can also simple start an local endpoint:

https://github.com/AKSW/KBox/blob/master/README.md#starting-a-sparql-endpoint

_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata