User Story:

As an OSCAL tool developer, I would like Properties to be optionally groupable in order to differentiate different sets of Properties from each other.

For example: one set of Properties may apply at integration time while another set of Properties may apply at deployment time; or one set of Properties may apply during development while a different set of Properties may apply during production.

An existing grouping example is under OSCAL Catalog, where Group is permitted to contain params, props...groups. It would be useful to have a grouping mechanism especially for Properties in other documents such as Component Definition, Profile and Assessment Results.

Goals:

The ability to group Properties in in OSCAL documents besides Catalog, such as Component Definition, Profile and Assessment Results.

• Add a group flag to the property Metaschema definition
• Develop a concrete example
• Socialize this during an OSCAL model review.
• Collect feedback, and identify any follow-on work if needed.

Dependencies:

N/A

Acceptance Criteria

• All OSCAL website and readme documentation affected by the changes in this issue have been updated. Changes to the OSCAL website can be made in the docs/content directory of your branch.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.
• The CI-CD build process runs without any reported errors on the PR. This can be confirmed by reviewing that all checks have passed in the PR.

{The items above are general acceptance criteria for all User Stories. Please describe anything else that must be completed for this issue to be considered resolved.}