screenshot buttons
Click on the 'URL' button to get the URL of the search result and save it to the clipboard.

Linking the RelFinder

Click on the 'URL' button to get the URL of the current search result and save it to the clipboard. You can use this URL to directly link to a result.


You can also dynamically compose URLs to integrate the RelFinder with your tool. The following parameters can be defined and added to the URL of the Flash movie (swf):

  • obj1, obj2, ..., objN: The URIs of the objects between which relationships shall be searched within the dataset.
  • name: The name of the dataset which will be displayed in the settings menu.
  • abbreviation: An abbreviation (or ID) for the dataset configuration. This can be used to load the RelFinder directly with this specific configuration. (For instance, demo.swf?id=lmdb loads the RelFinder with the 'Linked Movie Data Base' configuration by default).
  • description: A description of the dataset which will be displayed in the settings menu.
  • endpointURI: The URL of the SPARQL endpoint. The RelFinder uses this URL + '/sparql?' to query the endpoint.
  • dontAppendSPARQL: Prevents the RelFinder from appending '/sparql?' to the defined endpointURI.
  • defaultGraphURI: The URI of the default graph which should be used for the search (usually not necessary).
  • isVirtuoso: If the SPARQL server is a "Virtuoso" server this value can be set to 'true'. The RelFinder will then use Virtuoso specific commands for an improved autocompletion. If you are not sure better set this value to 'false'. That should always work.
  • useProxy: If the SPARQL server has NO crossdomain.xml set this value to 'true' in order to forward all queries to the defined proxy server.
  • method: HTTP method for SPARQL requests. Possible values are POST and GET.
  • autocompleteURIs: URIs of properties that should be used for autocompletion and disambiguation features. (Usually, RDF label works fine - http://www.w3.org/2000/01/rdf-schema#label).
  • autocompleteLanguage: The language code that will be used for autocomplete (e.g., 'en' for English or 'de' for German). A language code is usually not necessary.
  • ignoredProperties: URIs of properties that should not be included in the relationship search.
  • abstractURIs: URIs of properties that provide short descriptions for the info box. (If no value for the 1st property is found, the RelFinder continues with the second property, etc.)
  • imageURIs: URIs of properties that provide images for the info box. (If no value for the 1st property is found, the RelFinder continues with the second property, etc.)
  • linkURIs: URIs of properties that provide web links for the info boxes. (The values of all given properties are displayed as links.)
  • maxRelationLegth: The maximum length of relationships that the RelFinder searches for (a value between 1 and 3 is recommended).

Note that all variables have to be Base64 encoded.


Here is how the resulting link could look like (without Base64 encoded values! - Base64 encoded version):

http://relfinder.semanticweb.org/demo.swf
?obj1=Fiat|http://dbpedia.org/resource/Fiat
&obj2=Ferrari|http://dbpedia.org/resource/Ferrari
&obj3=Maserati|http://dbpedia.org/resource/Maserati
&name=DBpedia
&abbreviation=dbp
&description=Linked Data version of Wikipedia.
&endpointURI=http://dbpedia.org/sparql
&dontAppendSPARQL=true

&defautlGraphURI=http://dbpedia.org
&isVirtuoso=true
&useProxy=false
&method=POST

&autocompleteLanguage=en
&autocompleteURIs=http://www.w3.org/2000/01/rdf-schema#label
&ignoredProperties=http://dbpedia.org/property/wikiPageUsesTemplate, http://dbpedia.org/property/wikilink, http://dbpedia.org/property/wordnet_type, http://www.w3.org/1999/02/22-rdf-syntax-ns#type, http://www.w3.org/2004/02/skos/core#subject
&abstractURIs=http://dbpedia.org/ontology/abstract
&imageURIs=http://dbpedia.org/ontology/thumbnail, http://xmlns.com/foaf/0.1/depiction
&linkURIs=http://purl.org/ontology/mo/wikipedia, http://xmlns.com/foaf/0.1/homepage, http://xmlns.com/foaf/0.1/page
&maxRelationLegth=2