On 8-10-2013 12:22, Pieter Colpaert wrote:
Hi Frans,
Perhaps VoID could help if you create your own feature [1] which
describes your limitation added on the server?
Thanks, I did not know about this part of VoID. But two things make me
wonder if it is appropriate:
1) Void:feature can be used for expressing certain technical features of
a dataset. But a dataset and a SPARQL endpoint are different things,
aren't they?
2) If I make up my own way of publishing endpoint metadata, how are
other parties ever going to find those data?
As a sidenote, maybe next to a SPARQL endpoint, just providing the
datadumps would be great as well?
Yes, I guess that is certainly a good idea. It will be of help for some
of the usage scenarios.
[1] http://www.w3.org/TR/void/#features
Kind regards,
Pieter
On 10/08/2013 12:05 PM, Barry Norton wrote:
Frans, SPARQL 1.1 introduced the notion of Service Descriptions [1].
Although these probably don't go far enough in the standard they are,
I believe, extensible.
Barry
[1] http://www.w3.org/TR/sparql11-service-description/
On Tue, Oct 8, 2013 at 10:46 AM, Frans Knibbe | Geodan
<[email protected] <mailto:[email protected]>> wrote:
Hello,
I am experimenting with running SPARQL endpoints and I notice the
need to impose some limits to prevent overloading/abuse. The
easiest and I believe fairly common way to do that is to LIMIT the
number of results that the endpoint will return for a single query.
I now wonder how I can publish the fact that my SPARQL endpoint
has a LIMIT and that is has a certain value.
I have read the thread Public SPARQL endpoints:managing (mis)-use
and communicating limits to users
<http://lists.w3.org/Archives/Public/public-lod/2013Apr/0198.html>, but
that seemed to be about how to communicate limits during querying.
I would like to know if there is a way to communicate limits
before querying is started.
It seems to me that a logical place to publish a limit would be in
the metadata of the SPARQL endpoint. Those metadata could contain
all limits imposed on the endpoint, and perhaps other things like
a SLA or a maintenance schedule... data that could help in the
proper use of the endpoint by both software agents and human users.
So perhaps my enquiry really is about a standard for publishing
SPARQL endpoint metadata, and how to access them.
Greetings,
Frans
--------------------------------------
*Geodan*
President Kennedylaan 1
1079 MB Amsterdam (NL)
T +31 (0)20 - 5711 347 <tel:%2B31%20%280%2920%20-%205711%20347>
E [email protected] <mailto:[email protected]>
www.geodan.nl <http://www.geodan.nl> | disclaimer
<http://www.geodan.nl/disclaimer>
--------------------------------------
--
--------------------------------------
*Geodan*
President Kennedylaan 1
1079 MB Amsterdam (NL)
T +31 (0)20 - 5711 347
E [email protected]
www.geodan.nl <http://www.geodan.nl> | disclaimer
<http://www.geodan.nl/disclaimer>
--------------------------------------
