W3C home > Mailing lists > Public > public-lod@w3.org > March 2011

Re: The truth about SPARQL Endpoint availability

From: Richard Cyganiak <richard@cyganiak.de>
Date: Tue, 1 Mar 2011 00:04:25 +0000
Cc: public-lod@w3.org, SW-forum <semantic-web@w3.org>, semanticweb@yahoogroups.com
Message-Id: <A7C5B4EB-E7E9-4665-827B-2F5601BD769D@cyganiak.de>
To: Pierre-Yves Vandenbussche <py.vandenbussche@gmail.com>
Great work Pierre-Yves!

Good to see that the CKAN directory is useful for something besides drawing pretty cloud pictures ;-)

The logo is genius.

Currently it seems that you get a red light for 75% uptime. 75% uptime sucks, but it is still very different from 0% uptime, which probably means that the site has died completely. So may I propose lowering the threshold between red and yellow a bit?

Or maybe the 0% endpoints should simply be displayed black.

Finally, could you create a CKAN record for your dataset, following [1]? Because then we could use your tool to verify that your tool is up and running.

Again, great work.


[1] http://www.w3.org/wiki/TaskForces/CommunityProjects/LinkingOpenData/DataSets/CKANmetainformation

On 28 Feb 2011, at 18:55, Pierre-Yves Vandenbussche wrote:

> Hello all,
> you have already encountered problems of SPARQL endpoint accessibility ?
> you feel frustrated they are never available when you need them?
> you develop an application using these services but wonder if it is reliable?
> Here is a tool [1] that allows you to know public SPARQL endpoints availability and monitor them in the last hours/days. 
> Stay informed of a particular (or all) endpoint status changes through RSS feeds.
> All availability information generated by this tool is accessible through a SPARQL endpoint.
> This tool fetches public SPARQL endpoints from CKAN  open data. From this list, it runs tests every hour for availability.
> [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html
> [2] http://ckan.net/
> Pierre-Yves Vandenbussche.
Received on Tuesday, 1 March 2011 00:06:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:12 UTC