A platform-agnostic, configurable, and brandable SPARQL editor and visualization interface.
- Autocompletion of your entire ontology
- Result visualizations modes including; a table, an image grid, a pie chart, and a map
- Integration with your query library
- Shareable queries / URLs
- A resizable code editor
- An interactive tour of the GUI
- A configurable color scheme
- ...and plenty of more...
{
"sparql_endpoint": "",
"query_library_endpoint": "",
"title": "",
"demo_tour": {
"demo_query": "",
"demo_query_cursor_position": {
"line": 1,
"ch": 1
}
},
"map_background": {
"url_template": "",
"attribution": ""
},
"color_scheme": {
"main_brand": "",
"main_brand_darkened": "",
"secondary_brand": "",
"secondary_brand_darkened": "",
"main_text": "",
"main_text_lighted": "",
"secondary_text": "",
"background": "",
"background_shaded": "",
"border": ""
},
"favicons": {
"favicon_success": "",
"favicon_error": "",
"favicon_progess": ""
},
"autocomplete": {
"classes": [],
"prefixes": [],
"properties": [],
"services": [],
"uris": []
}
}The SPARQL endpoint to use. If left out, the user will be able to input their own endpoint.
The endpoint to use for the query library. If left out, the query library will be disabled.
The title of the editor.
An object for the demo tour configuration. If left out, the demo tour will be disabled. Note that the demo_query and demo_query_cursor_position can be used to trigger/demo autocompletion features as if a real user would be typing.
demo_query: The query to use for the demo tour. Use\nfor newlines.demo_query_cursor_position: The cursor position to use for the demo tour.line: The line number for the cursor position.ch: The character number for the cursor position.
Optional map background settings.
url_template: URL template for map tiles. See URL template at leafletjs.com.attribution: String to use for map attribution, can take HTML.
An object for the autocompletion configuration.
classes: An array of plain-class-URIs to autocomplete,http://schema.org/CreativeWorknotschema:CreativeWork.prefixes: An array of prefixes to autocomplete, following SPARQL format,rdfs: <http://www.w3.org/2000/01/rdf-schema#>, etc.properties: An array of plain-property-URIs to autocomplete,http://www.w3.org/2000/01/rdf-schema#labelnotrdfs:label.services: An array of federated endpoints to autocomplete,http://dbpedia.org/sparql, etc.uris: An array of URIs to autocomplete.
An object for the color scheme configuration. These are all exposed as root CSS variables so you can tweak the defaults in the browser's dev tools before adding them to the configuration.
main_brandmain_brand_darkenedsecondary_brandsecondary_brand_darkenedmain_textmain_text_lightedsecondary_textbackgroundbackground_shadedborder
A query library is a JSON file containing an array of queries. Each query is an object with the following properties:
title: The title of the query.tags: An array of tags for the query.body: The query body.
It's common to generate this JSON file from a code-snippet library or from induvidual SPARQL query files. Here is an example, generating a library from .rq files using Python.
[
{
"title": "List users by the number of monuments registered with a given tag",
"tags": [
"monuments",
"users",
"tags"
],
"body": "PREFIX schema: <http://schema.org/>\n\nSELECT ?creator (COUNT(?monument) AS ?monument_count) WHERE {\n BIND(<https://fornpunkt.se/tagg/stensattning> AS ?tag)\n ?monument schema:keywords ?tag ;\n a schema:CreativeWork ;\n schema:creator ?creator .\n}\nGROUP BY ?creator\nORDER BY DESC(?monument_count)\n"
},
]Thor only consists of static files but expects to find your config.json file in the config directory. Your query library can also be served from the config directory if you wish.