-
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
Name missing from property of select-objective-by-id #844
Labels
Comments
david-waltermire
assigned david-waltermire and wendellpiez and unassigned david-waltermire
Mar 11, 2021
8 tasks
wendellpiez
added a commit
to wendellpiez/metaschema
that referenced
this issue
Mar 16, 2021
Merged
4 tasks
david-waltermire
pushed a commit
to usnistgov/metaschema
that referenced
this issue
Mar 16, 2021
david-waltermire
added a commit
to david-waltermire/OSCAL
that referenced
this issue
Mar 16, 2021
8 tasks
david-waltermire
pushed a commit
that referenced
this issue
Mar 16, 2021
nikitawootten-nist
pushed a commit
to nikitawootten-nist/metaschema-xslt
that referenced
this issue
Jul 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The name is missing from the only property of select-objective-by-id. This manifests in two JSON schemas.
Assessment Plan Model: JSON Schema at line 1570 https://github.com/usnistgov/OSCAL/blob/master/json/schema/oscal_assessment-plan_schema.json#L1570
Assessment Results Model: JSON Schema at line 1604 https://github.com/usnistgov/OSCAL/blob/master/json/schema/oscal_assessment-results_schema.json#L1604
Also appears in the OSCAL web-based documentation. For example:
https://pages.nist.gov/OSCAL/documentation/schema/assessment-layer/assessment-plan/json-schema/#global_select-objective-by-id_h2
Who is the bug affecting?
All users relying on the schemas and documentation.
What is affected by this bug?
Appears to impact all schema files and web documentation generated based on the model.
For me, this breaks by dynamic generation of OSCAL class files.
When does this occur?
When generating schema files and web documentation.
How do we replicate the issue?
See links provided above.
Expected behavior (i.e. solution)
The property in question should have a name.
Other Comments
{Add any other context about the problem here.}
The text was updated successfully, but these errors were encountered: