David Waltermire

@guyzyl We can discuss this on a lunch with the Devs to get community feedback on the desire to do this and any impacts this will cause. If we make...

Doing a `git pull --ff-only` would be an easy fix.

@aj-stein-nist and @Compton-NIST Was there a plan to produce an example or a few? This wasn't explicitly stated in the goals. If so, it might be good to create a...

It looks like the prop `control-origination` is only supported at the `implemented-requirement` level right now. This can be added to the statement, by-component, and statement/by-component levels. It should be noted...

This was a gap identified in #1385. Perhaps this could be addressed as part of this issue. We need to consider a way forward that aligns with how FedRAMP is...

@SilentEsper Can you provide a list of the property names that are concerning you? A bit more detail will help us figure out how best to address this.

We can add props. We should also consider supporting responsible role here.

I am not sure this is a schema issue. Looking at the [XML](https://github.com/usnistgov/OSCAL/blob/9f17e56826c72f06b48ce66cf05dfc58f852b116/xml/schema/oscal_mapping_schema.xsd#L1278) and [JSON](https://github.com/usnistgov/OSCAL/blob/9f17e56826c72f06b48ce66cf05dfc58f852b116/json/schema/oscal_mapping_schema.json#L723) implementations, the relationship value is required. This appears to be an issue with the generated...

@aj-stein-nist investigated this with me and we identified a JSON schema generation bug that is causing this. usnistgov/metaschema#240 was created to fix the schema generation bug. Nothing more to do...

Pushing this to the OSCAL 1.1 release.