Partial Component Compositions

[meganwolf0]

Is your feature request related to a problem? Please describe.

Refactor the component-definition composition functionality to only compose components but maintain validations and relative links.

Some of this work might relate to/help uncover the solutions for #716 and #717

Describe the solution you'd like

• Given component defn with imported components and validation links
• When composition is executed on said component defn with optionality to only compose the components
• Then validations are not incorporated in the back-matter; relative path links are handled

Describe alternatives you've considered

Add all validations to the back-matter in component defn and then just add those to the back-matter in the SSP

Additional context

To enable the SSP to use the validations, while they are still in a disaggregated state (i.e., not in the back-matter), the component-definition needs to be passed to the SSP generate processes with those links intact and properly remapped relative to the SSP output file path.

Expected Deliverable

• Updated optionality on composer
• Updated documentation/intent on tools compose, intended use cases, scenarios (coupled to Compose Documentation - Purpose #715). Where does decompose fit? (Decompose OSCAL and Validations #397)

[meganwolf0]

Closed via #905