- From: Daniel Schwabe <dschwabe@inf.puc-rio.br>
- Date: Sat, 07 Mar 2009 00:36:47 -0300
- To: Kingsley Idehen <kidehen@openlinksw.com>
- CC: public-lod@w3.org
Kingsley , Giovanny, Michael and all, thanks for the prompt replies. I didn't express myself properly. I'm looking for a programmatic way to find the SPARQL endpoint, something analogous to a DNS -> ip translation. This metaphor breaks down right away, as there is no centralized service where I can query - this is what I was trying to emulate with Sindice, by issuing a query for the void:sparqlEndpoint property, given the dataset's home URL. Hopefully, if there is one, Sindice would have indexed it. I could query the site for its sitemap extension (would it always be <home url>/sitemap.xml? doesn't seem so...), as Giovanni suggests, and see if I get a result; in the affirmative case, I have to parse it and look for the <sc:sparqlEndpointLocation> element. As Michael Lang put it, one could have a Dataset Registry, but again I would want to have a way to query it programmatically. In addition, it would be a centralized resource. Hence my suggestion - I am looking for a simple way to enable autodiscovery. If all sites would agree to make the sitemap.xml available at <home url>/sitemap.xml, that would work as well. I just think that a simple naming convention such as <home url>/sparql would be even easier to implement, and it may become one of those "de facto" standards if the main datasets follow the convention... (as I said, many already do...) Cheers D
Received on Saturday, 7 March 2009 03:37:31 UTC