Re: The truth about SPARQL Endpoint availability
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is indeed
something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list)
and some returns a answer pretty quickly. Some doesn't and some doesn't
support count.
However, one could have this information only for the stores that answers
the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M
triples, say) would be happy for someone to keep issuing such a query, even
if they did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store
to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint -
now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha
scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
Re: The truth about SPARQL Endpoint availability
Is the number of triples that important? With all respect to the
people on this list, I think there's a tendency to obsess over triple
counts. Aren't we past that bootstrap phase of being awed when we see
millions of triples being produced? I thought we'd moved towards
being more focussed on quality and utility of data than sheer numbers?
Besides, for me the most interesting datasets are those that are
continually changing as they reflect the real world and I'd like to
see us work towards metrics for freshness and coverage.
On Sun, Mar 6, 2011 at 11:20 AM, Tim Berners-Lee ti...@w3.org wrote:
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is
indeed something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list)
and some returns a answer pretty quickly. Some doesn't and some doesn't
support count.
However, one could have this information only for the stores that answers
the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M
triples, say) would be happy for someone to keep issuing such a query, even
if they did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store
to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint
- now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha
scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
Re: The truth about SPARQL Endpoint availability
Yes, I was puzzling over this.
And then what other useful things might be special-cased.
(classes?, even a dump of rdfs:label?)
But it sort of sticks in the craw to do that.
And I keep coming back to the fact that there is already a way of doing this in
the Linked Data world.
If you have the voiD description in your endpoint, then it all just works.
And it can be queried or browsed, etc.
So for example (in our case) querying
http://southampton.rkbexplorer.com/sparql/ with
{?s void:sparqlEndpoint http://southampton.rkbexplorer.com/sparql/}
gives
?s = http://southampton.rkbexplorer.com/id/void
And bingo!
Browse the store metadata as LD or SPARQL to your heart's content, as you would
with any other data we offer from that store.
And whatever else metadata about the store that is wanted can be proposed as
different vocabs or extensions to voiD.
One thing I am puzzling over, though:
Should http://southampton.rkbexplorer.com/sparql/ be Linked Data?
Currently if you ask for RDF we give 406 Not Acceptable.
It might be helpful to 303 to an RDF description; and if so, would it look
different from the voiD description?
Or certainly somehow getting back an rdfs:seeAlso would be valid.
Or is this already sorted out somewhere that I have missed?
(I told you I'm not a voiD guru :-) )
Best
Hugh
On 6 Mar 2011, at 11:20, Tim Berners-Lee wrote:
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is
indeed something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list)
and some returns a answer pretty quickly. Some doesn't and some doesn't
support count.
However, one could have this information only for the stores that answers
the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M
triples, say) would be happy for someone to keep issuing such a query, even
if they did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store
to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint
- now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha
scritto:
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
Re: The truth about SPARQL Endpoint availability
Talk of how many triples are in a store puts me in mind of this quote
Measuring programming progress by lines of code is like measuring
aircraft building progress by weight.
At every stage we should be able to answer a key question from someone
setting up a linked data site for the first time, and that question is
What's in it for me?
If we (the community interested in the development of Linked Data) want
to get data on linkage and size of datasets, then the tools better do
that automatically, because there's very few webmasters out there
willing to do extra work just so we can make pretty graphs.
Ian Davis wrote:
Is the number of triples that important? With all respect to the
people on this list, I think there's a tendency to obsess over triple
counts. Aren't we past that bootstrap phase of being awed when we see
millions of triples being produced? I thought we'd moved towards
being more focussed on quality and utility of data than sheer numbers?
Besides, for me the most interesting datasets are those that are
continually changing as they reflect the real world and I'd like to
see us work towards metrics for freshness and coverage.
On Sun, Mar 6, 2011 at 11:20 AM, Tim Berners-Lee ti...@w3.org wrote:
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is indeed
something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list) and
some returns a answer pretty quickly. Some doesn't and some doesn't support
count.
However, one could have this information only for the stores that answers the
count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M triples,
say) would be happy for someone to keep issuing such a query, even if they did
decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ; rdf:value
?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store to
also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint -
now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of error.
For a properly maintained site, of course, the VoiD description will give lots
of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the content
of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha scritto:
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
Re: The truth about SPARQL Endpoint availability
I believe that people coming from a MySQL (well MyISAM, specifically)
background would assume a global COUNT to be fast, since it's a O(1) operation
on a MyISAM table with a primary key.
Another way to go would be to add a NOOP command to SPARQL, surely?
Dan
On 6 Mar 2011, at 11:20, Tim Berners-Lee wrote:
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is
indeed something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list)
and some returns a answer pretty quickly. Some doesn't and some doesn't
support count.
However, one could have this information only for the stores that answers
the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M
triples, say) would be happy for someone to keep issuing such a query, even
if they did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store
to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint
- now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha
scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Re: The truth about SPARQL Endpoint availability
On 6 Mar 2011, at 12:16, Christopher Gutteridge wrote:
Talk of how many triples are in a store puts me in mind of this quote
Measuring programming progress by lines of code is like measuring
aircraft building progress by weight.
Well, but you know that quality on the Web of Data is measured in million
triples! ;-)
Jokes aside, as long as triple store performance is a frequent limiting factor,
triple counts are important.
“We can't load that dataset, it would be another 200MT, this would kill our
store”
“Their dataset is only 100kT, so how come their endpoint is so slow?”
“Well if you have a million triples then you should be ok with any of the major
stores on the hardware you already have.”
“Given the load rate we typically get on our store, loading this dataset should
take till tuesday.”
“Wow, this new dataset increases the total number of triples in the LOD Cloud
by 3%!”
You might object to some, but surely not all, of these uses of triple counts.
there's very few webmasters out there willing to do extra work just so we can
make pretty graphs.
Aside: As a maker of pretty graphs, I can tell you that you would be surprised.
Enjoy your Sunday!
Richard
Ian Davis wrote:
Is the number of triples that important? With all respect to the
people on this list, I think there's a tendency to obsess over triple
counts. Aren't we past that bootstrap phase of being awed when we see
millions of triples being produced? I thought we'd moved towards
being more focussed on quality and utility of data than sheer numbers?
Besides, for me the most interesting datasets are those that are
continually changing as they reflect the real world and I'd like to
see us work towards metrics for freshness and coverage.
On Sun, Mar 6, 2011 at 11:20 AM, Tim Berners-Lee
ti...@w3.org
wrote:
Maybe the count of triples should be special-cased in the sparql server
code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd
certainly prefer if people don't run a global count too often (or at all).
It is indeed something that makes typical SPARQL implementations work very
hard.
But it's a good reminder we should provide an alternative and i'll look
into providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint
list) and some returns a answer pretty quickly. Some doesn't and some
doesn't support count.
However, one could have this information only for the stores that
answers the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it
very unlikely that the owner of a store with a decent chunk of data ( 1M
triples, say) would be happy for someone to keep issuing such a query,
even if they did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s
http://rdfs.org/ns/void#numberOfTriples
?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in
the scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD
store to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD
endpoint(s) plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL
endpoint - now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then
quite rightly decide they have burnt enough resources, and return some
sort of error.
For a properly maintained site, of course, the VoiD description will
give lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why
Re: The truth about SPARQL Endpoint availability
Thanks Richard, that's really useful. I'm hoping to be talking to lots
of people this year who are thinking of dipping their toe in the water,
and it's really helpful to have some clear soundbites of why you should
bother to do things, rather than appeal to people's better nature.
Richard Cyganiak wrote:
On 6 Mar 2011, at 12:16, Christopher Gutteridge wrote:
Talk of how many triples are in a store puts me in mind of this quote
Measuring programming progress by lines of code is like measuring aircraft
building progress by weight.
Well, but you know that quality on the Web of Data is measured in million
triples! ;-)
Jokes aside, as long as triple store performance is a frequent limiting factor,
triple counts are important.
“We can't load that dataset, it would be another 200MT, this would kill our
store”
“Their dataset is only 100kT, so how come their endpoint is so slow?”
“Well if you have a million triples then you should be ok with any of the major
stores on the hardware you already have.”
“Given the load rate we typically get on our store, loading this dataset should
take till tuesday.”
“Wow, this new dataset increases the total number of triples in the LOD Cloud
by 3%!”
You might object to some, but surely not all, of these uses of triple counts.
there's very few webmasters out there willing to do extra work just so we can
make pretty graphs.
Aside: As a maker of pretty graphs, I can tell you that you would be surprised.
Enjoy your Sunday!
Richard
Ian Davis wrote:
Is the number of triples that important? With all respect to the
people on this list, I think there's a tendency to obsess over triple
counts. Aren't we past that bootstrap phase of being awed when we see
millions of triples being produced? I thought we'd moved towards
being more focussed on quality and utility of data than sheer numbers?
Besides, for me the most interesting datasets are those that are
continually changing as they reflect the real world and I'd like to
see us work towards metrics for freshness and coverage.
On Sun, Mar 6, 2011 at 11:20 AM, Tim Berners-Lee
ti...@w3.org
wrote:
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is indeed
something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list) and
some returns a answer pretty quickly. Some doesn't and some doesn't support
count.
However, one could have this information only for the stores that answers the
count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M triples,
say) would be happy for someone to keep issuing such a query, even if they did
decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s
http://rdfs.org/ns/void#numberOfTriples
?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ; rdf:value
?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store to
also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint -
now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then
Re: The truth about SPARQL Endpoint availability
On 3/6/11 7:56 AM, Richard Cyganiak wrote:
On 6 Mar 2011, at 12:16, Christopher Gutteridge wrote:
Talk of how many triples are in a store puts me in mind of this quote
Measuring programming progress by lines of code is like measuring aircraft
building progress by weight.
Well, but you know that quality on the Web of Data is measured in million
triples! ;-)
Jokes aside, as long as triple store performance is a frequent limiting factor,
triple counts are important.
“We can't load that dataset, it would be another 200MT, this would kill our
store”
“Their dataset is only 100kT, so how come their endpoint is so slow?”
“Well if you have a million triples then you should be ok with any of the major
stores on the hardware you already have.”
“Given the load rate we typically get on our store, loading this dataset should
take till tuesday.”
“Wow, this new dataset increases the total number of triples in the LOD Cloud
by 3%!”
You might object to some, but surely not all, of these uses of triple counts.
there's very few webmasters out there willing to do extra work just so we can
make pretty graphs.
Aside: As a maker of pretty graphs, I can tell you that you would be surprised.
Enjoy your Sunday!
Richard
In addition to the above, smart SPARQL-FED [1] isn't achievable without
good stats about SPARQL endpoints. Locality aware cost optimization is
very dependent on metadata [2] gleaned from remote data sources
associated with a SPARQL endpoint. What's good for SQL is well and truly
good for SPARQL re. data virtualization, assuming Triple/Quad stores are
a sub-category of DBMS. We can leverage voID when making SPARQL endpoint
description metadata. It's actually very important from a pragmatic view
point, especially if we truly believe in the crystallization of the Web
as a Global Data Space.
I don't expect users or Web developers to write SPARQL-FED, but I do
expect them to assume and/or demand the Linked Data experience that
SPARQL-FED, SPARQL Endpoint Metadata, and voID facilitate.
Links:
1. http://www.w3.org/TR/sparql-features/#Basic_federated_query - SPARQL-FED
2. http://www.w3.org/TR/sparql-features/#Service_description -- SPARQL
endpoint metadata.
Kingsley
Ian Davis wrote:
Is the number of triples that important? With all respect to the
people on this list, I think there's a tendency to obsess over triple
counts. Aren't we past that bootstrap phase of being awed when we see
millions of triples being produced? I thought we'd moved towards
being more focussed on quality and utility of data than sheer numbers?
Besides, for me the most interesting datasets are those that are
continually changing as they reflect the real world and I'd like to
see us work towards metrics for freshness and coverage.
On Sun, Mar 6, 2011 at 11:20 AM, Tim Berners-Lee
ti...@w3.org
wrote:
Maybe the count of triples should be special-cased in the sparql server code,
spotted on input and the store size returned.
if it is reasonable for the endpoint to keep track of the size of its store.
(Do they anyway?)
Tim
On 2011-03 -05, at 11:58, Bill Roberts wrote:
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is indeed
something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list) and
some returns a answer pretty quickly. Some doesn't and some doesn't support
count.
However, one could have this information only for the stores that answers the
count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M triples,
say) would be happy for someone to keep issuing such a query, even if they did
decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s
http://rdfs.org/ns/void#numberOfTriples
?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store to
also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
Re: The truth about SPARQL Endpoint availability
Pierre-Yves, Peter, On 2 Mar 2011, at 16:59, Pierre-Yves Vandenbussche wrote: If someone from CKAN could answer these questions: Is it normal in CKAN to have more than one endpoint ? (I think so) No, http://ckan.net/package/geospecies is the only CKAN record where two endpoints were entered. All other packages have zero or one. Is it possible in CKAN endpoint to differentiate between main and alternative endpoint ? The question of alternative endpoints hasn't really come up yet. For geospecies someone just added it ad hoc. Actually, the LOD Cloud Cache (hope Hugh isn't listening!) has its own CKAN package: http://ckan.net/package/lod-cloud-cache Its SPARQL endpoint is already listed there. So I took the liberty to remove it from the GeoSpecies package. At some point we should explore making the list of packages mirrored in the LOD Cache explicit on CKAN. Best, Richard
Re: The truth about SPARQL Endpoint availability
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the content
of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
Re: The truth about SPARQL Endpoint availability
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of error.
For a properly maintained site, of course, the VoiD description will give lots
of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Re: The truth about SPARQL Endpoint availability
Hi,
I think it depends on the store, I've tried some (from the endpoint list) and
some returns a answer pretty quickly. Some doesn't and some doesn't support
count.
However, one could have this information only for the stores that answers the
count query, no need to try all time.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
Re: The truth about SPARQL Endpoint availability
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list) and
some returns a answer pretty quickly. Some doesn't and some doesn't support
count.
However, one could have this information only for the stores that answers the
count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M triples,
say) would be happy for someone to keep issuing such a query, even if they did
decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store to
also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint -
now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Re: The truth about SPARQL Endpoint availability
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping
in the scovo stuff, so more like:
ROTFL, reading that Hugh claims to be *not* a VoID guru ;)
Note that SCOVO modelling of stats in VoID has been deprecated and
simplified [1].
Fancy the challenge, it is the weekend?! :-)
Indeed!
Cheers,
Michael
[1] http://www.w3.org/TR/void/#statistics
--
Dr. Michael Hausenblas, Research Fellow
LiDRC - Linked Data Research Centre
DERI - Digital Enterprise Research Institute
NUIG - National University of Ireland, Galway
Ireland, Europe
Tel. +353 91 495730
http://linkeddata.deri.ie/
http://sw-app.org/about.html
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint
list) and some returns a answer pretty quickly. Some doesn't and
some doesn't support count.
However, one could have this information only for the stores that
answers the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find
it very unlikely that the owner of a store with a decent chunk of
data ( 1M triples, say) would be happy for someone to keep issuing
such a query, even if they did decide to give enough resources to
execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping
in the scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension
void:numberOfTriples ; rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a
voiD store to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD
endpoint(s) plus Pierre-Yves's data (he has a SPARQL endpoint), to
do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL
endpoint - now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then
quite rightly decide they have burnt enough resources, and return
some sort of error.
For a properly maintained site, of course, the VoiD description
will give lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if
logged and compared over time, can give a practical view of the
liveliness of the content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche
ha scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059
Re: The truth about SPARQL Endpoint availability
On 5 Mar 2011, at 15:23, Michael Hausenblas wrote:
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
ROTFL, reading that Hugh claims to be *not* a VoID guru ;)
Tee hee.
Very kind, but
Note that SCOVO modelling of stats in VoID has been deprecated and simplified
[1].
sort of proves my assertion :-)
And perhaps this little interchange proves the assertion in [1]
Statistics would be verbose, and querying them with SPARQL was difficult.
I was looking at our voiD docs.
Seems we have not updated them, and they still do scovo.
Better make sure the boys get to work :-)
Fancy the challenge, it is the weekend?! :-)
Indeed!
Cheers
Cheers,
Michael
[1] http://www.w3.org/TR/void/#statistics
--
Dr. Michael Hausenblas, Research Fellow
LiDRC - Linked Data Research Centre
DERI - Digital Enterprise Research Institute
NUIG - National University of Ireland, Galway
Ireland, Europe
Tel. +353 91 495730
http://linkeddata.deri.ie/
http://sw-app.org/about.html
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list)
and some returns a answer pretty quickly. Some doesn't and some doesn't
support count.
However, one could have this information only for the stores that answers
the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M
triples, say) would be happy for someone to keep issuing such a query, even
if they did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store
to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint -
now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha
scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23
Re: The truth about SPARQL Endpoint availability
Thanks Hugh - as someone running a couple of SPARQL endpoints, I'd certainly
prefer if people don't run a global count too often (or at all). It is indeed
something that makes typical SPARQL implementations work very hard.
But it's a good reminder we should provide an alternative and i'll look into
providing triple counts in voiD.
Bill
On 5 Mar 2011, at 15:14, Hugh Glaser wrote:
Hi,
On 5 Mar 2011, at 14:22, Andrea Splendiani wrote:
Hi,
I think it depends on the store, I've tried some (from the endpoint list)
and some returns a answer pretty quickly. Some doesn't and some doesn't
support count.
However, one could have this information only for the stores that answers
the count query, no need to try all time.
I am happy for a store implementor or owner to disagree, but I find it very
unlikely that the owner of a store with a decent chunk of data ( 1M triples,
say) would be happy for someone to keep issuing such a query, even if they
did decide to give enough resources to execute it.
I would quickly blacklist such a site.
VoID:
is this a good query:
select * where {?s http://rdfs.org/ns/void#numberOfTriples ?o }
I'm no SPARQL or voiD guru, but I think you need a bit more wrapping in the
scovo stuff, so more like:
SELECT DISTINCT ?endpoint ?uri ?triples ?uris WHERE
{ ?ds a void:Dataset .
?ds void:sparqlEndpoint ?uri .
?ds rdfs:label ?endpoint .
?ds void:statItem [ scovo:dimension void:numberOfTriples ;
rdf:value ?triples ] .
}
Try it at
http://kwijibo.talis.com/voiD/
or
http://void.rkbexplorer.com/
I guess Pierre-Yves might like to enhance his page by querying a voiD store
to also give basic stats.
Or someone might like to do a store reporter that uses (a) voiD endpoint(s)
plus Pierre-Yves's data (he has a SPARQL endpoint), to do so.
And maybe the CKAN endpoint would have extra useful data as well.
A real Semantic Web application that queried more than one SPARQL endpoint -
now that would be a novelty!
Fancy the challenge, it is the weekend?! :-)
ciao
Hugh
it doesn't seem viable if so.
ciao,
Andrea
Il giorno 05/mar/2011, alle ore 13.49, Hugh Glaser ha scritto:
NIce idea, but,... :-)
SELECT (count(*) as ?c) WHERE {?s ?p ?o}
is a pretty anti-social thing to do to a store.
At best, a store of any size will spend a while thinking, and then quite
rightly decide they have burnt enough resources, and return some sort of
error.
For a properly maintained site, of course, the VoiD description will give
lots of similar information.
Best
Hugh
On 5 Mar 2011, at 13:06, Andrea Splendiani wrote:
Hi, very nice!
I have a small suggestion:
why don't you ask count(*) where {?s ?p ?o} to the endpoint ?
Or ask for the number of graphs ?
Both information, number of triples and number of graphs, if logged and
compared over time, can give a practical view of the liveliness of the
content of the endpoint.
best,
Andrea Splendiani
Il giorno 28/feb/2011, alle ore 18.55, Pierre-Yves Vandenbussche ha
scritto:
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.
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Andrea Splendiani
Senior Bioinformatics Scientist
Centre for Mathematical and Computational Biology
+44(0)1582 763133 ext 2004
andrea.splendi...@bbsrc.ac.uk
--
Hugh Glaser,
Intelligence, Agents, Multimedia
School of Electronics and Computer Science,
University of Southampton,
Southampton SO17 1BJ
Work: +44 23 8059 3670, Fax: +44 23 8059 3045
Mobile: +44 78 9422 3822, Home: +44 23 8061 5652
http://www.ecs.soton.ac.uk/~hg/
Re: The truth about SPARQL Endpoint availability
I think this is great, but I am wondering if there should be some way of differentiating between the original endpoint and third-party endpoints. The GeoSpecies/TaxonConcept endpoint is the same, but there are other third-party endpoints. I don't understand why the statistics for the GeoSpecies/TaxonConcept original endpoints are different since they are the same site. Thanks, - Pete On Mon, Feb 28, 2011 at 12:55 PM, Pierre-Yves Vandenbussche py.vandenbuss...@gmail.com 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche. -- --- Pete DeVries Department of Entomology University of Wisconsin - Madison 445 Russell Laboratories 1630 Linden Drive Madison, WI 53706 TaxonConcept Knowledge Base http://www.taxonconcept.org/ / GeoSpecies Knowledge Base http://lod.geospecies.org/ About the GeoSpecies Knowledge Base http://about.geospecies.org/
Re: The truth about SPARQL Endpoint availability
Richard Cyganiak wrote: On 1 Mar 2011, at 00:14, Pierre-Yves Vandenbussche wrote: Average 24h and 7days availability are just extra info. Colour associated to an endpoint is given based on its availability right now. That means: -a red endpoint is NOT available right now. -an orange endpoint is available but had some troubles since last 24h. -a green endpoint is available without any trouble since last 24h. Ok. But my point stands: There's a big difference between “down this very moment” (red) and “has never been up in the last 7 days”. The former might be back in 15 minutes. The latter most likely is gone permanently. I think it would be good to capture that in the choice of color. good/fair point, I'd suggest: -a red endpoint has not been available for X hours/days. -an orange endpoint is available but had some troubles since last 24h. -a green endpoint is available without any trouble since last 24h. even better if X was a last seen X hours/days ago cheers, nathan
The truth about SPARQL Endpoint availability
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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche.
Re: The truth about SPARQL Endpoint availability
On 2/28/11 1:55 PM, 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ 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. Awesome! Major piece of critical infrastructure for DataDNS :-) -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Re: The truth about SPARQL Endpoint availability
Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche.
Re: The truth about SPARQL Endpoint availability
Thanks. Has caused me to find two mistakes in our CKAN entries (biolit and opencyc)! But also, I didn't understand this entry to one of our RKB ones, which has been up as far as I know: Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) 0% 1,13% attachment: rss.gifattachment: endpoint.pngattachment: ckan.png As your link does get to the endpoint, which allowed me to do a valid query. So I checked another random red dot: Linking Italian University Statistics Project 0% 0% attachment: rss.gifattachment: endpoint.pngattachment: ckan.png Which seems fine as well. So maybe a bit debugging of the process, but I will certainly find the RSS useful to get an external view of the uptime. Thanks. Hugh 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. -- Hugh Glaser, Intelligence, Agents, Multimedia School of Electronics and Computer Science, University of Southampton, Southampton SO17 1BJ Work: +44 23 8059 3670, Fax: +44 23 8059 3045 Mobile: +44 78 9422 3822, Home: +44 23 8061 5652 http://www.ecs.soton.ac.uk/~hg/
Re: The truth about SPARQL Endpoint availability
Hello Hugh,
As some endpoints does not accept the ask query, I use a simple select
request to test SPARQL protocol :
select ?s
where{?s ?p ?o.}LIMIT 1
This query leads to an error on this endpoint
http://oai.rkbexplorer.com/sparql/:
Error
Failed to connect to SPARQL endpoint, or the endpoint returned and error
trying to process your query.
Pierre-Yves Vandenbussche.
On Mon, Feb 28, 2011 at 11:03 PM, Hugh Glaser h...@ecs.soton.ac.uk wrote:
Thanks.
Has caused me to find two mistakes in our CKAN entries (biolit and
opencyc)!
But also, I didn't understand this entry to one of our RKB ones, which has
been up as far as I know:
Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) 0%
1,13%
Re: The truth about SPARQL Endpoint availability
Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche.
Re: The truth about SPARQL Endpoint availability
Oh sorry, I overlooked this for some reason. What a pitty. However, I thought more about some inline Semantic Web Linked Data in the feeds. Would that be an option? Cheers, Bob PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS delivers me a Missing parameter: query. So I guess, I have to parametrize the request. An instruction for that might be useful then ;) Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche: Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche.
Re: The truth about SPARQL Endpoint availability
Robert, Do you have example of inline Semantic Web Linked Data in the feeds ? My SPARQL endpoint have no human client for the moment ... computer first !! Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 11:35 PM, Bob Ferris z...@elbklang.net wrote: Oh sorry, I overlooked this for some reason. What a pitty. However, I thought more about some inline Semantic Web Linked Data in the feeds. Would that be an option? Cheers, Bob PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS delivers me a Missing parameter: query. So I guess, I have to parametrize the request. An instruction for that might be useful then ;) Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche: Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche.
Re: The truth about SPARQL Endpoint availability
What we'll be wanting soon is a nagios check for our endpoints. Is there any established good/bad practice? 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ 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. -- Christopher Gutteridge -- http://id.ecs.soton.ac.uk/person/1248 You should read the ECS Web Team blog: http://blogs.ecs.soton.ac.uk/webteam/
Re: The truth about SPARQL Endpoint availability
On 2/28/11 5:43 PM, Pierre-Yves Vandenbussche wrote: Robert, Do you have example of inline Semantic Web Linked Data in the feeds ? My SPARQL endpoint have no human client for the moment ... computer first !! Do you have a graph representation of the data describing SPARQL endpoint availability using term from the vocabulary you devised for this effort? Basically, do you have HTML+RDFa, RDF/XML, N-Triples, Turtle etc.. representations of your entity descriptions graphs? You could place SPARQL protocol URLs in link/ within head/ as we do re. DBpedia pages, for instance. Kingsley Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 11:35 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net wrote: Oh sorry, I overlooked this for some reason. What a pitty. However, I thought more about some inline Semantic Web Linked Data in the feeds. Would that be an option? Cheers, Bob PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS delivers me a Missing parameter: query. So I guess, I have to parametrize the request. An instruction for that might be useful then ;) Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche: Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net mailto:z...@elbklang.net mailto:z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche. -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Re: The truth about SPARQL Endpoint availability
Kingsley, Thanks for your support. All data available through the SPARQL endpoint is compliant to this vocabulary: http://labs.mondeca.com/vocab/endpointStatus which relies on VoID . What Robert suggested me is to integrate RDFa in RSS feed which is a great idea. I will for sure improve the endpoint accessibility for humans. Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 11:54 PM, Kingsley Idehen kide...@openlinksw.comwrote: On 2/28/11 5:43 PM, Pierre-Yves Vandenbussche wrote: Robert, Do you have example of inline Semantic Web Linked Data in the feeds ? My SPARQL endpoint have no human client for the moment ... computer first !! Do you have a graph representation of the data describing SPARQL endpoint availability using term from the vocabulary you devised for this effort? Basically, do you have HTML+RDFa, RDF/XML, N-Triples, Turtle etc.. representations of your entity descriptions graphs? You could place SPARQL protocol URLs in link/ within head/ as we do re. DBpedia pages, for instance. Kingsley Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 11:35 PM, Bob Ferris z...@elbklang.net wrote: Oh sorry, I overlooked this for some reason. What a pitty. However, I thought more about some inline Semantic Web Linked Data in the feeds. Would that be an option? Cheers, Bob PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS delivers me a Missing parameter: query. So I guess, I have to parametrize the request. An instruction for that might be useful then ;) Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche: Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche. -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Re: The truth about SPARQL Endpoint availability
Pierre-Yves, Great contribution to the eco-system, congrats! Where applicable and if possible you may want to consider using the SD vocab as described in [1]. KUGTW! Cheers, Michael [1] http://www.w3.org/2001/sw/interest/void/#sparql-sd -- Dr. Michael Hausenblas, Research Fellow LiDRC - Linked Data Research Centre DERI - Digital Enterprise Research Institute NUIG - National University of Ireland, Galway Ireland, Europe Tel. +353 91 495730 http://linkeddata.deri.ie/ http://sw-app.org/about.html On 28 Feb 2011, at 23:03, Pierre-Yves Vandenbussche wrote: Kingsley, Thanks for your support. All data available through the SPARQL endpoint is compliant to this vocabulary: http://labs.mondeca.com/vocab/endpointStatus which relies on VoID . What Robert suggested me is to integrate RDFa in RSS feed which is a great idea. I will for sure improve the endpoint accessibility for humans. Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses On Mon, Feb 28, 2011 at 11:54 PM, Kingsley Idehen kide...@openlinksw.com wrote: On 2/28/11 5:43 PM, Pierre-Yves Vandenbussche wrote: Robert, Do you have example of inline Semantic Web Linked Data in the feeds ? My SPARQL endpoint have no human client for the moment ... computer first !! Do you have a graph representation of the data describing SPARQL endpoint availability using term from the vocabulary you devised for this effort? Basically, do you have HTML+RDFa, RDF/XML, N-Triples, Turtle etc.. representations of your entity descriptions graphs? You could place SPARQL protocol URLs in link/ within head/ as we do re. DBpedia pages, for instance. Kingsley Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses On Mon, Feb 28, 2011 at 11:35 PM, Bob Ferris z...@elbklang.net wrote: Oh sorry, I overlooked this for some reason. What a pitty. However, I thought more about some inline Semantic Web Linked Data in the feeds. Would that be an option? Cheers, Bob PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS delivers me a Missing parameter: query. So I guess, I have to parametrize the request. An instruction for that might be useful then ;) Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche: Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2] http://ckan.net/ Pierre-Yves Vandenbussche. -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Re: The truth about SPARQL Endpoint availability
Thank you Michael, good remark, the more data are linked the better ... coming soon :) Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses http://mondeca.wordpress.com/ On Tue, Mar 1, 2011 at 12:16 AM, Michael Hausenblas michael.hausenb...@deri.org wrote: Pierre-Yves, Great contribution to the eco-system, congrats! Where applicable and if possible you may want to consider using the SD vocab as described in [1]. KUGTW! Cheers, Michael [1] http://www.w3.org/2001/sw/interest/void/#sparql-sd -- Dr. Michael Hausenblas, Research Fellow LiDRC - Linked Data Research Centre DERI - Digital Enterprise Research Institute NUIG - National University of Ireland, Galway Ireland, Europe Tel. +353 91 495730 http://linkeddata.deri.ie/ http://sw-app.org/about.html On 28 Feb 2011, at 23:03, Pierre-Yves Vandenbussche wrote: Kingsley, Thanks for your support. All data available through the SPARQL endpoint is compliant to this vocabulary: http://labs.mondeca.com/vocab/endpointStatus which relies on VoID . What Robert suggested me is to integrate RDFa in RSS feed which is a great idea. I will for sure improve the endpoint accessibility for humans. Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses On Mon, Feb 28, 2011 at 11:54 PM, Kingsley Idehen kide...@openlinksw.com wrote: On 2/28/11 5:43 PM, Pierre-Yves Vandenbussche wrote: Robert, Do you have example of inline Semantic Web Linked Data in the feeds ? My SPARQL endpoint have no human client for the moment ... computer first !! Do you have a graph representation of the data describing SPARQL endpoint availability using term from the vocabulary you devised for this effort? Basically, do you have HTML+RDFa, RDF/XML, N-Triples, Turtle etc.. representations of your entity descriptions graphs? You could place SPARQL protocol URLs in link/ within head/ as we do re. DBpedia pages, for instance. Kingsley Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses On Mon, Feb 28, 2011 at 11:35 PM, Bob Ferris z...@elbklang.net wrote: Oh sorry, I overlooked this for some reason. What a pitty. However, I thought more about some inline Semantic Web Linked Data in the feeds. Would that be an option? Cheers, Bob PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS delivers me a Missing parameter: query. So I guess, I have to parametrize the request. An instruction for that might be useful then ;) Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche: Hello Robert, Every information produced by this service are stored in a SPARQL Endpoint : http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html These open data are linked to CKAN ones. You can already access them. best, Pierre-Yves Vandenbussche Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com mailto:pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com http://www.mondeca.com/ Blog: Leçons de choses http://mondeca.wordpress.com/ On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris z...@elbklang.net mailto:z...@elbklang.net wrote: Congrats Pierre, well done! This might hopefully become a quite useful resource. Any plans to publish this information itself as Semantic Web Linked Data? Cheers, Bob Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche: 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 http://labs.mondeca.com/sparqlEndpointsStatus/index.html[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 http://ckan.net/ open data. From this list, it runs tests every hour for availability. [1] http://labs.mondeca.com/sparqlEndpointsStatus/index.html http://labs.mondeca.com/sparqlEndpointsStatus/index.html[2]
Re: The truth about SPARQL Endpoint availability
On 2/28/11 6:03 PM, Pierre-Yves Vandenbussche wrote:
Kingsley,
Thanks for your support. All data available through the SPARQL
endpoint is compliant to this vocabulary:
http://labs.mondeca.com/vocab/endpointStatus which relies on VoID .
What Robert suggested me is to integrate RDFa in RSS feed which is a
great idea.
Yes. But you can also do same in the HTML page that contains the list of
endpoints. In addition, you can use link
rel={some-predicate-uri-if-not-IANA-registered} / to make this
machine readable discernible agents that understand Web Linking
semantics. Of course, you could also go one level deep re. HTTP metadata
using Link:.
Links:
1.
http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http://dbpedia.org/page/Linked_Dataacceptheader=useragentheader=
-- Example of what I mean .
Kingsley
I will for sure improve the endpoint accessibility for humans.
Pierre-Yves Vandenbussche
Research Development
Mondeca
3, cité Nollez 75018 Paris France
Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59
Mail: pierre-yves.vandenbuss...@mondeca.com
mailto:pierre-yves.vandenbuss...@mondeca.com
Website: www.mondeca.com http://www.mondeca.com/
Blog: Leçons de choses http://mondeca.wordpress.com/
On Mon, Feb 28, 2011 at 11:54 PM, Kingsley Idehen
kide...@openlinksw.com mailto:kide...@openlinksw.com wrote:
On 2/28/11 5:43 PM, Pierre-Yves Vandenbussche wrote:
Robert,
Do you have example of inline Semantic Web Linked Data in the
feeds ?
My SPARQL endpoint have no human client for the moment ...
computer first !!
Do you have a graph representation of the data describing SPARQL
endpoint availability using term from the vocabulary you devised
for this effort?
Basically, do you have HTML+RDFa, RDF/XML, N-Triples, Turtle etc..
representations of your entity descriptions graphs? You could
place SPARQL protocol URLs in link/ within head/ as we do re.
DBpedia pages, for instance.
Kingsley
Pierre-Yves Vandenbussche
Research Development
Mondeca
3, cité Nollez 75018 Paris France
Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59
Mail: pierre-yves.vandenbuss...@mondeca.com
mailto:pierre-yves.vandenbuss...@mondeca.com
Website: www.mondeca.com http://www.mondeca.com/
Blog: Leçons de choses http://mondeca.wordpress.com/
On Mon, Feb 28, 2011 at 11:35 PM, Bob Ferris z...@elbklang.net
mailto:z...@elbklang.net wrote:
Oh sorry,
I overlooked this for some reason. What a pitty. However, I
thought more about some inline Semantic Web Linked Data in
the feeds. Would that be an option?
Cheers,
Bob
PS: http://labs.mondeca.com/repositories/ENDPOINT_STATUS
delivers me a Missing parameter: query. So I guess, I have
to parametrize the request. An instruction for that might be
useful then ;)
Am 28.02.2011 23:25, schrieb Pierre-Yves Vandenbussche:
Hello Robert,
Every information produced by this service are stored in
a SPARQL
Endpoint :
http://labs.mondeca.com/sparqlEndpointsStatus/endpoint/endpoint.html
These open data are linked to CKAN ones. You can already
access them.
best,
Pierre-Yves Vandenbussche
Research Development
Mondeca
3, cité Nollez 75018 Paris France
Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59
Mail: pierre-yves.vandenbuss...@mondeca.com
mailto:pierre-yves.vandenbuss...@mondeca.com
mailto:pierre-yves.vandenbuss...@mondeca.com
mailto:pierre-yves.vandenbuss...@mondeca.com
Website: www.mondeca.com http://www.mondeca.com
http://www.mondeca.com/
Blog: Leçons de choses http://mondeca.wordpress.com/
On Mon, Feb 28, 2011 at 10:45 PM, Bob Ferris
z...@elbklang.net mailto:z...@elbklang.net
mailto:z...@elbklang.net mailto:z...@elbklang.net wrote:
Congrats Pierre, well done!
This might hopefully become a quite useful resource.
Any plans to
publish this information itself as Semantic Web Linked
Data?
Cheers,
Bob
Am 28.02.2011 19:55, schrieb Pierre-Yves Vandenbussche:
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
http://labs.mondeca.com/sparqlEndpointsStatus/index.html[1]
that allows you to know
Re: The truth about SPARQL Endpoint availability
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. Richard [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.
Re: The truth about SPARQL Endpoint availability
Hi Richard, Now we have pretty cloud pictures and some coloured spotlights ;) Average 24h and 7days availability are just extra info. Colour associated to an endpoint is given based on its availability right now. That means: -a red endpoint is NOT available right now. -an orange endpoint is available but had some troubles since last 24h. -a green endpoint is available without any trouble since last 24h. May be I should put my legend at table's top. Pierre-Yves Vandenbussche. On Tue, Mar 1, 2011 at 1:04 AM, Richard Cyganiak rich...@cyganiak.dewrote: 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. Richard [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 Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses http://mondeca.wordpress.com/
Re: The truth about SPARQL Endpoint availability
On 1 Mar 2011, at 00:14, Pierre-Yves Vandenbussche wrote: Average 24h and 7days availability are just extra info. Colour associated to an endpoint is given based on its availability right now. That means: -a red endpoint is NOT available right now. -an orange endpoint is available but had some troubles since last 24h. -a green endpoint is available without any trouble since last 24h. Ok. But my point stands: There's a big difference between “down this very moment” (red) and “has never been up in the last 7 days”. The former might be back in 15 minutes. The latter most likely is gone permanently. I think it would be good to capture that in the choice of color. Best, Richard May be I should put my legend at table's top. Pierre-Yves Vandenbussche. On Tue, Mar 1, 2011 at 1:04 AM, Richard Cyganiak rich...@cyganiak.de wrote: 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. Richard [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 Research Development Mondeca 3, cité Nollez 75018 Paris France Tel. +33 (0)1 44 92 35 07 - fax +33 (0)1 44 92 02 59 Mail: pierre-yves.vandenbuss...@mondeca.com Website: www.mondeca.com Blog: Leçons de choses
