- From: Ruben Verborgh <Ruben.Verborgh@UGent.be>
- Date: Fri, 15 Dec 2017 15:25:10 +0000
- To: "Jakob.Voss@gbv.de" <Jakob.Voss@gbv.de>
- CC: "public-hydra@w3.org" <public-hydra@w3.org>
Hi Jakob, > I'am not fully sure about the relationship between LDF and Triple Pattern Fragments so which to refer to with BEACON. Linked Data Fragments is a theoretical framework to capture all possible read interfaces to RDF. This includes SPARQL endpoints, data dumps, Linked Data documents, Triple Pattern Fragments. Triple Pattern Fragments is a specific RDF interface with subject/predicate/object access. > I implemented an additional DataSource, see the commit in this branch: > > https://github.com/gbv/Server.js/tree/beacon That's awesome. The next release of Server.js (v3, due soon) will allow defining datasources as separate npm packages, so there will be no need to fork anymore. > BEACON further supports some metadata about a set of links, e.g. title and date of modification. Is this metadata part of Triple Pattern Fragments or does it belong to Linked Data Fragments? This metadata is not part of TPF, but it can be added. TPF is specified in such a way that extra metadata is allowed. > In Server.js I found no way to inject the metadata into the server from a DataSource so it needs to be hard-coded in config.json? You're right. We currently have support for modules that generate extra metadata (such as https://github.com/LinkedDataFragments/Server.js/tree/v2.2.2/lib/views/summary), but these are not tied to datasources indeed. It makes sense for datasources to generate extra metadata. > P.S: Server.json uses https://www.npmjs.com/package/uritemplate and beacon-links uses https://www.npmjs.com/package/uri-templates. Any arguments to not switch to the latter? No opinion either way! Best, Ruben
Received on Friday, 15 December 2017 15:25:49 UTC