Moved allowed-value for component type to make it available in component definition as well not just ssp.

Author: Michaela Iorga

src/metaschema/oscal_implementation-common_metaschema.xml

@@ -242,7 +242,6 @@
                         <enum value="this-system">The system as a whole.</enum>
                         <enum value="system">An external system, which may be a leveraged system or the other side of an interconnection.</enum>
                         &allowed-values-component-type;
-                        <enum value="network">A physical or virtual capability that provides connectivity, segmentation, routing, traffic distribution, name resolution, or network boundary control.</enum>
                   </allowed-values>
             </constraint>
       </define-flag>

src/metaschema/shared-constraints/allowed-values-component-type.ent

@@ -13,3 +13,4 @@
 <enum xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0" value="region">An isolated geographic area where a cloud service provider (CSP) operates a cluster of data centers.</enum>
 <enum xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0" value="zone">A fault-isolated cloud computing data center group within a region, connected by low-latency links.</enum>
 <enum xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0" value="resource-container">A logical administrative, governance, billing, or resource-scoping boundary used to organize cloud resources.</enum>
+<enum xmlns="http://csrc.nist.gov/ns/oscal/metaschema/1.0" value="network">A physical or virtual capability that provides connectivity, segmentation, routing, traffic distribution, name resolution, or network boundary control.</enum>