2011
DOI: 10.1007/978-3-642-21034-1_22
|View full text |Cite
|
Sign up to set email alerts
|

The Use of Foundational Ontologies in Ontology Development: An Empirical Assessment

Abstract: Abstract. There is an assumption that ontology developers will use a top-down approach by using a foundational ontology, because it purportedly speeds up ontology development and improves quality and interoperability of the domain ontology. Informal assessment of these assumptions reveals ambiguous results that are not only open to different interpretations but also such that foundational ontology usage is not foreseen in most methodologies. Therefore, we investigated these assumptions in a controlled experime… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

2
27
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
6
2
1

Relationship

2
7

Authors

Journals

citations
Cited by 36 publications
(29 citation statements)
references
References 16 publications
2
27
0
Order By: Relevance
“…It is known one can improve on one's low precision-i.e., the ontology admits more models than it should-by using a more expressive language and adding more class expressions, but this is easier said than done (except for the new tool to add more disjointness axioms (Ferré and Rudolph, 2012)). For domain ontologies, another option that influences to notion of being wellknown and mature is its linking to a foundational ontology and that therewith less modelling issues occur (Keet, 2011), but this has to do with the knowledge that is represented, not with, e.g., language feature misunderstandings. We leave a more detailed investigation in this direction for future works.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…It is known one can improve on one's low precision-i.e., the ontology admits more models than it should-by using a more expressive language and adding more class expressions, but this is easier said than done (except for the new tool to add more disjointness axioms (Ferré and Rudolph, 2012)). For domain ontologies, another option that influences to notion of being wellknown and mature is its linking to a foundational ontology and that therewith less modelling issues occur (Keet, 2011), but this has to do with the knowledge that is represented, not with, e.g., language feature misunderstandings. We leave a more detailed investigation in this direction for future works.…”
Section: Discussionmentioning
confidence: 99%
“…Distinguishing between file name and URI. This is related to naming issues where the .owl file has a meaningful name, but the ontology URI has a different name (also observed in (Keet, 2011)). C3.…”
Section: Candidate Pitfallsmentioning
confidence: 99%
“…Effectively, our approach is defined and specified by the following statements: 1) Modularize the ontology into small reusable modules or fragments (upper, core, domain and domain-specific) which are themselves ontologies. 2) Use of foundational ontologies, from the start of the ontology building process, to facilitate the ontology development by preventing to reinvent the wheel concerning basic categories and relations [14] and to improve overall quality and semantic interoperability of conceptual models [15]. 3) Use of legal-core ontologies, such as LKIF-Core [7], in the development process of the ontology specifically for modeling the core module.…”
Section: Proposed Middle-out Approachmentioning
confidence: 99%
“…There are multiple good reasons to use a foundational ontology in theory, and it has been shown to improve the ontology quality, understandability, and interoperability in praxis [17]. It comes at the 'cost' for figuring out how to align a domain ontology with it, and it can have implications for the language used for the overall ontology.…”
Section: Alignment Of Dmop With a Foundational Ontologymentioning
confidence: 99%