-
Notifications
You must be signed in to change notification settings - Fork 46
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
assessedElement to target SoftwareArtifact instead of Element #911
Comments
I think the target should be Since in the future we might have security info for other, non-software artifacts. |
Note - that if we make this more restrictive, it will be a breaking change, so this will have to be in either 3.0.1 or 4.0. |
Having it as Element is going to provide more flexibility for future profiles. Ok to discuss further but at this point it's going to 4.0 related change. For instance, we could have an assessedElement on a Role or Relationship type which are not artifacts. |
Removing the milestone until this is discussed. |
From /Security/assessedElement:
"Specifies subpackages, files or snippets ..."
If it's limited to only packages, files and snippets then why its target is Element and not SoftwareArtifact?
Package, File and Snippet are the only subclasses of SoftwareArtifact.
The text was updated successfully, but these errors were encountered: