More robust support for datatype checking in Metaschema Schematron

[wendellpiez]

User Story:

As indicated by #191, updates to the XSLT M4 Metaschema stack (behind PR #214) will support both old and new datatype names.

As a user, however, I want to know what the new names are and where to use them.

A metaschema Schematron could report warnings or errors (?) when encountering old names for datatypes; ideally it would permit reassigning the value with the corresponding new type (Schematron Quickfix?)

Goals:

A Schematron test to flag, in a Metaschema or metaschema module

• unrecognized datatypes
• old datatype names (report with their new names)
• optionally (depending on feasibility/maintainability), Quickfix for correction
• optionally, with unit test/s showing correct handling of datatype assignments (tbd)

Also: review state of XSD and make followup Issue as appropriate. Are old values XSD-valid?

Dependencies:

None known. This work is timely as OSCAL 1.0.4 schemas are migrated forward.

Acceptance Criteria

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

[wendellpiez]

Better handling is now implemented in the branch behind PR #214.