Nine month progress report submitted for continuation towards a PhD
Toward a Canonical Method to Solve Patterns of Ontology Modelling Issues 11 ____________________________________________________________________________________________________________Faults is-a is-a is-aThis property value is a necessary and sufficient condition for all faults of type development fault This property value is a necessary condition for all faults of type development fault This property value is a necessary and sufficient condition for all faults of type physical fault This property value is a necessary and sufficient condition for all faults of type interaction fault This property value is a necessary condition for all faults of type interaction faultFigure 3 - Matrix representation of the classes of combined faults. For ReSIST, and again with application use in mind, it would seem unnecessary to create classes for all types of faults, provided that users of the knowledge base may never populate many of those classes with any instances, simply because they may not describe their research interest in those terms. For this reason, ontology use, together with the notion of building an ontology fit for purpose, it would not deem appropriate attempting to model all the information conveyed by Figures 1 to 3, in terms of one class for every type of fault, with the additional need to provide axioms, domain and range information for each class. This addresses the question of how much information to model. Selecting an adequate level of detail to model would