Marcelo Machado

Same here: ``` Error accessing SPARQL endpoint https://query.wikidata.org/sparql: The endpoint returned an invalid SPARQL results JSON response. at emitError (.../.nvm/versions/node/v14.19.0/lib/node_modules/@ldf/server/node_modules/@ldf/datasource-sparql/lib/datasources/SparqlDatasource.js:74:33) at Request. (.../.nvm/versions/node/v14.19.0/lib/node_modules/@ldf/server/node_modules/@ldf/datasource-sparql/lib/datasources/SparqlDatasource.js:48:28) at Request.emit (events.js:412:35) at IncomingMessage. (....nvm/versions/node/v14.19.0/lib/node_modules/@ldf/server/node_modules/request/request.js:1076:12) at...

I am facing the same issue after update npm.

I believe it's a Blazegraph issue as well, but I have no access to try change this possible configuration. But I'm not quite sure that this shouldn't be an issue...

I am biased to the first approach you described and the start point would be make the `sparqlEndpoint` field an array [here](https://github.com/comunica/comunica/blob/efa0e9192f0a22d242744779f0286228de92959f/packages/actor-rdf-metadata-extract-sparql-service/lib/ActorRdfMetadataExtractSparqlService.ts#L31). However, before going too deep into this solution...

This problem is caused by two reasons: (1) Wikidata (Blazegraph) does not support queries with GRAPH. So the following lines that add the GRAPH in the query causes problems on...

Ok, I will change this and see if I can fix the tests too.

What do you think about doing this little by little? For example, in the datasource I am creating I have already added this dependency: https://github.com/marcelomachado/Server.js/commit/d29c3323f984d13731b16c66422d38a19e29ca20

Hello @bcogrel, thanks for answering. Yes, I considered that, and for now it's the solution I'm using. However, this comparison brings results beyond the expected considering the precision point. For...

Thanks @bcogrel, In fact it looks like a minimalist implementation, it is possible to notice in this code that you sent me the existence of some [variables created but not...

Hi @RdNetwork, sorry for the delay. The solution is described in the issue, however I still haven't had time to replace the `request` library nor to change the tests.