Skip to content

Commit

Permalink
[skip ci] Add missing link to oscal-content per review feedback.
Browse files Browse the repository at this point in the history
Thanks for catching this, @nikitawootten-nist.
  • Loading branch information
aj-stein-nist committed Nov 9, 2023
1 parent 042cb3e commit 3ba2c34
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion decisions/0008-oscal-content-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Since 2016, the OSCAL project has iterated on methods and locations for managing

### Data Management and Governance Challenges

As enhancements and bug fixes for OSCAL increased, separate of the content, in between official upstream releases of SP 800-53A and SP 800-53B, staff and community members [identified bugs and enhancements to the OSCAL representations](). In most cases, these work items would not or did not diverge from the content in the official publication version. These data quality and OSCAL-specific enhancements would or did improve the ability of technical staff using the OSCAL representation to create or improve catalog and profile automation. There has been no clear guidance on how to accept these changes, publish them, and how to identify their versions upon release. These governance questions led to an accumulation of work items that delayed publication (at this time, read: merged into the `main` branch).
As enhancements and bug fixes for OSCAL increased, separate of the content, in between official upstream releases of SP 800-53A and SP 800-53B, staff and community members [identified bugs and enhancements to the OSCAL representations](https://github.com/usnistgov/oscal-content/issues). In most cases, these work items would not or did not diverge from the content in the official publication version. These data quality and OSCAL-specific enhancements would or did improve the ability of technical staff using the OSCAL representation to create or improve catalog and profile automation. There has been no clear guidance on how to accept these changes, publish them, and how to identify their versions upon release. These governance questions led to an accumulation of work items that delayed publication (at this time, read: merged into the `main` branch).

### OSCAL Dependency Upgrades, Integration, and Regression Test Challenges

Expand Down

0 comments on commit 3ba2c34

Please sign in to comment.