Align profile resolution specification with latest processing model defined in the profile metaschema.

[david-waltermire]

User Story

As an OSCAL Profile author or consumer, I need to understand the logic for resolving identifier reassignments during profile resolution. The profile resolution specification needs to provide a clear processing model based on what is currently modeled in the profile metaschema.

Goals

• [ ] document processing requirements based on the current profile metaschema reassignment implementation.

Dependencies

None.

Acceptance Criteria

• [ ] All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
• [ ] A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• [ ] The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

[aj-stein-nist]

As Dave has rolled of the project, I will re-assign this to myself in the interim until I can update it.

[aj-stein-nist]

Not completed last sprint and not in scope for Sprint 63, moving to the backlog.

[aj-stein-nist]

This seems important but needs more definition before it is ready with a Todo status to work in sprint. Will set to Needs Refinement.