Skip to content
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

Open
ilans opened this issue Nov 13, 2024 · 4 comments
Open

assessedElement to target SoftwareArtifact instead of Element #911

ilans opened this issue Nov 13, 2024 · 4 comments
Labels
Profile:Security Security Profile and related matters

Comments

@ilans
Copy link
Collaborator

ilans commented Nov 13, 2024

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.

@bact bact added Profile:Security Security Profile and related matters RDF/OWL/SHACL RDF graph, schema, ontology, constraint labels Nov 13, 2024
@zvr zvr changed the title [SHACL] assessedElement to target SoftwareArtifact instead of Element assessedElement to target SoftwareArtifact instead of Element Nov 13, 2024
@zvr zvr removed the RDF/OWL/SHACL RDF graph, schema, ontology, constraint label Nov 13, 2024
@zvr zvr added this to the 3.0.1 milestone Nov 14, 2024
@zvr
Copy link
Member

zvr commented Nov 14, 2024

I think the target should be /Core/Artifact.

Since in the future we might have security info for other, non-software artifacts.

@goneall
Copy link
Member

goneall commented Nov 14, 2024

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.

@kestewart
Copy link
Contributor

kestewart commented Nov 14, 2024

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.

@kestewart
Copy link
Contributor

Removing the milestone until this is discussed.

@kestewart kestewart removed this from the 3.0.1 milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Profile:Security Security Profile and related matters
Projects
None yet
Development

No branches or pull requests

5 participants