Ontology Testing - Methodology and Tool

ArCo: The Italian Cultural Heritage Knowledge Graph

“…To detect any incoherence in the ontologies, we regularly run a reasoner, HermiT, during the modeling phase. Then, to evaluate the appropriateness of the ontologies against requirements, we follow the methodology described in [5], which focuses on testing an ontology against its requirements, intended as the ontological commitment expressed by means of CQs and domain constraints. All testing activities and resulting data (OWL files complying to the ontology described in [5]) are documented in a specific section of ArCo's GitHub repository.…”

Themis: a tool for validating ontologies through requirements

“…Another work related to ontology testing tools is Scone, 4 a tool for scenario-based ontology evaluation, which is based on Cucumber 5 and uses controlled natural language to define ontology scenarios which create mock individuals. Additionally, Blomqvist et al [10] presented an agile approach and tool available as an Eclipse plugin. This tool supports three types of test, namely: (1) verification example, (2) inference verification and (3) error provocation.…”

“…Carnivora and Sirenia using the guidelines provided in Themis website 10. As an example, the user can enter the test expression Event sub-ClassOf InteractionPattern in order to check a subsumption relation in the ontology expected from the requirement "An event is a type of Interaction pattern".Additionally, Themis allows the users to export a set of test expressions, i.e., a test suite, as an RDF file in order to be able to reuse it.Listing 1 shows an example of the test expressions Action subClassOf InteractionPattern and Event subClassOf InteractionPattern in RDF syntax.…”

Test-Driven Development of Ontologies

“…Unlike extensive CQ and query patters, it specifies different types of tests focussed on the ABox rather than knowledge represented in the TBox, such as "instantiation tests" (instance checking) and "recovering tests" (query for a class' individuals) and using mock individuals where applicable [8]; other instance-oriented test approaches have been proposed as well, although focussing on RDF/Linked Data rather than the OWL ABox [19]. A NeON plugin with similar functionality and methodical steps within the eXtreme Design approach also has been proposed [3], but not the types of tests. A more basic variant is incorporated in the EFO Validator 3 for the Experimental Factor Ontology (EFO), which has tests for presence of a specific class or relation.…”

“…They are examples of generic, high-level information systems-oriented methodologies, but support for effective ontology authoringadding the right axioms and adding the axioms right-has received some attention only more recently. Processes at this 'micro' level of the development process, rather than the 'macro' level, may use the reasoner to propose axioms with FORZA [16], use Ontology Design Patterns (ODPs) [7], and start gleaning ideas from software engineering practices, notably exploring the notion of unit tests [35], eXtreme Design with ODPs [3], and Competency Question (CQ)-based authoring using SPARQL [28]. However, testing whether a CQ can be answered does not say how to add/change the knowledge represented in the ontology, FORZA considers simple object properties only, and eXtreme Design limits one to ODPs that have to come from some place.…”