From 95f11d7fb52cf1608b580cfc9af35eefb226591e Mon Sep 17 00:00:00 2001
From: Al S <xee5ch@member.fsf.org>
Date: Fri, 21 Feb 2025 21:53:51 -0500
Subject: [PATCH] Option 2 add enum value for #2112

Instead of adjusting the constraint, this changes alternatively proposes
updating the enumeration with a new enum value of "recommendation." This
may be the proposal of @iMichaela in the comment below, and this change
proposal is to determine if it is the preferred approach.
---
 src/metaschema/oscal_catalog_metaschema.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/metaschema/oscal_catalog_metaschema.xml b/src/metaschema/oscal_catalog_metaschema.xml
index 8b476aa612..c4dd82fa6f 100644
--- a/src/metaschema/oscal_catalog_metaschema.xml
+++ b/src/metaschema/oscal_catalog_metaschema.xml
@@ -263,6 +263,7 @@
                               'assessment-method' instead.</enum>
                         <enum value="assessment-method">The part describes a method-based assessment
                               over a set of assessment objects.</enum>
+                        <enum value="recommendation">The part describes a specific approach for a set of implementation requirements more opinionated than a statement or guidance.</enum>
                   </allowed-values>
                   <allowed-values id="oscal-control-statement-part-subpart-name"
                         target="part[has-oscal-namespace('http://csrc.nist.gov/ns/oscal') and @name='statement']//part[has-oscal-namespace('http://csrc.nist.gov/ns/oscal')]/@name">