...
- There is no one correct way to model a domain— there are always viable alternatives. The best solution almost always depends on the application that you have in mind and the extensions that you anticipate.
- Ontology development is necessarily an iterative process.
- Concepts in the ontology should be close to objects (physical or logical) and relationships in your domain of interest. These are most likely to be nouns (objects) or verbs (relationships) in sentences that describe your domain.
The seven step methodology follows from these principles and are:
- Determine the domain and scope of the ontology
- Consider reusing existing ontologies
- Enumerate important terms in the ontology
- Define the classes and the class hierarchy
- Define the properties of classes
- Define the facets of the slots
- Create instances
In the KMY Working Group meetings, held February through June, 2013, a first draft terms or concepts relating to the Knowledge Mobilization domain were listed and agreed upon. These concepts or classes, are listed in the Knowledge Mobilization Ontology v.0 page in this wiki. Next, the scope of that domain was identified. A critical question in that process deserves revisiting.
For what types of questions the information in the ontology should provide answers? List those here...
1.
2.
3.
Next, what are some competency questions that we can identify in order to assess the scope of the KMY?
...
What are our competency questions? List those here...
1.
Ontology Development 101: A Guide to Creating Your First Ontology
...
2.
3.
Steps two through seven were followed in designing KMY. We will review these steps and complete the review exercise by reexamining KMY Use Cases, and moving through the application (as various users) to determine what classes are redundant, what classes require refining, or do not meet our needs. The same assessment will be applied to properties.