David Waltermire

Addressing this issue requires features from OSCAL 1.1.0. Moving this issue to that milestone.

@ohsh6o Do you have an update to this proposal based on your notes above?

@ohsh6o Can you create a concrete change proposal listing each property to add and providing a corresponding definition. We talked about organization name (or party reference), `dataset-name`, and `dataset-version` on...

This issue requires building a relationship between parameters in the catalog model. It also requires some thought on how to address parameter pairs related to set-parameter in catalogs, profiles, and...

We should hold off on addressing this until we make significant progress on #1058, since how we address rules may provide a different path for solving this. I am going...

This will require changes to the Metaschema syntax. Created usnistgov/metaschema#185 for this.

The JSON schema fragment for this property is currently: ```json "oscal-profile-oscal-profile:include-all" : { "title" : "Insert All", "description" : "Insert all controls from the imported catalog or profile resources identified...

We discussed this on the 6/25/2021 model review. There seems to be an emerging consensus that changing this to a boolean field with a required `true` value would be ideal;...

This is being worked as part of #1058, which is targeting a 1.2.0 release. Pushing this back to 1.2.0 as a result.

This seems to be atypical for a continuous integration approach where the philosophy is to test that every commit is verified for correctness. Why not enable these validation checks to...