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
E [email protected]
www.geodan.nl <http://www.geodan.nl> | disclaimer
<http://www.geodan.nl/disclaimer>
--------------------------------------
