- From: Luca Matteis <lmatteis@gmail.com>
- Date: Wed, 24 Jun 2015 16:50:32 +0200
- To: Ruben Verborgh <ruben.verborgh@ugent.be>
- Cc: public-linked-data-fragments@w3.org
Hi Ruben, This is really cool and looking forward to using the latest library. Have you thought about a triple pattern fragments interface that is exposed using WebSockets rather than HTTP? On the server it would be the same amount of work (just matching triple patterns), while on the client, it could be less resourceful since you'd instantiate a single request (rather than one for each pattern). I'm not sure however if ws:// links are considered linked data, since you wouldn't have a ws:// link for each resource. Just a thought, and thanks for the great work! Luca On Wed, Jun 24, 2015 at 4:09 PM, Ruben Verborgh <ruben.verborgh@ugent.be> wrote: > Hi all, > > If people ask you whether a Hydra client exists that can use multiple APIs at the same time, here it is: http://client.linkeddatafragments.org/ > > Starting version 1.3.0, the Triple Pattern Fragments client supports federated SPARQL queries. This means that the client uses multiple interfaces to find an answer to a query. For example, the query in http://bit.ly/cubist-works uses an API on fragments.dbpedia.org and on data.linkeddatafragments.org. Any TPF API can be added. > > Code: https://github.com/LinkedDataFragments/Client.js > Specification (unchanged): http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/ > > Best, > > Ruben
Received on Wednesday, 24 June 2015 14:51:00 UTC