Repository navigation
Conversation
State which artifacts the SDK converts to OSCAL today and link the tracking issue for the rest. Replace "self-contained" with what it meant: OSCAL documents carry derived values alongside authored intent. Add a comparison row on where each format is adapted, content or structure. Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com> Assisted-by: Claude (model: claude-opus-5-5)
jmeridth
approved these changes
Oct 13, 2026
jmeridth
left a comment
jmeridth
left a comment
Member
There was a problem hiding this comment.
🤖 (summary) Approving. Nice tightening of the OSCAL claims. One non-blocking note: the SDK also converts Evaluation Logs, and the go-gemara#29 body is out of date in the same way.
| ### How do I get from Gemara to OSCAL? | ||
|
|
||
| The SDK maps Gemara artifacts to their OSCAL equivalents and handles OSCAL-specific requirements like UUID generation. Your source YAML stays lean; the SDK produces the OSCAL output. | ||
| The SDK converts Control Catalogs and Guidance Catalogs to their OSCAL equivalents and handles OSCAL-specific requirements like UUID generation. Your source YAML stays lean; the SDK produces the OSCAL output. |
Member
There was a problem hiding this comment.
🤖 (low, non-blocking) The SDK also converts Evaluation Logs to OSCAL Assessment Results (EvaluationLog(log).ToOSCALAssessmentResults(), shipped in v0.11.0), so this undersells it a bit. The go-gemara#29 body only lists the two catalogs, which might be where this came from. Worth adding?
Suggested change
| The SDK converts Control Catalogs and Guidance Catalogs to their OSCAL equivalents and handles OSCAL-specific requirements like UUID generation. Your source YAML stays lean; the SDK produces the OSCAL output. | |
| The SDK converts Control Catalogs and Guidance Catalogs to their OSCAL equivalents, and Evaluation Logs to OSCAL Assessment Results. It handles OSCAL-specific requirements like UUID generation. Your source YAML stays lean; the SDK produces the OSCAL output. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR refines the OSCAL section of the FAQ by stating which artifacts the SDK converts to OSCAL today and link the tracking issue for the rest. Replace "self-contained" with what it meant: OSCAL documents carry derived values alongside authored intent.