In the control-construct, the forwarding-domain attribute contains the forwarding construct that as per the core-model definition should be named as "fc" while in the yaml file is reported as "forwarding-construct".
Please correct the yaml file with the correct naming.
Also the following APIs should be fixed with the correct naming:
the change from forwarding-construct to fc needs not to be done for the default forwarding-domain schema under components, but only for the schema which is related to the MWDI/device CC definition (i.e. in the FORWARDING_DOMAIN schema only)
the reference is kept as FORWARDING_CONSTRUCT (instead of FC)
everywhere in the path definitions of the related apis where the forwarding domain is used, the forwarding-construct is also changed to fc
In the control-construct, the forwarding-domain attribute contains the forwarding construct that as per the core-model definition should be named as "fc" while in the yaml file is reported as "forwarding-construct".
Please correct the yaml file with the correct naming.
Also the following APIs should be fixed with the correct naming: