Add System Flag or Prop to Catalog Parameter Guidelines

[aj-stein-nist]

User Story

As an OSCAL tool developer or content consumer, I need a method to identify what organization defined a given parameter guideline. I would like a method to properly track what organization creates or maintains a given parameter guideline.

Goals

Address feedback, design a solution, and implement accordingly given PR feedback in david-waltermire#52 (comment). (NOTE: This is a replacement issue for david-waltermire#54 because GitHub doesn't allow transfering from personal owner to org owner repo.)

Dependencies

No response

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.

[GaryGapinski]

Is it safe to presume that this issue is prompted in part by the {0,∞} cardinality of guidance?

One might desire the same declaration of provenance for constraint {0,∞}.

As of the current (1.0.4) schema guideline has blockElementGroup content, which precludes prop and has no element which could be coaxed into a declaration of provenance. However, param itself has elements which could be used to denote provenance (prop, link).

This appears to tacitly acknowledge the possibility of multiple origins of guidance (if so, profile resolution gets more complex).

[Arminta-Jenkins-NIST]

At 10/12 Triage Meeting: Team agrees that this issue needs to be marked as DEFINE.