Brian Ruf

# Status 24-Sept-2020 Nearly finished the definition in issue #572, and will be turning our attention to this shortly.

**THIS WAS ORIGINALLY POSTED TO ISSUE #713. THIS IS A MORE APPROPRIATE LOCATION** **Looking for public review and feedback on this comment** The point of the CRM is to expose...

# Status 8-Oct-2020 Sketched out information requirements for CRM file and made available for comment. Our plan is to focus on this following the preparation of the OSCAL release candidate....

# For feedback In today's modeling session, we discussed the idea that "Customer Responsibility Matrix (CRM)" does not fully convey what we intend for this model in OSCAL since it...

# Insights During today's modeling session, two considerations were raised which warrant attention related to: - Baseline Details; and - Aggregated Capabilities ## Baseline Details The point was raised that...

@david-waltermire-nist @bradh @wendellpiez, while I agree with Dave's position as a recommended practice to avoid, I also feel this should be at the discretion of the tool developer. That said,...

First, I would encourage - as a best practice among profile creation tools - all conflicts be called to the attention of the profile creator at the time of creation,...

As for how conflicts should be managed by tools, whether while authoring a profile, or resolving one, I see the following functional steps (which ignore current tool capabilities for the...

@JJediny this issue is about how the syntax in an OSCAL profile is interpreted to create a new catalog. It is about a specific issue in that process where the...

@JJediny, sorry for any confusion. While @wendellpiez does use the word version a couple times, he does so more loosely. Version may not be the best word, as it's not...