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.

Sign up for GitHub

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

Jump to bottom

Should the different prefixes of the Ontology be kept or not? #728

Open
AchillesDougalis opened this issue Dec 11, 2024 · 0 comments
Open

Should the different prefixes of the Ontology be kept or not? #728

AchillesDougalis opened this issue Dec 11, 2024 · 0 comments
Assignees
@victoriobentivogli
Labels
act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
Milestone
miscellaneous

Comments

@AchillesDougalis
Copy link
Contributor

AchillesDougalis commented Dec 11, 2024 •
edited
Loading

To investigate the advantages of the different epo prefixes that exist for each module, and if there is value in keeping them, rather than only having the epo: prefix.

The reasoning behind the modularization of the Ontology can be found here.

There is also a guideline on modularization on SEMIC Style guide.

related to #727
@AchillesDougalis AchillesDougalis added type: feature request something requested to be implemented in a future release act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature labels Dec 11, 2024
@AchillesDougalis AchillesDougalis added this to the miscellaneous milestone Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@victoriobentivogli victoriobentivogli

Labels
act: for internal discussion it needs to be discussed within the team module: none no module in particular because the issue is of technical or documentation nature type: feature request something requested to be implemented in a future release
Projects
None yet
Milestone
miscellaneous
Development

No branches or pull requests
2 participants
@victoriobentivogli @AchillesDougalis