You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content on the OSCAL site doesn't match the model. The content on https://pages.nist.gov/OSCAL/resources/concepts/layer/assessment/assessment-plan/ states that the assessment plan should contain a field for assessment actions, but I couldn't find it in the JSON/XML model, nor any references to it in the metaschema. Unsure if it's a bug or if it just hasn't been released yet. Either the model or content should be updated to improve accuracy.
Thank you for reporting the bug - It is the diagram that needs to be updated. We are in the process of reviewing all pages for accuracy, consistency, usability and accessibility.
Under the assessment-plan/assessment -assets there are tasks that documents scheduled events or milestone, which may be associated with a series of assessment actions. This is a more generic way of allowing the assessment planner to define tasks of type milestoneor oftypeaction`.
Describe the bug
The content on the OSCAL site doesn't match the model. The content on https://pages.nist.gov/OSCAL/resources/concepts/layer/assessment/assessment-plan/ states that the assessment plan should contain a field for assessment actions, but I couldn't find it in the JSON/XML model, nor any references to it in the metaschema. Unsure if it's a bug or if it just hasn't been released yet. Either the model or content should be updated to improve accuracy.
Who is the bug affecting
Content consumers of the OSCAL site.
What is affected by this bug
OSCAL Content, Documentation, Metaschema, Modeling, Website
How do we replicate this issue
Visit https://pages.nist.gov/OSCAL/resources/concepts/layer/assessment/assessment-plan/ and compare it to the JSON outline in https://pages.nist.gov/OSCAL-Reference/models/v1.1.2/assessment-plan/json-outline/
Expected behavior (i.e. solution)
The documentation should match the model.
Other comments
No response
Revisions
No response
The text was updated successfully, but these errors were encountered: