Brian Ruf
Brian Ruf
Made good progress on the collection of issues. This one will be addressed in sprint 68.
A few versions back, NIST moved away from publishing the JSON schemas in the repo and only making them available as download assets. Unfortunately this prevents us from linking to...
After review with @mpemy we have learned that the published NIST OSCAL JSON schema definitions continue to be incompatible as references for the OpenAPI definition as-is. **We will continue using...
Problem: Representation of objectives changed between 800-53 Rev 4 and 800-53 Rev 5 breaking parsers
There is a ton of information in this issue. Candidly, I haven't read all of it in detail, so apologies if this is duplicative. When addressing this issue, please consider...
@kylelaker Can you revise this ticket to reflect an client for the Transaction API instead of the REST API? Or close it an open a new issue for that purpose?
Must specify React component property types before we can size or work this.
@kylelaker do we have an issue for specifying React component property types that we can cite in the comment above?
Work in connection with #775 and try to address through application of the global styles.
Size and assign after #756
There are both recognized and unrecognized classes. Recognized classes are managed in an enumerated list with both human-friendly and OSCAL-friendly values.