This is linked to Spyderisk system-modeller issue #103.
The issue is that the structure of a domain model deployment bundle as required by system-modeller has been fixed. It should now consist of a zipfile, containing:
a folder called icons containing icon image files,
an NQ file containing the RDF graph, named <any>.nq,
a JSON file specifying which icon to display for each assertible asset class, named icon-mapping.json.
These should all be at the top level, i.e., the zipfile is not a zipped folder containing the above.
The CI pipeline here has also been fixed by @scp93ch, but only on branch '6a'.
This fix should be implemented in the 'master' branch, because that's the starting point to be copied by anyone who wants to create a completely new domain model. It should be possible for such a person to checkout the master branch, copy the source files without the other branches or git repository state to get a clean but 'empty' working set, then create a new detached git repository from that, which they may or may not wish to share through GitHub.
Action: make these changes available also in branch 'master'.
This is linked to Spyderisk system-modeller issue #103.
The issue is that the structure of a domain model deployment bundle as required by system-modeller has been fixed. It should now consist of a zipfile, containing:
icons
containing icon image files,<any>.nq
,icon-mapping.json
.These should all be at the top level, i.e., the zipfile is not a zipped folder containing the above.
The CI pipeline here has also been fixed by @scp93ch, but only on branch '6a'.
This fix should be implemented in the 'master' branch, because that's the starting point to be copied by anyone who wants to create a completely new domain model. It should be possible for such a person to checkout the master branch, copy the source files without the other branches or git repository state to get a clean but 'empty' working set, then create a new detached git repository from that, which they may or may not wish to share through GitHub.
Action: make these changes available also in branch 'master'.