Best practice check: Finding a SPARQL endpoint by an LOD URI

[pablomendes]

On Wed, Jul 4, 2012 at 7:45 AM, Heiko Paulheim
http://www.ke.tu-darmstadt.de/staff/heiko-paulheim

Hi all,

I am wondering whether there is a way of finding a SPARQL endpoint for an
LOD URI, i.e., a function f that behaves like
f(http://dbpedia.org/resource/Darmstadt) = http://dbpedia.org/sparql

TimBL's design issues document [1] says:
"To make the data be effectively linked, someone who only has the URI of
something must be able to find their way the SPARQL endpoint. [...]
Vocabularies for doing this have not yet been standardized."

Is that still the state of affairs? Are there any practical workarounds?

[1] http://www.w3.org/DesignIssues/LinkedData.html

From: Keith Alexander (keithalexander.co.uk)
Date: Wed, Jul 4, 2012 at 9:13 AM

Hi,

http://www.w3.org/TR/void/#discovery describes methods for publishers
to let their dataset descriptions be discovered via a Linked Data
URI.

The publisher can provide a 'back link' in the RDF they return from
the RDF document, to the dataset URI (which then provides a link to
the SPARQL endpoint)
eg:

foaf:isPrimaryTopicOf .
void:inDataset .

Or the publisher can make their dataset description available at
{their domain}/.well-known/void

Sadly I am not sure how wide-spread either of those are amongst
dataset publishers.

As a consumer, you could try going to:

http://dsi.lod-cloud.net/sparql
and querying for

PREFIX void: http://rdfs.org/ns/void#
select distinct ?dataset ?sparql where {
?dataset void:uriSpace ?urispace ; void:sparqlEndpoint ?sparql .
filter(regex('{your URI}', ?urispace))
}