Submissions:View Inheritance
From Odp
(Difference between revisions)
Line 36: | Line 36: | ||
}} | }} | ||
{{Architectural OP Reference Template | {{Architectural OP Reference Template | ||
- | |Origin= | + | |Origin=Object Oriented: |
* Meyer, B.: Object-Oriented Software Construction (Book/CD-ROM) (2nd Edition). Prentice Hall PTR (March 2000) | * Meyer, B.: Object-Oriented Software Construction (Book/CD-ROM) (2nd Edition). Prentice Hall PTR (March 2000) | ||
+ | Ontology: | ||
* Rector, A.L.: Modularisation of domain ontologies implemented in description logics and related formalisms including owl. In: K-CAP '03: Proceedings of the 2nd international conference on Knowledge capture, New York, NY, USA, ACM (2003) 121--128 | * Rector, A.L.: Modularisation of domain ontologies implemented in description logics and related formalisms including owl. In: K-CAP '03: Proceedings of the 2nd international conference on Knowledge capture, New York, NY, USA, ACM (2003) 121--128 | ||
|RelatedTo=Normalization, Classes As Property Values, Multiple Inheritance | |RelatedTo=Normalization, Classes As Property Values, Multiple Inheritance |
Revision as of 20:31, 29 August 2009
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 5655 |
General information
Name | View Inheritance |
---|---|
Also known as | |
Author(s) | Benedicto Rodriguez-Castro, Hugh Glaser |
Domain (if applicable) | |
Submitted by | BenedictoRodriguezCastro, HughGlaser |
Description
Problem description | There are ontology domain concepts that are difficult to represent due to the complexities in their definition and the presence of multiple alternative criteria to classify their abstractions. |
---|---|
Solution description | Introduce the following types of classes:
|
Implementation workflow | |
Reusable component |
Example
Problem example | |
---|---|
Solution example | Figure above in particular, shows a matrix representation of all types of faults which may affect a system during its life. Implicitly, the figure reveals several alternative criteria for the classification of faults:
|
Consequences | Inter- and Intra-criterion Multiple Inheritance.
There is an interesting feature regarding the types of multiple inheritance relations that can take place in the context of a View Inheritance pattern. These types of multiple inheritance relationships can be characterized as:
|
Pattern reference
Origin | Object Oriented:
Ontology:
|
---|---|
Known use | |
Reference | |
Related ODP | Normalization, Classes As Property Values, Multiple Inheritance |
Scenarios
Scenarios about View Inheritance
No scenario is added to this Content OP.
Reviews
Reviews about View Inheritance
There is no review about this proposal. This revision (revision ID 5655) takes in account the reviews: none
Other info at evaluation tab