EnricoDaga (Talk | contribs) |
(Article updated via HTTP request) |
||
| Line 12: | Line 12: | ||
{{My references}} | {{My references}} | ||
{{Modeling Issue toolbar}} | {{Modeling Issue toolbar}} | ||
| + | <noinclude>=====5-03-2010 [[User:MichaelUschold]] says:===== | ||
| + | This is a response to the comment left by Bene Rodriguez-Castro. | ||
| + | |||
| + | A description logic provides a very natural way to characterize concepts/classes by multiple criteria using the idea of a restriction. Furthermore, the classification hierarchy is generated automatically for you. | ||
| + | |||
| + | The elaboration you gave is a very good continuation of this issue. Feel free to move some of it into the main issue page.</noinclude> | ||
Title: View Inheritance
Description: Representation of multiple alternative abstraction criteria of a certain ontology domain concept
Diagram (this article has no graphical representation)
| Users | BenedictoRodriguezCastro, HughGlaser |
|---|---|
| Domains | General |
| Competency Questions | |
| Scenarios | |
| Proposed Solutions (OWL files) | |
| Related patterns | |
This is a response to the comment left by Bene Rodriguez-Castro.
A description logic provides a very natural way to characterize concepts/classes by multiple criteria using the idea of a restriction. Furthermore, the classification hierarchy is generated automatically for you.
The elaboration you gave is a very good continuation of this issue. Feel free to move some of it into the main issue page.
'Ontology Design Patterns'