Hotfix/refactor duplicates

[wandmagic]

Committer Notes

naming conflicts in the metaschema cause errors in java model generation. this refactoring of models allows for validation use the metaschema validate-content command to correctly run

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?
• Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

[aj-stein-gsa]

This may not be need and is related to a bug in the behavior of metaschema-java not conforming to the Metaschema spec and processiong behavior for two independent inline assembly definitions still being independent despite the same identical local name. See metaschema-framework/metaschema-java#259 for more details.

[wandmagic]

This may not be need and is related to a bug in the behavior of metaschema-java not conforming to the Metaschema spec and processiong behavior for two independent inline assembly definitions still being independent despite the same identical local name. See metaschema-framework/metaschema-java#259 for more details.

it may not be needed but it will also improve type generation and json-schema quality downstream, by re-using two seperate duplicate definitions which define the same thing

[iMichaela]

These are unacceptable changes as proposed .

1. NIST does not accept schemas not developed by NIST (see https://raw.githubusercontent.com/metaschema-framework/metaschema/refs/heads/develop/schema/xml/metaschema.xsd">)
2. The extend of proposed changes is not justified by the implied hotfix for a pair of clashing constraints

[wandmagic]

These are unacceptable changes as proposed .

1. NIST does not accept schemas not developed by NIST (see https://raw.githubusercontent.com/metaschema-framework/metaschema/refs/heads/develop/schema/xml/metaschema.xsd">)
2. The extend of proposed changes is not justified by the implied hotfix for a pair of clashing constraints

rolled the schema change back, the schema change is not needed for the hotfix

[wandmagic]

Closing, this, we can fix these issues upstream in metaschema java