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
As an OSCAL adopter, I need a clear understanding of what kinds of data OSCAL encoding is good for. In particular, I need to know that (at the lower levels) OSCAL is not intended for full text transcription of documents in general - only of the control portions of catalogs. So the catalog model (for example) is not intended to support (for example) all of NIST SP800-53.
Goals:
Clarification for ourselves and our users of our intended scope. Help finding others working in neighbor domains to help with problems we do not help with.
User Story:
As an OSCAL adopter, I need a clear understanding of what kinds of data OSCAL encoding is good for. In particular, I need to know that (at the lower levels) OSCAL is not intended for full text transcription of documents in general - only of the control portions of catalogs. So the catalog model (for example) is not intended to support (for example) all of NIST SP800-53.
Goals:
Clarification for ourselves and our users of our intended scope. Help finding others working in neighbor domains to help with problems we do not help with.
The page at https://pages.nist.gov/OSCAL/docs/relations/ requires revision, at least.
Dependencies:
While I can draft this copy I will need input from others to ensure it is correct.
Acceptance Criteria
At least the page mentioned has been revised.
The text was updated successfully, but these errors were encountered: