Open Sparql endpoint for external access (Comunica, LDKit)

Support
1

Currently we are building a nodejs (typescript) backend using the stardog SDK to run queries on a stardog database. For the time being, we are building the queries manually (assisted with [LDFlex](GitHub - LDflex/LDflex: A JavaScript DSL for querying Linked Data on the Web to prevent sparql injection attacks). We want to abstract the data layer using LDKit (dto alike) to facilitate development (we are using stardog as an operational database on our experiment) but I have not been able to connect a stardog sparql endpoint in the context to let LDKit run the queries. Is there any way to make it happen or I am limited to the rest API and the stardog SDK to run sparql queries? Are third parties going to be able to run queries through tools like Comunica without having to use the REST API?

Thanks!

2

I feel a little awkward replying to your post w/o any sort of answer .. but I wanted to thank you for the interesting references.

I think that these forums are often as much about spreading knowledge and stimulating ideas as they are about answering questions.

3

I've been able to send SPARQL queries to a stardog free endpoint by creating a new user, giving them the cloud and reader roles, and then using that new user's user/pass as credentials to send the SPARQL queries to an endpoint that looks like:

<ENDPOINT_URL>/<DATABASE_NAME>/query

Such as:

https://sd-8675309.stardog.cloud:5820/DBName/query

But I could not authenticate using my "account credentials", I had to create the new user, associate the roles, in the Studio Security tab

4

Thanks. Just in case I managed to connect it to the [host]/[database]/query endpoint. Sadly, LDKit only works with rdf+json and stardog does not support it as an accepted endpoint response. I will work on doing the manual mapping, will post a follow up if I manage to make it work.

5

Thank you! It is indeed the way to make it. It also works with Comunica and LDLink, but for the second one it needs some workaround to handle the incompatible response format (rdf+json vs stardog supported types). It also needs an additional workaround as query and update/post endpoints are different.

6

As a follow up, managed to make it work. Changed the query engine to Comunica, and set up the context in the following way:


        const context: Context = {
            sources: [
                {
                    type: "sparql",
                    value: "https://sd-xxxxx.stardog.cloud:5820/databasename/query",
                },
            ],
            httpAuth:
                "user:password",
        };

Can confirm it works for reading, writing, updating and deleting. I cannot express how much this helps our codebase and development. Highly recommended!

7

Hello! I am the author and maintainer of LDkit.

I have recently released LDkit 2.0 which supports text/turtle RDF serialization out of the box, so now it should be possible to connect to Stardog without the Comunica intermediary. Beware, since it is a major release, I have made some improvements to interfaces, it is not fully backward compatible, but only some minor changes are needed in existing code.

Thank you for your interest in the library! If you have any additional feedback or suggestions for improvements, please let me know.

8

Looks interesting. I'll add that to GitHub - semantalytics/awesome-semantic-web: A curated list of various semantic web and linked data resources.

It's not exactly clear what this is but it might make sense to someone familiar with linkage disequibrium. When I see LD I keep thinking Linked Data. Where is RDF being used? Does it output RDF?