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

Update web site coverage of OSCAL scope. #389

Closed
wendellpiez opened this issue May 30, 2019 · 3 comments
Closed

Update web site coverage of OSCAL scope. #389

wendellpiez opened this issue May 30, 2019 · 3 comments
Assignees
Labels
Scope: Website Issues targeted at the OSCAL project website. User Story

Comments

@wendellpiez
Copy link
Contributor

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.

@wendellpiez wendellpiez self-assigned this May 30, 2019
@wendellpiez wendellpiez added this to the OSCAL 1.0 M1 milestone May 30, 2019
@wendellpiez
Copy link
Contributor Author

For some reason the "Relations" page also has an empty side nav.

@david-waltermire david-waltermire added Scope: Website Issues targeted at the OSCAL project website. User Story labels May 30, 2019
wendellpiez added a commit to wendellpiez/OSCAL that referenced this issue Jul 25, 2019
@david-waltermire
Copy link
Contributor

The content for this is in the site under /OSCAL/docs/relations/. The team should review these changes.

david-waltermire pushed a commit to david-waltermire/OSCAL that referenced this issue Aug 16, 2019
david-waltermire pushed a commit to david-waltermire/OSCAL that referenced this issue Aug 16, 2019
@david-waltermire
Copy link
Contributor

This has been completed in PR #464.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Website Issues targeted at the OSCAL project website. User Story
Projects
None yet
Development

No branches or pull requests

2 participants