TY - JOUR
T1 - Learning the differences between ontologies and conceptual schemas through ontology-driven information systems
AU - Fonseca, Frederico
AU - Martin, James
PY - 2007
Y1 - 2007
N2 - In the traditional systems modeling approach, the modeler is required to capture a user's view of some domain in a formal conceptual schema. The designer's conceptualization may or may not match with the user's conceptualization. One of the reasons for these conflicts is the lack of an initial agreement among users and modelers concerning the concepts belonging to the domain. Such an agreement could be facilitated by means of an ontology. If the ontology is previously constructed and formalized so that it can be shared by the modeler and the user in the development process, such conflicts would be less likely to happen. Following up on that, a number of investigators have suggested that those working on information systems should make use of commonly held, formally defined ontologies that would constrain and direct the design, development, and use of information systems - thus avoiding the above mentioned difficulties. Whether ontologies represent a significant advance from the more traditional conceptual schemas has been challenged by some researchers. We review and summarize some major themes of this complex discussion. While recognizing the commonalities and historical continuities between conceptual schemas and ontologies, we think that there is an important emerging distinction that should not be obscured and should guide future developments. In particular, we propose that the notions of conceptual schemas and ontologies be distinguished so as to play essentially different roles for the developers and users of information systems. We first suggest that ontologies and conceptual schemas belong to two different epistemic levels. They have different objects and are created with different objectives. Our proposal is that ontologies should deal with general assumptions concerning the explanatory invariants of a domain - those that provide a framework enabling understanding and explanation of data across all domains inviting explanation and understanding.
AB - In the traditional systems modeling approach, the modeler is required to capture a user's view of some domain in a formal conceptual schema. The designer's conceptualization may or may not match with the user's conceptualization. One of the reasons for these conflicts is the lack of an initial agreement among users and modelers concerning the concepts belonging to the domain. Such an agreement could be facilitated by means of an ontology. If the ontology is previously constructed and formalized so that it can be shared by the modeler and the user in the development process, such conflicts would be less likely to happen. Following up on that, a number of investigators have suggested that those working on information systems should make use of commonly held, formally defined ontologies that would constrain and direct the design, development, and use of information systems - thus avoiding the above mentioned difficulties. Whether ontologies represent a significant advance from the more traditional conceptual schemas has been challenged by some researchers. We review and summarize some major themes of this complex discussion. While recognizing the commonalities and historical continuities between conceptual schemas and ontologies, we think that there is an important emerging distinction that should not be obscured and should guide future developments. In particular, we propose that the notions of conceptual schemas and ontologies be distinguished so as to play essentially different roles for the developers and users of information systems. We first suggest that ontologies and conceptual schemas belong to two different epistemic levels. They have different objects and are created with different objectives. Our proposal is that ontologies should deal with general assumptions concerning the explanatory invariants of a domain - those that provide a framework enabling understanding and explanation of data across all domains inviting explanation and understanding.
UR - http://www.scopus.com/inward/record.url?scp=51449093619&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=51449093619&partnerID=8YFLogxK
U2 - 10.17705/1jais.00114
DO - 10.17705/1jais.00114
M3 - Review article
AN - SCOPUS:51449093619
SN - 1558-3457
VL - 8
SP - 129
EP - 142
JO - Journal of the Association for Information Systems
JF - Journal of the Association for Information Systems
IS - 2
ER -