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

Filter using Class Status when generating OWL #202

Open
AchillesDougalis opened this issue May 16, 2024 · 3 comments
Open

Filter using Class Status when generating OWL #202

AchillesDougalis opened this issue May 16, 2024 · 3 comments
Labels
type: feature request something requested to be implemented in a future release
Milestone

Comments

@AchillesDougalis
Copy link

Each Class in an Enterprise Architect file has a certain status. We need a filtering mechanism in model2owl that will be able to:

  • Include elements with a certain status from the output files .
    AND/OR
  • Exclude elements with a certain status from the output files .
    2024-05-16_11-35
@AchillesDougalis AchillesDougalis added the type: feature request something requested to be implemented in a future release label May 16, 2024
@cristianvasquez
Copy link

cristianvasquez commented Sep 25, 2024

I duplicated this one

The UML modelling process is iterative, often involving configurations and entities still under review or analysis.

  • Draft status information is extracted from entities' metadata within the XMI file.
  • The configuration file specifies which statuses should be filtered.
  • When configured, elements marked as "Draft" are excluded from SHACL and/or OWL output.

Use case: Remove references to code lists that are not yet implemented

@rousso
Copy link
Contributor

rousso commented Oct 13, 2024

I duplicated this one

The UML modelling process is iterative, often involving configurations and entities still under review or analysis.

  • Draft status information is extracted from entities' metadata within the XMI file.
  • The configuration file specifies which statuses should be filtered.
  • When configured, elements marked as "Draft" are excluded from SHACL and/or OWL output.

Use case: Remove references to code lists that are not yet implemented

@cristianvasquez What do you mean duplicated? Is there another (duplicate) ticket? Please make sure there is only one ticket that clearly states what is to be done and that it is assigned to the proper project and milestone.

@rousso rousso assigned cristianvasquez and unassigned Dragos0000 Oct 13, 2024
@cristianvasquez
Copy link

cristianvasquez commented Oct 14, 2024

@rousso there was another ticket that I closed to group it with this one.
I crossed the duplicated part to avoid confusion

@cristianvasquez cristianvasquez removed their assignment Oct 14, 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

4 participants