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: Criterion_i: These classes represent each one of the alternative abstraction criteria of the TargetDomainConcept (Criterion1, Criterion2, Criterion_i in the Figure above). The list of classes may not be exhaustive or pairwise disjoint. Ci_Class_x: These classes refine each abstraction criteria class (C1_Class1, ..., C2_Class1, ..., Ci_Class_i in the Figure above). The list of classes may not be exhaustive or pairwise disjoint. 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).
Implementation workflow
Reusable component

{{Architectural OP Example Template |Problem=

Scenarios about View Inheritance

No scenario is added to this Content OP.

Reviews about View Inheritance

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 5640) takes in account the reviews: none