Provide a mechanism for defining schema specific metapath extensions

[RS-Credentive]

User Story

As a developer of metaschema tooling, I need a mechanism to identify metapath functions that are used in metaschema specifications.

Goals

When a metaschema specification such as OSCAL defines a metapath functions (e.g. "has-oscal-namespace"), metaschema tooling should be able to identify a pure metapath equivalent of the function. Currently, a tool which simply parses the metaschema xsd and a metaschema specification has no way to derive the pure metapath equivalent the metapath function.

Dependencies

No response

Acceptance Criteria

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

Revisions

No response

[david-waltermire]

This will require the ability to declare functions, which will require new syntax. Something like what exists in XSLT.

This is something that needs to be implemented in https://github.com/metaschema-framework/metaschema.