- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Tue, 25 Nov 2014 20:49:28 +0100
- To: Kingsley Idehen <kidehen@openlinksw.com>
- Cc: public-hydra@w3.org
> In addition, what would constitute the SPARQL endpoint, in this scenario? There is no notion of “SPARQL endpoint” in the context of triple pattern fragments. This is on purpose; only simple questions (= triple patterns) can be asked to servers. > By that I mean: an endpoint to which SPARQL-FED queries could be directed? Federated SPARQL queries over triple pattern fragment interfaces should be solved using a federated triple pattern fragments client. We are currently extending the existing JavaScript client to support federation. Basically, it just comes down to asking triple pattern fragments to multiple servers instead of just one. This change is quite straightforward, as many existing federation engines also have triple pattern (ASK) queries at the base of their algorithm. We can thus support federation without extending the interface. If you really want a SPARQL endpoint, you can set up a local one: https://github.com/LinkedDataFragments/Client.js/blob/v1.2.0/bin/ldf-client-http We used that one for experimentation, because it gives the exact same interface as other SPARQL endpoints. However, I highly recommend against setting this up as a public SPARQL endpoint; you'd inherit both the drawbacks of triple pattern fragments and SPARQL endpoints, without having the advantages of either—so essentially, the worst of both worlds. Best regards, Ruben
Received on Tuesday, 25 November 2014 19:50:02 UTC