-
Notifications
You must be signed in to change notification settings - Fork 10
Ontop Preferences
Ontop offers many different pereferences for users to configure it considering their needs. Ontop can be configured both from Protege plugin and from source code.
Go to Launcher -> Preferences -> Quest to configure Ontop preferences.
#####Data Configuration
Ontop presents two kind of data configuration mode: Virtual ABox and Classic ABox. This configuration defines how data assertions are given to the system.
'''Virtual Abox Mode:''' In this mode Ontop gets as input an RDFS/OWL2QL ontology and an .obda file which includes a set of mappings. By using the mappings, Ontop translates SPARQL queries over the ontology into SQL queries over database.
'''Classic ABox Mode:''' In this mode Ontop gets as input an ontology and data triples/ABox assertions. In this respect, Ontop works similarly to a traditional OWL reasoner or triple store. The interesting aspect of this mode is that Quest uses the same mechanism for query answering as the one used in virtual mode. That is, Quest will also use an OBDA model and a RDBMS during query answering; however, in this case the database (schema and data) and the mappings of the OBDA model are defined and man- aged by Quest itself.
'''Schema organization strategy of Classic ABox:''' The options for shema organization strategy are Direct and Semantic Index. '''Semantic Index:''' Ontop uses one table for each type of assertions, i.e., class, object, and data property assertions (in the last case one for each value domain)