Skip to content

Merging Control Mapping Model into develop branch#2174

Merged
iMichaela merged 22 commits intodevelopfrom
prototype2-mapping-model
Dec 10, 2025
Merged

Merging Control Mapping Model into develop branch#2174
iMichaela merged 22 commits intodevelopfrom
prototype2-mapping-model

Conversation

@iMichaela
Copy link
Contributor

@iMichaela iMichaela commented Dec 9, 2025

Committer Notes

Merging Control Mapping Model into develop branch in preparation of the OSCAL minor release 1.2.0

All 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:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you included examples of how to use your new feature(s)?
  • Have you updated the OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the OSCAL-Pages and OSCAL_Reference repositories.

aj-stein-nist and others added 22 commits December 9, 2025 11:15
@iMichaela iMichaela requested a review from a team as a code owner December 9, 2025 16:20
@iMichaela iMichaela requested review from a team and removed request for a team December 9, 2025 16:21
@iMichaela
Copy link
Contributor Author

iMichaela commented Dec 9, 2025

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 merge profile resolution issue #2166 which will be addressed after the event.

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 merge-combined functionality launched by usnistgov/OSCAL/src/utils/resolver-pipeline/testing/3_merged/merge.xspec.

For interested parties, returned errors are:

Tests for match=@opr:id template
ERROR in x:context (under 'Tests for match=@opr:id template'): Context is an empty sequence.
Error on line 12871 column 42 of merge-compiled.xsl:
  XTMM9000  Processing terminated by xsl:message at line 12871 in merge-compiled.xsl at template scenario9 on line 12810 column 83 of merge-compiled.xsl:  invoked by xsl:call-template at file: usnistgov/OSCAL/src/utils/resolver-pipeline/./testing/xspec/merge-compiled.xsl#73 at template main on line 30 column 41 of merge-compiled.xsl:  invoked by xsl:for-each at file: usnistgov/OSCAL/src/utils/resolver-pipeline/./testing/xspec/merge-compiled.xsl#46
at template main on line 30 column 41 of merge-compiled.xsl:
Processing terminated by xsl:message at line 12871 in merge-compiled.xsl

@rsherwood-nist rsherwood-nist self-assigned this Dec 10, 2025
Copy link

@rsherwood-nist rsherwood-nist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@iMichaela iMichaela merged commit 86e384f into develop Dec 10, 2025
1 check passed
@iMichaela iMichaela deleted the prototype2-mapping-model branch December 14, 2025 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants