Posts in category sparql

Resolving RDF Relationship-targets at Runtime

From  Jeni Tennison: On Resolvability:

There are three ways of locating the documentation about a particular property or class:

1) looking through the general documentation the data publisher has provided
2) resolving the URI of the class or property
3) searching

Using URIs for classes and properties provides a mechanism for applications to get hold of this extra information about unknown vocabularies. They might try four tactics, in order of priority:

1) look at the data they already know; the information they need about the unknown properties and classes may be included in the files they’ve already accessed (including those containing data)
2) look in an application-specific (possibly cloud-hosted) cache of vocabularies that the application has already downloaded
3) resolve the URI of the class or property by performing an HTTP GET (and add it to the application-specific cache)
4) look in a general-purpose cache, such as the Internet Archive or an ontology repository such as Swoogle

Generic API's:

SPARQL Endpoints:

edit: strange - a Sindice Api call returns an XML resultset alright, but the contained URI of that query itself (seems to be ment as a self-reference) leads nowhere. See for example: