Abstract

Ontologies are supposed to address the problem of making information systems’ conceptual models shareable and understandable. Most often, however, ontologies are nothing but structured lexical resources, which bring with them the classic problem behind natural language meanings: how to make sure that names and predicates are consistently interpreted all through the information sphere? Here is where formal ontology comes to play. In fact, the ‘ontological level’ [1, 3] is where, thanks to formal constraints (meaning axioms), unintended models (spurious interpretations) should be cut off. Yet, interpreting well-founded, highly formalized ontologies is far from trivial, and does not come for free. What makes ontology so difficult in practice? How to make concepts understandable and alleviate the burden of mapping strict ontological specifications with business data? This short paper will provide a brief overview on common issues when working with formal ontology and how to address them in practice, and will give some hint on effective usages of highly formalized shared conceptual models for business information systems.

Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call