David Waltermire

@guyzyl Expressing the choice semantic in JSON Schema is very challenging. You can use `oneOf` or `anyOf` to express the combination of properties that are allowed, but the combinations are...

@guyzyl True. But the tooling around JSON and XML Schema is insufficient as well for our needs. Tooling will catch up.

@erikjohnson2 There is a lot to unpack here. I think some of this can be handled by existing OSCAL capabilities (i.e., leveraged authorizations, component targeted assessment plans). I am happy...

@iMichaela Keep in mind that FedRAMP assesses systems as a whole and requires the same for continuous monitoring. Like the ISB, agencies will likely have a more decomposed view of...

Issue #1190 will be an attempt to develop some concrete examples of how to represent (re)use of select services from a cloud-based system in OSCAL. These examples should provide for...

We have considered producing a YAML-based version of the OSCAL models. This would be another output format of our metaschema-based production process. We could use this to autogenerate documentation and...

This relates to issues https://github.com/usnistgov/OSCAL/issues/538 https://github.com/usnistgov/OSCAL/issues/843 https://github.com/usnistgov/OSCAL/discussions/1115. This also relates to PR #1196. Perhaps this could be added to that PR?

There are some good points here. @aj-stein-nist Would you please summarize the points made above? Alternately, @GaryGapinski you could provide a summary.

- For the `--validate` option in schema generation, we cannot use the option due to Metaschema entity resolution issues during the schema generation process. - The converter generation process is...

Maybe [Hugo templating](https://gohugo.io/templates/rss/) can be used to address this?