Support expanded qnames in Metapath

[david-waltermire]

User Story:

As a Metaschema {stakeholder}, I {provide a clear and concise description of what the problem is. Ex. I need to be able to do}

Goals:

• Metapath expanded qname handling
• Unit tests
  • Use of function namespace prefixes
  • Use of data type namespace prefixes

Dependencies:

{Describe any previous issues or related work that must be completed to start or complete this issue.}

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.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}

[david-waltermire]

Support for this was added in metaschema-framework/metaschema-java v1.0.0 back in August 2024.

[iMichaela]

Thank you for the pointer.
For the community members’ clear understanding, it is important to note that the metaschema-framework GH repository (and all its projects) is a repository that does not belong to NIST, nor is NIST endorsing or using the metaschema-framework projects and that the enhancements discussed herein were not proposed back to NIST as contributions.