Skip to content

Conversation

@sei-renae
Copy link
Contributor

@sei-renae sei-renae commented Feb 17, 2025

@ahouseholder ahouseholder self-assigned this Feb 17, 2025
@ahouseholder ahouseholder changed the title Resolve issue 584 Fix json schema example Feb 17, 2025
Copy link
Contributor

@ahouseholder ahouseholder Feb 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't seem right. Why would Exploitation have a key of "V"? "V" used to be Virulence, which was replaced by "Automatable" ("A"). So this change to "Exploitation" seems out of place.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for catching that I went to L34 instead of L54. Update incoming.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thes scheme example should go in an archive folder, we no longer support this format
data/schema_examples/Computed-CVE-2014-0751-Coordinator-with-tree.json

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spawned @sei-vsarvepalli 's comment into a new issue #687 so we don't have to hold this PR for merging

Copy link
Contributor

@ahouseholder ahouseholder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the one note about exploitation, virulence, and automatable to be fixed.

Also, we should plan to merge this one after #683 because both PRs touch some of the same files, and it will be easier to resolve conflicts if we merge #683 before #684 (this PR).

Copy link
Contributor

@ahouseholder ahouseholder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Will merge shortly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spawned @sei-vsarvepalli 's comment into a new issue #687 so we don't have to hold this PR for merging

@ahouseholder ahouseholder merged commit 3008938 into CERTCC:main Feb 18, 2025
1 check passed
@sei-renae sei-renae deleted the 584 branch February 19, 2025 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

There might be a typo in the ssvc data example.

3 participants