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.
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.