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

Add NIST SP 800-53 in YAML format #262

Merged
merged 1 commit into from
Nov 9, 2018

Conversation

redhatrises
Copy link
Contributor

NIST SP 800-53 in yaml format which is part of #68 and #203

Copy link
Contributor

@iMichaela iMichaela left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the first draft of SP 800-53 rev4 catalog represented in YAML. The conversion was dome from JSON. The team is encouraged to provide additional feedback.

@iMichaela iMichaela merged commit 85c86f3 into usnistgov:master Nov 9, 2018
@wendellpiez
Copy link
Contributor

I like what I am seeing here. There are still a couple of important issues to be sorted through, mainly related to prose and arbitrarily-ordered content (including but not limited to mixed inline content).

How to approach this: I could work with @redhatrises trading examples and test cases, to explore possibilities. Or we could go straight to a larger group -- because similar issues are salient on the JSON side (where we are casting to markdown to address this) and also because a robust XML/YAML pathway (including tooling @david-waltermire-nist is contemplating) will depend on these decisions.

The acid test is a robust, lossless two-way conversion between XML OSCAL and YAML OSCAL and back again, analogous to what we are doing with the JSON (with the help of the metaschema).

cc @iMichaela @anweiss and @akarmel

@wendellpiez
Copy link
Contributor

@redhatrises also I'd love to see the conversion script. Python?

A detail to add is that we have been aided in XML-JSON conversion by XPath 3.1 functions that execute the syntactic mapping. Without anything similar on the YAML side, we need to develop this capability -- and this script appears to be a good start (even if it reads the JSON not the XML).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants