W3C home > Mailing lists > Public > public-lod@w3.org > January 2017

grlc turns your Linked Data queries into Linked Data APIs

From: Albert Meroño Peñuela <albert.merono@vu.nl>
Date: Thu, 26 Jan 2017 13:58:41 +0100
Message-ID: <CAL=mkuzgENkki5WMa--Huz6SnLVLYk69z6UM58Q-33Xr5f--HQ@mail.gmail.com>
To: SW-forum <semantic-web@w3.org>, Linking Open Data <public-lod@w3.org>
CC: "Hoekstra, R.J." <rinke.hoekstra@vu.nl>
Hi all,

Just letting you know that there is a public instance of grlc available at
[1]. No more hard-coded queries in your Linked Data consuming applications!

grlc [5], inspired by tools like BASIL [4], is a small server that converts
your SPARQL queries into Linked Data APIs, automatically and on the fly. To
do this, it assumes that your SPARQL queries are publicly available in a
GitHub (or similar) repository. For example, queries stored in
https://github.com/CLARIAH/wp4-queries have their equivalent API at
http://grlc.io/api/CLARIAH/wp4-queries/api-docs
(notice the user and repository names in the URIs). You can call API
endpoints by e.g. http://grlc.io/api/CLARIAH/wp4-queries/datasets

Full details are described in this paper [2].

The latest additions include a docker-based deployment, parameter
enumerations, result pagination, and compatibility with #LD servers, RDF
dumps, and HTML+RDFa pages (besides SPARQL endpoints).

We would be pleased to hear from your experiences on using grlc: bugs,
performance, use cases, feature requests, etc. grlc's issue tracker can be
found at [3].

Thanks,
Albert

[1] http://grlc.io
[2]
https://www.albertmeronyo.org/wp-content/uploads/2016/04/SALAD2016_paper_4.pdf
[3] https://github.com/CLARIAH/grlc/issues
[4] http://basil.kmi.open.ac.uk/app/#/collection
[5] https://github.com/CLARIAH/grlc
Received on Thursday, 26 January 2017 12:59:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:22:37 UTC