# Modular Ontology Modeling

### Tracking #: 2806-4020

Authors:
Cogan Shimizu
Karl Hammar
Pascal Hitzler

Responsible editor:
Guest Editors ESWC 2020

Submission type:
Full Paper
Abstract:
Reusing ontologies for new purposes, or adapting them to new use-cases, is frequently difficult. In our experiences, we have found this to be the case for several reasons: (i) differing representational granularity in ontologies and in use-cases, (ii) lacking conceptual clarity in potentially reusable ontologies, (iii) lack and difficulty of adherence to good modeling principles, and (iv) a lack of reuse emphasis and process support available in ontology engineering tooling. In order to address these concerns, we have developed the Modular Ontology Modeling (MOMo) methodology, and its supporting tooling infrastructure, CoModIDE (the \textit{Comprehensive Modular Ontology IDE} -- commodity''). MOMo builds on the established eXtreme Design methodology, and like it emphasizes modular development and design pattern reuse; but crucially adds the extensive use of graphical schema diagrams, and tooling that support them, as vehicles for knowledge elicitation from experts. In this paper, we present the MOMo workflow in detail, and describe several {\color{ForestGreen} useful resources for executing it. In particular, we} provide a thorough and rigorous evaluation of CoModIDE in its role of supporting the MOMo methodology's graphical modeling paradigm. We find that CoModIDE significantly improves approachability of such a paradigm, and that it displays a high usability.
Revised Version:
Previous Version:
Tags:
Reviewed

Decision/Status:
Minor Revision

Solicited Reviews:
Click to Expand/Collapse
Review #1
By Christoph Lange submitted on 30/Aug/2021
 Suggestion: Accept Review Comment: The revised manuscript addresses all reviewers' concerns in a convincing way. A few minor linguistic mistakes remain. Please find them annotated at https://www.dropbox.com/s/mma8hbkk3oebh82/swj2806.pdf?dl=0. Other than that, I have one remark about the newly added scientific content: in Section 3.6.3, you argue that "ideally [the] workflow [of keeping track of requirements and their provenance, from use case descriptions through competency questions through key notions and subsequently modules] is supported by integrated requirements management tooling that provides traceability of those requirements." What tool could play this role in the context of ontology engineering?
Review #2
Anonymous submitted on 06/Sep/2021