Skip to content

Clarify relationship with OSCAL #74

@ralphbean

Description

@ralphbean

I've been diving around docs today learning about OSCAL, gemara, and baseline - and one thing isn't clear to me: What's the relationship between OSCAL and gemara? Why create gemara when OSCAL has been around for years?

My hunch is that it's simply about simplicity. OSCAL is complicated. gemara is attractive because its easier to work with and at the end of the day you can translate your gemara files to OSCAL for export if a consumer needs that.

  • Is that hunch correct?
  • If it is, is it worthwhile clarifying that in the docs somehow?

A separate, larger topic, I know that the baseline files (expressed in gemara layer 2) can be exported as an OSCAL catalog using tools in the baseline repo. Does there exist a well-defined process for mapping between each of the gemara layers and each of the OSCAL models generally? (Do the project maintainers intend for such a thing to be possible even if its not yet well-defined at this time?)

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions