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

Describe how UML package dependencies are handled #146

Open
rob-metalinkage opened this issue Apr 19, 2023 · 0 comments
Open

Describe how UML package dependencies are handled #146

rob-metalinkage opened this issue Apr 19, 2023 · 0 comments
Assignees
Labels
type: implementation question something needs clarified, refined or decided before the implementation can continue

Comments

@rob-metalinkage
Copy link

XMI is package centric, so XMI reuse must mirror UML package dependencies.

In an ecosystem with many UML packages (e.g. INSPIRE) dependency management is a real problem, since UML has internal UUIDs but no way is provided for resolving these (or often even exposing them) to locate dependencies.

There may be a relationship between this and the merge-xmi but its not clear.

Also, if the tool doesnt require dependencies, because it assumes that it will owl:import each depdendent ontology and this is sufficient (?) this should also be explicit.

@costezki costezki self-assigned this Jul 25, 2023
@costezki costezki added the type: implementation question something needs clarified, refined or decided before the implementation can continue label Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: implementation question something needs clarified, refined or decided before the implementation can continue
Projects
None yet
Development

No branches or pull requests

2 participants