Skip to content

Conversation

@aj-stein-gsa
Copy link
Contributor

@aj-stein-gsa aj-stein-gsa commented Sep 20, 2024

Committer Notes

Closes #40.

All Submissions:

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

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 updated all website and readme documentation affected by the changes you made?
  • Have you written new tests for your core changes, as applicable?
  • Have you included examples of how to use your new feature(s)?

@aj-stein-gsa aj-stein-gsa self-assigned this Sep 20, 2024
@aj-stein-gsa aj-stein-gsa changed the base branch from main to develop September 20, 2024 21:32
@RS-Credentive
Copy link

Okay, this clarifies my confusion regarding the definition of "has-oscal-namespace" and profile resolution. These are OSCAL specific metaschema extensions. As an author of metaschema tooling, I would like to see a supported mechanism for defining custom metapath functions that can be automatically processed. I will open a separate issue.

@david-waltermire david-waltermire force-pushed the 40-document-where-to-find-oscal-specific-custom-metaschema-functions-not-in-metaschema-java branch from 46a9c5b to 1a5a4d6 Compare October 3, 2024 03:43
@david-waltermire david-waltermire merged commit 1200e43 into metaschema-framework:develop Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document where to find OSCAL-specific custom Metaschema functions not in metaschema-java

3 participants