Re: Public SPARQL endpoints for generic usage


On 8 Apr 2010, at 02:43, Stephane Corlosquet wrote:

> Hi,
> Some applications don't have the capability or the resources to run SPARQL queries themselves and must rely on external services. There exist a few SPARQL public endpoints which allow generic SPARQL querying [1] [2]. Are there any policy on using these public endpoints in applications? I understand these were setup primarily for educational purposes. Obviously anyone wanting to build a reliable service would host their own SPARQL endpoints, but how about situations where the user setting up an application using SPARQL is not able to host such a service. Think of handheld devices, or situations where no SPARQL library is available for software stack an application runs on. 
> The use case which prompted me to write this email is in PHP where ARC2 requires MySQL to run SPARQL queries. During the installation of Drupal, imagine we want to get all the classes of a vocabulary with:
>   select *
>   from <>
>   where {
>     {?class rdf:type owl:Class}
>     union
>     {?class rdf:type rdfs:Class}.
>     OPTIONAL {?class rdfs:label ?label}.
>   }
> (similarly for properties)

> Sites running on a database other than MySQL will need to use an external SPARQL endpoint. I imagine this is not an isolated use case.

You can have a look at RAP [1], it provides in memory SPARQL capabilities [2].




> Do we have public endpoints available for this sort of (ideally lightweight) querying? How do they deal with server load (API key, IP based flooding control)?
> Steph.
> [1]
> [2]

Dr. Alexandre Passant
Digital Enterprise Research Institute
National University of Ireland, Galway
:me owl:sameAs <> .

Received on Thursday, 8 April 2010 10:09:14 UTC