-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add Classification support #19
base: main
Are you sure you want to change the base?
Conversation
Documentation is currently missing |
Can this (and the other PR) be redone so that there are actual clean diffs (i.e. no changes in whitespace and other formatting that makes the changes very hard to review and also impossible to merge as is)? It also seems to me, but again hard to check with all the superfluous changes, that this touches more places than it technically needs to. Other than that this PR is misnamed: It does not add SRMD support at all, it adds classifications. SRMD is a stand-alone file format, not the SSP Traceability classifications. I think that SSP should first add support for specifying per-element (and other entities, like parameter sets, ...) generic meta-data support, which could then be used to point to / embed SRMD files and other format meta-data. That SSP might also want to add classifications for all modeling elements is I think another issue. |
Any ideas what formatting settings to use? I use XML Spy. |
Ideally tell XML Spy to not touch anything that you are not changing, and to use 4 spaces no tabs indentation. Not sure how to tell XML Spy this, I tend never to use it. It is usually easier to work with editors in textual mode, as for any other language, as this allows clearer control of the stuff changed... |
I think that can easily be incorporated in the current proposal. |
Adds support fro srmd classifications via an GElementCommont group that wraps annotations and classifications.
Therefore srmd classifications can be used with all entities that are annotatable.