| GraphicallyRepresentedBy
|
Normalisation abstract.png +
|
| LogicalODPAim
|
To untangle a polyhierarchy, coding the su … To untangle a polyhierarchy, coding the subsumption relationships using restrictions rather than class-subclass relationships. The application example for this ODP is adapted from the Cell Type Ontology. In the example, the subsumption relationships that already are in the Cell Type Ontology are inferred by the reasoner instead of hard-coded. The term Neutrophil is used as an example class to show how a class can relate to different modules. w a class can relate to different modules.
|
| LogicalODPAlsoKnownAs
|
Modularization +,
Untangling +
|
| LogicalODPAuthor
|
AlanRector +,
MikelEganaAranguren +
|
| LogicalODPConsequence
|
The ontology gets untangled and becomes a collection of neat modules. The rest of the semantics are given by restrictions pointing to the modules, and the reasoner maintains the structure, avoding error-prone human maintenance of the polyhierarchy.
|
| LogicalODPElements
|
The original classes of the ontology are divided in different axes. The conditions for each subsumption relationship are encoded as restrictions (e.g. [PerformsFunction some Defense]) that will relate the different modules.
|
| LogicalODPKnownUse
|
See [[Community:References/Modularisation of domain ontologies implemented in description logics and related formalisms including owl 3|(Rector, 2003)]]
|
| LogicalODPMotivation
|
There are ontologies where a given class c … There are ontologies where a given class can have plenty of superclasses, building a polyhierarchy. If all those subsumption relationships are directly stated by the ontology maintainer, two main problems rise: (i) the ontology becomes very difficult to maintain: whenever a subsumption must be deleted (because a class has changed) or created (because a new class has been created) it has to be done by hand; in a polyhierarchy the process becomes very inefficient and error-prone. (ii) the semantics are implicitly stated, not explicitly: any other ontologist or reasoner only knows that a class is a subclass of its superclasses, without knowing why. of its superclasses, without knowing why.
|
| LogicalODPName
|
Normalization +
|
| LogicalODPOrigin
|
See [[Community:References/Modularisation of domain ontologies implemented in description logics and related formalisms including owl 3|(Rector, 2003)]]
|
| LogicalODPSample
|
http://ontologydesignpatterns.org/wiki/Image:Normalisation_instance.png +
|
| LogicalODPScenario
|
[[Image:Normalisation_instance.png|center]]
|
| LogicalODPWorkflow
|
Identify the modules: group the classes. C … Identify the modules: group the classes. Create the modules, maintaining only one parent for any given primitive class and making primitive siblings disjoint. Redefine the classes (or define the newly added classes) according to the conditions for belonging to each module. Protege includes a wizard, the restrictions matrix, that helps in the process. ictions matrix, that helps in the process.
|
| Modification dateThis property is a special property in this wiki.
|
23 September 2010 12:38:55 +
|
| SubmittedBy
|
BenedictoRodriguezCastro +
|
| Categories |
LogicalOP +,
ProposedLogicalOP +,
Review assigned +
|
