In the context of the ePO conceptual model, certain cases of relationships between properties are expressed as inheritance. However, as reported in ePO#666, concerns have been raised that it may not be the suitable way to model some cases that expect exclusively a subproperty in a subclass. Additionally, an analysis conducted as a part of model2owl#205 revealed that it is not possible to properly support such cases with inheritance. Specifically, applying inheritance in these cases leads to contradictions in the OWL representation of the model. Therefore, the modelling approach needs to be revised in order to choose the most suitable approach for the existing cases. Property overriding has been proposed as a potential alternative to inheritance, but further identification and analysis of use cases are needed before a decision can be made.
The concerning cases identified so far expect a subproperty to be used in data and not superproperty, as presented in the example in ePO#632. That cannot be expressed with inheritance that has been used so far as it implies both subproperty and superproperty for a subclass.
The task requires the following actions to be taken and relevant artefacts to be prepared:
- Identification and documentation of relevant cases: Identify and document existing cases of dependent properties that fall within the scope of potential candidates for property overriding (ePO#632 and ePO#635)
- Analysis of modeling approaches: Analyze the identified cases, understand the requirements behind them and research suitable modeling techniques, such as property overriding or alternatives like disjointness. Document findings, including reasoning for the selected approach.
- Proposal for UML representation: Develop a proposal for how the chosen modeling approach should be represented in the UML (CM)
- Feasibility assessment for model2owl: Review the proposed approach in the context of model2owl. Coordinate with the model2owl team to ensure the solution is feasible and can be implemented.
- Final documentation and review: Produce final documentation that summarizes the analysis, decisions, and proposals made.
In the context of the ePO conceptual model, certain cases of relationships between properties are expressed as inheritance. However, as reported in ePO#666, concerns have been raised that it may not be the suitable way to model some cases that expect exclusively a subproperty in a subclass. Additionally, an analysis conducted as a part of model2owl#205 revealed that it is not possible to properly support such cases with inheritance. Specifically, applying inheritance in these cases leads to contradictions in the OWL representation of the model. Therefore, the modelling approach needs to be revised in order to choose the most suitable approach for the existing cases. Property overriding has been proposed as a potential alternative to inheritance, but further identification and analysis of use cases are needed before a decision can be made.
The concerning cases identified so far expect a subproperty to be used in data and not superproperty, as presented in the example in ePO#632. That cannot be expressed with inheritance that has been used so far as it implies both subproperty and superproperty for a subclass.
The task requires the following actions to be taken and relevant artefacts to be prepared: