You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue involves enhancing the model2owl tool to support a new modelling feature for related properties as described in ePO#737 The related task will provide a specification of the modelling feature that will be the basis for this task. The modelling feature has been tentatively identified as property overriding, but the outcome of the related task will provide a definitive specification that will inform this task.
This task requires the implementer to:
Identify suitable OWL and SHACL representations: Given the UML specification, define how the related properties will be represented in both SHACL and OWL. The OWL representation needs to reflect the intended semantic and SHACL shapes have to contain constraints for validation purposes.
Define, document and implement transformation rules: Define transformation rules for generating the artefacts from the UML model. These need to be documented in the model2owl documentation and implemented in model2owl codebase.
Provide conventions and checkers if possible: Analyze the UML modelling approach and determine if UML conventions and checkers can be identified for the UML representation in order to set rules for creating UML model and validation rules for ensuring correctness. If possible, the conventions and checkers should be documented, and the checkers implemented in model2owl.
The issue involves enhancing the model2owl tool to support a new modelling feature for related properties as described in ePO#737 The related task will provide a specification of the modelling feature that will be the basis for this task. The modelling feature has been tentatively identified as property overriding, but the outcome of the related task will provide a definitive specification that will inform this task.
This task requires the implementer to:
Note
This ticket depends on ePO#737.
The text was updated successfully, but these errors were encountered: