Merging Control Mapping Model into develop branch#2174
Conversation
This reverts commit defe67e.
… available in the imports.
…umentation to reflect override behavior.
…r values in "type"
…lements in "coverage" definition.
…uble definition of .
|
IMPORTANT NOTE: This PR is the result of the OSCAL Foundation's request to test the Controls Mapping Model at the OSCAL PlugFest on Dec 15, 2025. The PR submitted in preparation of such minor release. Due to time constraints, the PR is not addressing the Issue #2166 is one of the OF's work items for near future and requires a review of the specification, the resolver's implementation and of the test suit which exercises positive and negative unit tests. The profile resolver tests, if ran, will return errors that are not breaking the build , when testing For interested parties, returned errors are: |
Committer Notes
Merging Control Mapping Model into
developbranch in preparation of the OSCAL minor release 1.2.0All Submissions:
By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.
(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)
Changes to Core Features: