SEARCH: drop the search API

[jacoscaz]

Assuming we choose to follow through with #103, the SEARCH API would become a redundant, less-powerful alternative to the SPARQL API. It wouldn't make sense to keep it around.

[gsvarovsky]

Actually the search API might be very useful to me.

The reason is, my project has a json-rql interface. It looks like it would be better for me to use your search API directly, rather than translating first to SPARQL.

I will try to investigate as soon as possible. When do you anticipate doing this work?

[jacoscaz]

@gsvarovsky interesting! I'm still brainstorming on this and I am really happy to get some community feedback.

Consider that the work on the SPARQL API will bring support for SPARQL queries expressed both as SPARQL strings and as SPARQL Algebra objects (see https://www.npmjs.com/package/sparqlalgebrajs). From the looks of it, converting a JSON RQL query to a SPARQL Algebra object should not be any more difficult than converting the same query to use with quadstore's Search API.

What do you think? I would otherwise be happy to figure out how to keep the search API around.

[gsvarovsky]

You are right, using the algebra will be just as good as the current search API, probably even better. Thanks!

[jacoscaz]

No worries! Thank you for mentioning JSON RQL, I wasn't aware of it. I will come back to this issue in a while, once work on SPARQL continues.

[jacoscaz]

Released on NPM - quadstore@7.0.1-alpha.9