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

Review Top-Level Model Indices and Supporting Constraints #1431

Open
8 tasks
aj-stein-nist opened this issue Aug 26, 2022 · 1 comment
Open
8 tasks

Review Top-Level Model Indices and Supporting Constraints #1431

aj-stein-nist opened this issue Aug 26, 2022 · 1 comment
Labels
Aged A label for issues older than 2023-01-01 enhancement Scope: Modeling Issues targeted at development of OSCAL formats User Story

Comments

@aj-stein-nist
Copy link
Contributor

aj-stein-nist commented Aug 26, 2022

User Story

As a NIST OSCAL developer, in order to be confident of a thorough model review to tighten up docs and supporting constraint and index definitions for programmatic use in Metaschema-aware libraries, I would like an updated review of models for missing top-level indices and supporting constraints.

Goals

  • Review and add missing indices that add useful or necessary indices for all top-level OSCAL top-level models (catalog, profile, SSP, AP, AR, POA&M)
  • Review and add supporting constraints that logically flow from just those index updates as applicable with discussion of team during review

Original rationale and goals can be found in the comment, leading to the creation of this issue.

Dependencies

Acceptance Criteria

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

This is very open-ended and needs to broken down and organized to delegate to developers to work. Per discussion with Arminta, marking this as needs refinement.

@Compton-US Compton-US added the Aged A label for issues older than 2023-01-01 label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aged A label for issues older than 2023-01-01 enhancement Scope: Modeling Issues targeted at development of OSCAL formats User Story
Projects
Status: Needs Refinement
Development

No branches or pull requests

3 participants