| Line 18: | Line 18: | ||
* ''CiClass_xCjClass_y'', ''Ci_Class_xClass_y'': These classes participate in multiple inheritance relationships combining different refinements from the alternative abstraction criteria classes (''C1Class3_C2Class2'' and ''C1_Class1Class2'' in the Figure above). | * ''CiClass_xCjClass_y'', ''Ci_Class_xClass_y'': These classes participate in multiple inheritance relationships combining different refinements from the alternative abstraction criteria classes (''C1Class3_C2Class2'' and ''C1_Class1Class2'' in the Figure above). | ||
}} | }} | ||
| − | {{Architectural OP Example Template}} | + | {{Architectural OP Example Template |
| + | |Problem=http://ontologydesignpatterns.org/wiki/Image:Fig_avizienis_fault_5a.jpg | ||
| + | }} | ||
{{Architectural OP Reference Template}} | {{Architectural OP Reference Template}} | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| Name | View Inheritance |
|---|---|
| Also known as | |
| Author(s) | Benedicto Rodriguez-Castro, Hugh Glaser |
| Domain (if applicable) | |
| Submitted by | BenedictoRodriguezCastro, Hugh Glaser |
| 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 |
| Problem example | http://ontologydesignpatterns.org/wiki/Image:Fig_avizienis_fault_5a.jpg |
|---|---|
| Solution example | |
| Consequences |
| Origin | |
|---|---|
| Known use | |
| Reference | |
| Related ODP |
No scenario is added to this Content OP.
This revision (revision ID 5638) takes in account the reviews: none
Other info at evaluation tab