Michaela Iorga

@Telos-sa - Can you provide please the entire file (curated) via email at [email protected]. The snippets are not providing full proof that the data is in the right place. The...

It is a good catch. Thank you. WE are working on new OSCAL content releases (CSF v2.0 and 800-171), and will address this bug as well

@Telos-sa - This is an OSCAL schema issue not OSCAL content. Can you please move the issue to the https://github.com/usnistgov/OSCAL repo? . I could do it myself, but it would...

@Telos-sa - Thank you for the additional explanation. This is still not an `oscal-content` issue. Are you OK if I move it to the correct repo?

@aj-stein-gsa - Thank you for opening this issue. I am concerned that GRC tools or other implementors that developed tools based on the existing metaschema definitions of the models will...

> > @aj-stein-gsa - Thank you for opening this issue. I am concerned that GRC tools or other implementers that developed tools based on the existing metaschema definitions of the...

@HillviewCap - Please note all checks fail in this PR. Please provide a justification for your PR approval.

@brian-ruf - thank you resurfacing this issue. I raised it long ago in a separate context and got a heavy push back from the technical director of that time. Let's...

> @iMichaela can you take a look at this I'll put it on my ToDo list and mark it with high priority. Thank you.

> @brian-ruf if possible, are we able to add "hardware-model" to this list. See [PR 1088](https://github.com/GSA/fedramp-automation/pull/1088). Thank you. @Gabeblis - enhancing (adding) accepted values to existing constraints is not a...