Closed kityansiu closed 1 year ago
Easiest way to test:
The issue is resolved with commit: https://github.com/ge-high-assurance/RITE/pull/122/commits/e78b2f06cc7f2fcdc8c6f7585bb3682cefc2b986
The commit message mentions other things
I have highlighted specific lines that make the fix possible, I pass in a list of model graphs from yaml instead of single model graph:
When right clicking on manifest.yaml and doing "Manifest Import", the ingestion goes to the default graphs specified in Window > Preferences > RACK instead of following what's in either model.yaml or import.yaml when they're specified. Here's the desired behavior demonstrated via RACK cli.
In MBSE-Ontology/OwlModels/model.yaml, I have the following :
And in MBSE-Ontology/manifest.yaml, I have the following:
When I run
rack manifest import manifest.yaml
it correctly ingests the model into the model-graph http://rack001/mbsemodel.Here's another example. In ADEPT/InstanceData/import.yaml, I have the following:
And in ADEPT/manifest.yaml, I have the following:
When I run
rack manifest import manifest.yaml
it correctly ingests the data into the data-graph http://rack001/adeptdata while correctly referencing both model-graphs.Note: The top-level "footprint" is only used to make sure the lower ones don't violate it. It isn't actually used. So, the best practice is to specify the model-graphs and data-graph in both the import.yaml (for data) and data.yaml (for model). Otherwise, the default graphs (http://rack001/model and http://rack001/data) can be used.