UAF14 — ForceDesignation literals are unusuable without customization in UAF v1.3

OpposableElement.designation is typed by DesignationKind (an Enumeration) instead of allowing selection of ForceDesignation literals, rendering the force-affiliation use case unusable in descriptive architectures.

Problem
Because the type of the designation property is DesignationKind (i.e., the enumeration type), a conforming tool (e.g., Cameo 2026x) correctly treats the legal values as instances of DesignationKind (enumerations such as ForceDesignation), not the enumeration literals of ForceDesignation.
Consequently:

Modelers cannot select RedForce / BlueForce / etc. via the normative tag.
Assigning the enumeration ForceDesignation itself conveys no force-affiliation information useful for descriptive architecture, analysis, color-coding, filtering, or querying.
The primary practical use case for force designation on Operational Performers (and other OpposableElements) is therefore unsupported by the normative profile.

This creates a significant usability and semantic gap for Mission Engineering and operational architecture models that rely on force affiliation (Blue/Red/White/etc.) as a first-class descriptive property.