W3C home > Mailing lists > Public > semantic-web@w3.org > April 2010

Re: Public SPARQL endpoints for generic usage

From: Ivan Mikhailov <imikhailov@openlinksw.com>
Date: Sat, 10 Apr 2010 11:52:48 +0700
To: Stephane Corlosquet <scorlosquet@gmail.com>
Cc: semantic-web@w3.org
Message-Id: <1270875168.3114.593.camel@octo.iv.dev.null>
Hello Stephane,

> 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.

I did not hear about related policy at any endpoint but I haven't
researched the subject in depth.

Our own public endpoints, like http://lod.openlinksw.com/sparql are
provided "as is" with no restrictions on their use in applications or in
some other specific way. OTOH the risk of server overloading is always
significant even if endpoints restricts the complexity of queries and
execution time, because the frequency of requests is not restricted. So
the reliability is not 99.9%. if I were application software vendor I'd
rather rent an Amazon's virtual machine with a ready-to-use copy of LOD
public endpoint or host and maintain my own copy or ask the vendor of my
favorite SPARQL processor if some appropriate offers exist.

Best Regards,

Ivan Mikhailov
OpenLink Software
http://virtuoso.openlinksw.com
Received on Saturday, 10 April 2010 04:53:18 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 08:45:17 UTC