Describe the bug

I noticed that the references to the schematron files and metaschema.xsd pointed to the old metaschema submodule instead of the new metaschema-xslt. This resulted in validations passing when there were possible issues in metaschema documents.

Who is the bug affecting

All developers, and ultimately the schemas and converters in OSCAL.

What is affected by this bug

Modeling, Tooling & API

How do we replicate this issue

See the following references for an example:

• OSCAL/src/metaschema/oscal_component_metaschema.xml

  Line 2 in ef4df06

  <?xml-model href="../../build/metaschema/toolchains/xslt-M4/validate/metaschema-composition-check.sch" type="application/xml" schematypens="http://purl.oclc.org/dsdl/schematron"?>

• OSCAL/src/metaschema/oscal_component_metaschema.xml

  Line 15 in ef4df06

  xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0" xsi:schemaLocation="http://csrc.nist.gov/ns/oscal/metaschema/1.0 ../../build/metaschema/toolchains/xslt-M4/validate/metaschema.xsd">

Expected behavior (i.e. solution)

Validations should fail when problems are encountered in documents.

Other comments

I already have a PR ready to push. Will push shortly for review.

Revisions

No response