Started comms guidance; vector string notation rewrite#64
Merged
j--- merged 1 commit intoCERTCC:mainfrom Nov 17, 2020
Merged
Conversation
zmanion
approved these changes
Nov 17, 2020
4 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 should fix #25. I've basically written the abbreviated format (that is, vector string) from scratch, since what SSVCv1 had in the "Pilot results" subsection in Section 5 was not particularly descriptive.
There are other issues associated with #24 that this commit creates a space to resolve. Those are tagged in the text, namely #26 and #29.
In the process of working on this, it also raised the issue of what sort of full format we may want to specify for communicating results. I'll create a new issue for that.