Package package#Core is supposed to contain elements:
that are defined in core.rdf, but are included in some domain model tables to support domain model editor functions
that need to be available in every package, e.g., elements added as probes to debug construction patterns, threat paths, etc.
that are needed in many packages in different branches of the package dependency hierarchy
All elements in the first category and some from the second even have URIs that start 'core#'.
The weird thing is that (based on some automated dependency analysis), the asserted package dependency hierarchy PackageInterdependencies.csv says that package#Network depends on package#Core, but package#Physical and package#Users do not. This means package#Core is not actually at the bottom of the package dependency hierarchy.
This is clearly nuts, given that debugging probes may be needed in construction patterns or threats in any other package. They haven't been needed in package#Physical and package#Users because those are old and stable parts of the domain model, but that doesn't mean it could never happen.
mike1813
commented
1 week ago
Package package#Core is supposed to contain elements:
All elements in the first category and some from the second even have URIs that start 'core#'.
The weird thing is that (based on some automated dependency analysis), the asserted package dependency hierarchy PackageInterdependencies.csv says that package#Network depends on package#Core, but package#Physical and package#Users do not. This means package#Core is not actually at the bottom of the package dependency hierarchy.
This is clearly nuts, given that debugging probes may be needed in construction patterns or threats in any other package. They haven't been needed in package#Physical and package#Users because those are old and stable parts of the domain model, but that doesn't mean it could never happen.
This should be fixed.