All Schema v2.02 updates. Simplifying the code #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sei-vsarvepalli
added
bug
This was referenced Oct 5, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This tries to address a number of Issues that we have been addressing
Issue #149 =>
Provide SSVC export in PDF format with a table and information
Export JSON to include full definitions of all the various options.
Import CVE template for ssvc-calc to be available.
Display SSVC vector format in the screen right before Export
Provide permalink for people to share for the current decision for processing.
Issue #150
ISO 8601 a specific version of the format that excludes "milliseconds" and uses the Z to represent UTC time
Issue #151
Simplify the decision_points schema to be flat (only "complex" and "simple" no need for children identify themselves as "child" and to identify their parents.
Complex decisions can include other "complex" decisions. It will be recursive as the schema itself does not really care about. These logic should be put into the code that analyzes the tree JSON.