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

Add Constraint IDs/Names for All Constraints in Model #1430

Open
6 tasks
aj-stein-nist opened this issue Aug 26, 2022 · 3 comments
Open
6 tasks

Add Constraint IDs/Names for All Constraints in Model #1430

aj-stein-nist opened this issue Aug 26, 2022 · 3 comments
Labels
Aged A label for issues older than 2023-01-01 enhancement model-refactor Used to mark issues related to model refactoring for the Metaschema v4 transition. 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 effectively and efficiently manage the use of names and identifiers in OSCAL models (defined in the Metaschema), I want all constraints to be given unique identifier ID/names. In the best case scenario, I want some method to augment setting this up for all the constraints the first time so I do not have to do so manually.

Goals

  • Research approach/method to programmatically add them
  • Check in the update models with updated constraint IDs to manage all unique in models and globally

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 aj-stein-nist added enhancement User Story Scope: Modeling Issues targeted at development of OSCAL formats model-refactor Used to mark issues related to model refactoring for the Metaschema v4 transition. labels Aug 26, 2022
@aj-stein-nist
Copy link
Contributor Author

So Dave suggests this will be an epic and focus on research, experimentation, and method of this approach and rolling it out.

@aj-stein-nist
Copy link
Contributor Author

I am going to remove this from the sprint for now and add it to the backlog.

@aj-stein-nist aj-stein-nist removed this from the v1.1.0 milestone Jul 27, 2023
@aj-stein-nist
Copy link
Contributor Author

This issue needs to be refined or prune into a spike, and a placeholder for follow-on work.

@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 model-refactor Used to mark issues related to model refactoring for the Metaschema v4 transition. Scope: Modeling Issues targeted at development of OSCAL formats User Story
Projects
Status: Needs Refinement
Development

No branches or pull requests

3 participants