Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data Type Check in Metaschema Definitions #32

Open
6 tasks
Tracked by #33
aj-stein-nist opened this issue Dec 6, 2022 · 1 comment
Open
6 tasks
Tracked by #33

Data Type Check in Metaschema Definitions #32

aj-stein-nist opened this issue Dec 6, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@aj-stein-nist
Copy link
Contributor

aj-stein-nist commented Dec 6, 2022

User Story

As a Metaschema developer, in order to make sure I make use of proper datatypes when adding and modifying Metaschema-based models, I want validation to warn and recommend corrections to present fixes to me.

The current implemented approach requires running produce-datatype-validation-functions.xsl to update oscal-datatypes-check.xsl. This should be refactored to dynamically build the necessary data from the base schemas as part of the oscal-datatypes-check.xsl. This avoids needing to manually run produce-datatype-validation-functions.xsl.

Goals

  • Update Schematron checks to enforce correct usage of valid Metaschema datatypes dynamically (@wendellpiez)
  • Add QuickFix (SQF) checks to recommend possible fixes for incorrect datatype usage (verify implementation) (@wendellpiez)
  • Automate enforcement in OSCAL CI/CD pipelines in GitHub Actions (@aj-stein-nist)

Dependencies

N/A

Acceptance Criteria

  • All Metaschema website and readme documentation affected by the changes in this issue have been updated. Changes to the Metaschema 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.
@aj-stein-nist
Copy link
Contributor Author

Per discussion with team reorganization, I will move this Metaschema issue off the NIST OSCAL workboard.

@david-waltermire david-waltermire transferred this issue from usnistgov/metaschema Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants