Data Type Check in Metaschema Definitions

[aj-stein-nist]

User Story

As a Metaschema developer, in order to make sure I make use of proper datatypes when adding and modifying Metaschema-based models, I want validation to warn and recommend corrections to present fixes to me.

The current implemented approach requires running produce-datatype-validation-functions.xsl to update oscal-datatypes-check.xsl. This should be refactored to dynamically build the necessary data from the base schemas as part of the oscal-datatypes-check.xsl. This avoids needing to manually run produce-datatype-validation-functions.xsl.

Goals

• [ ] Update Schematron checks to enforce correct usage of valid Metaschema datatypes dynamically (@wendellpiez)
• [ ] Add QuickFix (SQF) checks to recommend possible fixes for incorrect datatype usage (verify implementation) (@wendellpiez)
• [ ] Automate enforcement in OSCAL CI/CD pipelines in GitHub Actions (@aj-stein-nist)

Dependencies

N/A

Acceptance Criteria

• [ ] All Metaschema website and readme documentation affected by the changes in this issue have been updated. Changes to the Metaschema 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]

Per discussion with team reorganization, I will move this Metaschema issue off the NIST OSCAL workboard.