Re: grlc turns your Linked Data queries into Linked Data APIs

On 1/26/17 7:58 AM, Albert Meroño Peñuela wrote:
> 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 have their
> equivalent API at
> (notice the user and repository names in the URIs). You can call API
> endpoints by e.g.
> 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]
> [2]
> [3]
> [4]
> [5]

Hi Albert,

Looks interesting.

I am trying to test what you've described quickly, but I am hitting an
issue that would be resolved by you simply sharing an example URI based
on the pattern you describe via the statement  " Go to the address bar
of this page, and append /api/github_username/repository_name" .

In the world of Linked Data, we should only be a click away from
whatever we are trying to expose to others.

I await a functional sample URI based on your repo :)


Kingsley Idehen       
Founder & CEO 
OpenLink Software   (Home Page:

Weblogs (Blogs):
Legacy Blog:
Blogspot Blog:
Medium Blog:

Profile Pages:

Web Identities (WebID):

Received on Thursday, 26 January 2017 15:36:23 UTC