Ruben Taelman

Related to #44. I would not make this obligatory though. I agree it's a good practise, but IMO this server should enable quickly setting up something, without having to pick...

Loading of remote files by first downloading is something that we indeed plan on adding at some point.

The QPF branch contains fixes for this (831bd4231e46f8185c12d836904914efa5d82494) and other related issues (https://github.com/LinkedDataFragments/Server.js/commits/feature-qpf-latest/lib/datasources/CompositeDatasource.js). @RubenVerborgh Should we backport these fixes? Or just wait until the 3.0.0 release?

@RubenVerborgh It won't be a clean cherry-pick, because the datasource is already graph-based at that point.

Not sure why that wouldn't work. Can you query `http://localhost:3030/pizza/sparql` with other tools? Do you see any error messages in the LDF server logs? Do you see any incoming requests...

And what about Fuseki's logs?

Config looks fine to me at first glance. Also no warnings are reported when starting the server? I don't have the bandwidth to debug this myself, but these places in...

Well that's silly... I don't immediately see a reason why this would not be allowed. If true, then this would be a good thing to be resolved in SPARQL 1.2...

Can you inspect the error message of `e` to see what is going wrong? (just adding a `console.log` should be sufficient) https://github.com/LinkedDataFragments/Server.js/blob/master/packages/datasource-sparql/lib/datasources/SparqlDatasource.js#L48

What datasource back-end and server version are you using? This sounds similar to a recent bug in HDT that has been fixed already: #83.