-
Notifications
You must be signed in to change notification settings - Fork 187
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 identifiers to each inline constraint in Metaschema definitions of NIST OSCAL models #2088
Comments
This is something we would like to see as well. We plan to use these IDs in customer facing reports, along with other information from the oscal-cli validation results, to help customers identify and remediate issues in their data/OSCAL. Currently the "id" changes for NIST constraints on each run, which makes it difficult to track whether a specific error has been remediated or not on subsequent oscal-cli validations. |
Thank you @aj-stein-gsa and @Telos-sa . I think the request is reasonable and we can look at scheduling it early next year, after wrapping up some ongoing work. |
I will send a PR for consideration then later today or Sunday. |
User Story
As a developer who makes use of OSCAL models and embedded data modeling requirements defined by assembly, field, and flag constraints, I would like every constraint (
allowed-values
;expect
;matches
;index
;index-has-key
;has-cardinality
; etc.) to have a defined@id
field. Per the Metaschema specification, this field is optional. AGoals
Dependencies
No response
Acceptance Criteria
(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)
Revisions
No response
The text was updated successfully, but these errors were encountered: