Stardog v5 and up have separate read and write endpoint about ld-r

[ali1k]

thanks @mathib
I updated the SPARQL query APIs to use /query for selection queries and /update for update queries. It is still compatible with /annex one though.

[ali1k]

I updated the Stardog sample config since they seem to have updated their endpoint URL. Can you try to use /annex/testDB/sparql/query as your path and see if update queries would work?

[mathib]

It works, thanks! My bad, because I overlooked those comments in the server.js config... Awesome framework :)

Do you know what the difference is when using this alternative path? I could not find anything about this in the Stardog manual. Besides that, are there options to connect to a stardog db, when it is running locally but with authentication (a user should login with a pw)? If I try it now, the web UI says:

There was no resource in the selected dataset! This might be due to the connection problems or because the estimated query execution time exceeds the configured limit. Please check the connection parameters of your dataset's Sparql endpoint or add resources to your dataset...

[ali1k]

good that it worked!
I don't know exactly what the difference it. It seems they have changed their APIs. At the moment, there is no support for endpoints with authentication. It is on our todo list.

[mathib]

@ali1k : I've asked to the Stardog community, how this will evolve and they said that /annex/testDB/sparql/query will be depreciated in next versions: https://community.stardog.com/t/stardog-sparql-endpoints/814/2

The workflow of LD-R should maybe allow to use /query and /update in the future?