Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling property inheritance in SHACL shapes #205

Open
costezki opened this issue Jul 23, 2024 · 1 comment
Open

Handling property inheritance in SHACL shapes #205

costezki opened this issue Jul 23, 2024 · 1 comment
Labels
type: feature request something requested to be implemented in a future release
Milestone

Comments

@costezki
Copy link
Collaborator

costezki commented Jul 23, 2024

ePO issue 664 discusses how to handle property inheritance in the generated OWL and SHACL shapes.

This is a new feature that can be implemented in model2owl.

Overview:
This issue involves enhancing the model2owl tool to handle property inheritance when generating OWL and SHACL shapes from UML models. The goal is to ensure that property inheritance in UML diagrams is accurately reflected in the generated OWL and SHACL artefacts. This enhancement is related to ePO Issue #664, which addresses property inheritance handling in SHACL.

Acceptance Criteria:

  • UML conventions related to property inheritance are documented and integrated into the conventions set (aka StyleGuide) in model2owl documentation.
  • Formal transformation rules for handling property inheritance are written and documented in the model2owl documentation.
  • UML checkers for validating property inheritance are defined and implemented.
  • The transformation process successfully handles property inheritance according to the documented formal transformation rules.
  • Thorough testing of the solution is conducted, with appropriate unit tests demonstrating correct behavior.
@costezki costezki added the type: feature request something requested to be implemented in a future release label Jul 23, 2024
@rousso rousso added this to the 3.0.0 milestone Oct 13, 2024
@rousso
Copy link
Contributor

rousso commented Oct 13, 2024

@cristianvasquez the description is vague. Please provide a clear description for this ticket.

@cristianvasquez cristianvasquez removed their assignment Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request something requested to be implemented in a future release
Projects
None yet
Development

No branches or pull requests

3 participants