Odp:WhatIsAnExemplaryOntology
From Odp
(Difference between revisions)
m |
Current revision (04:48, 18 February 2010) (view source) |
||
| (7 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
| - | An exemplary ontology is one that can serve as a model that can be imitated or leveraged by | + | * [[Ontology:Main|Visit the catalogue of Exemplary Ontologies]] |
| + | * [[ODP:Exemplary ontology FAQ| Exemplary Ontologies FAQ]] | ||
| + | |||
| + | ==What is an Exemplary Ontology?== | ||
| + | An exemplary ontology is one that can serve as a model that can be imitated or leveraged by ontology engineers in the future. The most fundamental property of an exemplary ontology is being ''well designed for its intended purpose''. Think of a paper clip - from a purely utilitarian perspective, it went through many stages of evolution before it became a thing of elegant simplicity - linked to a specific purpose. From a design perspective it is a thing of beauty. Nothing is extraneous, it just works. So it is with any well designed artifact. Any ontology that has reached a similar pinnacle of good design will have many of the following properties: | ||
# well designed for its purpose. | # well designed for its purpose. | ||
# explicitly stated requirements (especially competency questions) were specified and used to guide the design process. | # explicitly stated requirements (especially competency questions) were specified and used to guide the design process. | ||
| - | # meets ''all ''and for the most part, ''only ''the intended requirements | + | # meets ''all ''and for the most part, ''only ''the intended requirements; |
# does not make unnecessary commitments or assumptions | # does not make unnecessary commitments or assumptions | ||
# will be easy to extend to meet additional unknown future requirements | # will be easy to extend to meet additional unknown future requirements | ||
| Line 11: | Line 15: | ||
## instantiates known design patterns | ## instantiates known design patterns | ||
# there is a core set of primitives that are used to build up more complex parts. This is a kind of reuse within the same ontology, as opposed to reusing external ontologies and patterns. The coralary to this is: the same concepts are not created independently multiple times in different places in the ontology. | # there is a core set of primitives that are used to build up more complex parts. This is a kind of reuse within the same ontology, as opposed to reusing external ontologies and patterns. The coralary to this is: the same concepts are not created independently multiple times in different places in the ontology. | ||
| - | # easy to understand and maintain | + | # easy to understand and maintain; |
## avoids hacks and workarounds (which tend to be ugly anyway) | ## avoids hacks and workarounds (which tend to be ugly anyway) | ||
## lacks redundancy (related to point about reusing primitives) | ## lacks redundancy (related to point about reusing primitives) | ||
| Line 19: | Line 23: | ||
## includes diagrams to illustrate 1&2 above | ## includes diagrams to illustrate 1&2 above | ||
| - | The reason for the ontology meeting ''only'' the intended requirements is to keep the ontology as lean as possible. | + | The reason for the ontology meeting ''only'' the intended requirements is to keep the ontology as lean as possible. The ontology should of course contain things that help ensure that it can easily expanded to meet as yet unanticipated future requirements -- even if they are not strictly needed to meet stated requirements. |
Current revision
What is an Exemplary Ontology?
An exemplary ontology is one that can serve as a model that can be imitated or leveraged by ontology engineers in the future. The most fundamental property of an exemplary ontology is being well designed for its intended purpose. Think of a paper clip - from a purely utilitarian perspective, it went through many stages of evolution before it became a thing of elegant simplicity - linked to a specific purpose. From a design perspective it is a thing of beauty. Nothing is extraneous, it just works. So it is with any well designed artifact. Any ontology that has reached a similar pinnacle of good design will have many of the following properties:
- well designed for its purpose.
- explicitly stated requirements (especially competency questions) were specified and used to guide the design process.
- meets all and for the most part, only the intended requirements;
- does not make unnecessary commitments or assumptions
- will be easy to extend to meet additional unknown future requirements
- it reuses as much as possible
- leverages upper level ontologies where appropriate
- leverages existing domain ontologies
- instantiates known design patterns
- there is a core set of primitives that are used to build up more complex parts. This is a kind of reuse within the same ontology, as opposed to reusing external ontologies and patterns. The coralary to this is: the same concepts are not created independently multiple times in different places in the ontology.
- easy to understand and maintain;
- avoids hacks and workarounds (which tend to be ugly anyway)
- lacks redundancy (related to point about reusing primitives)
- well documented
- describes the core ideas of the ontology
- describes the core classes and relationships
- includes diagrams to illustrate 1&2 above
The reason for the ontology meeting only the intended requirements is to keep the ontology as lean as possible. The ontology should of course contain things that help ensure that it can easily expanded to meet as yet unanticipated future requirements -- even if they are not strictly needed to meet stated requirements.
