Re: a new SPARQL query engine for JavaScript

Hi.

> Exciting news! Does this support sparql 1.1 property paths? Or generalizing, which part of the sparql 1.1 spec does it support?

Property paths are not supported yet.
It wouldn’t require anything special,
just some implementation time :-)

Here’s an overview of all (un)supported operations:
https://github.com/comunica/comunica/issues/39

> Could this be used as a replacement for a graph database to support a nodejs application (with smaller graphs of course)?

Not sure if I understand your question,
but you can use it within any Node.js application:
https://github.com/comunica/comunica/tree/master/packages/actor-init-sparql#usage-within-application

Kind regards,
Ruben Taelman
On 2 June 2018 at 01:18:54, João Rocha da Silva (joaorosilva@gmail.com) wrote:

Hi,

Exciting news! Does this support sparql 1.1 property paths? Or generalizing, which part of the sparql 1.1 spec does it support?

Could this be used as a replacement for a graph database to support a nodejs application (with smaller graphs of course)?

Thanks for keeping us posted :-)

Best,
João Rocha da Silva  

Sent from my BlackBerry — the most secure mobile device

  Original Message  
From: Ruben.Verborgh@UGent.be
Sent: 1 June 2018 9:36 pm
To: public-rdfjs@w3.org
Subject: a new SPARQL query engine for JavaScript

Dear all,

Not just another SPARQL query engine,
but a pluggable query framework.

Check it out below!

Ruben

Begin forwarded message:

> From: Ruben Taelman <ruben.taelman@ugent.be>
> Subject: Comunica: a meta-query engine for the Web
> Date: 1 Jun 2018 13:37:44 GMT+2
> To: <public-lod@w3.org>
>  
> Dear all,
>  
> With this mail, we announce the public release of Comunica,
> a modular framework for JavaScript and the Web
> that can be used to compose a SPARQL Query Engine.
>  
> Comunica is a flexible query engine framework
> that allows plugging in and out different algorithms and implementations. .
> Separate modules exist for handling different SPARQL operators,
> and Comunica allows different implementations of such modules
> to be swapped in without having to change any code.
> Using semantic configuration files, Comunica can be instantiated
> into engines that use a specified set of modules.
> This is great for Web applications which only need a subset of features,
> and for research purposes, when you want to compare different algorithms.
>  
> Comunica is able to federate over heterogeneous interfaces,
> so you can execute a query over a federation of
> TPF interfaces, SPARQL endpoints, raw RDF files, etc.
> Comunica thereby acts as the successor
> of the current Linked Data Fragments client.
>  
> If you are interested in querying Linked Data on the Web,
> we invite you to try out Comunica:
> http://comunica.linkeddatafragments.org/
> or even collaborate on the development of its modules.
>  
> Comunica will be presented at the ISWC 2018 resources track.
> The corresponding article is available here:
> https://comunica.github.io/Article-ISWC2018-Resource/
>  
> Kind regards,
>  
> Ruben Taelman
> Joachim Van Herwegen
> Miel Vander Sande
> Ruben Verborgh
>  
> Some more links:
>   Documentation: http://comunica.readthedocs.io/en/latest/
>   GitHub: https://github.com/comunica/comunica
>   NPM: https://www.npmjs.com/package/@comunica/actor-init-sparql