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.

Sign up for GitHub

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

Jump to bottom

Fix typo: Asbtract -> Abstract #888

Merged
merged 1 commit into from
Sep 26, 2024
Merged

Fix typo: Asbtract -> Abstract #888

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions model/Security/Classes/VexVulnAssessmentRelationship.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ SPDX-License-Identifier: Community-Spec-1.0

## Summary

Asbtract ancestor class for all VEX relationships
Abstract ancestor class for all VEX relationships

## Description

Expand All @@ -17,10 +17,10 @@ When linking elements using a VexVulnAssessmentRelationship, the following
requirements must be observed:

- The from: end must be a /Security/Vulnerability classed element
- The to: end must point to elements representing the VEX _products_.
- The to: end must point to elements representing the VEX *products*.

To specify a different element where the vulnerability was detected, the VEX
relationship can optionally specify _subcomponents_ using the assessedElement
relationship can optionally specify *subcomponents* using the assessedElement
property.

VEX inherits information from the document level down to its statements. When a
Expand Down