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

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

From: Kingsley Idehen <kidehen@openlinksw.com>
Date: Thu, 26 Jan 2017 10:35:55 -0500
To: public-lod@w3.org
Message-ID: <b7bfa297-6993-a2c7-68f5-966131872b3c@openlinksw.com>
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 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

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 :)

-- 
Regards,

Kingsley Idehen	      
Founder & CEO 
OpenLink Software   (Home Page: http://www.openlinksw.com)

Weblogs (Blogs):
Legacy Blog: http://www.openlinksw.com/blog/~kidehen/
Blogspot Blog: http://kidehen.blogspot.com
Medium Blog: https://medium.com/@kidehen

Profile Pages:
Pinterest: https://www.pinterest.com/kidehen/
Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter: https://twitter.com/kidehen
Google+: https://plus.google.com/+KingsleyIdehen/about
LinkedIn: http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal: http://kingsley.idehen.net/dataspace/person/kidehen#this
        : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this



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

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