0.25
0.5
0.75
1.25
1.5
1.75
2
Test-Driven Development of Ontologies
Published on Jul 28, 20161160 Views
Emerging ontology authoring methods to add knowledge to an ontology focus on ameliorating the validation bottleneck. The verification of the newly added axiom is still one of trying and seeing what th
Related categories
Chapter list
Test-Driven Development of Ontologies00:00
Outline - 100:19
Outline - 200:31
Ontology Development Interface (Protege) - 100:32
Ontology Development Interface (Protege) - 200:50
Ontology Development Interface (Protege) - 301:12
Untitled01:12
Introduction: Ontology authoring01:14
Several scenarios of TDD usage in ontology authoring - 102:29
Several scenarios of TDD usage in ontology authoring - 203:36
Recap TDD in software development04:13
TDD in conceptual modelling [Tort et al.(2011)]04:59
Tests in ontology engineering - 105:21
Tests in ontology engineering - 205:56
Outline - 306:11
General, default, process Test-Driven Development06:20
TDD test specification, preliminaries07:20
Example: TBox TDD test with SPARQL-OWL08:34
Example: ABox TDD test with SPARQL-OWL09:08
Example: an ABox-based Test of of an RBox axiom09:55
Outline - 410:22
Design considerations and issues10:29
TDDOnto11:03
Screenshots TDDonto - 111:19
Screenshots TDDonto - 211:45
Evaluation - 112:15
Evaluation - 213:02
Mock objects (light blue) vs. SPARQL-OWL (dark blue)13:56
Hypothesis H114:28
Ontology classification and test computation times per ontology axiom count (ABox)14:59
Classification vs TDD TBox-level, OWL 2 DL, by size15:25
Hypothesis H215:44
Outline - 516:49
Implementation issue16:53
Methodology sketch18:49
Outline - 619:56
Conclusions19:59
References I20:46
References II20:49
References III20:51
Thank you20:55