Doc 3, Line 35, API[content-mgmt-api-3]/spec is an object that cannot be empty. It should contain definition, lifecycle, system, and type properties and may contain an optional owner prop.

Doc 4, Line 44, API[content-mgmt-api-4]/spec must have required property type.

Doc 5, Line 59, API[content-mgmt-api-5]/spec/type value cannot be empty and must be one of the allowed values: openapi, asyncapi

Doc 6, Line 73, API[content-mgmt-api-6]/spec/type value myapi is not one of the allowed values: openapi, asyncapi

Doc 7, Line 86, API[content-mgmt-api-7]/spec must have required property lifecycle.

Doc 8, Line 102, API[content-mgmt-api-8]/spec/lifecycle value cannot be empty and must be one of the allowed values: experimenting, developing, maintaining, deprecating, obsolete

Doc 9, Line 116, API[content-mgmt-api-9]/spec/lifecycle value mylifecycle is not one of the allowed values: experimenting, developing, maintaining, deprecating, obsolete

Doc 10, Line 128, API[content-mgmt-api-8]/spec must have required property system.

Doc 11, Line 145, API[content-mgmt-api-11]/spec/system is a string that cannot be empty. It should be populated or be removed completely if not required.

Doc 12, Line 159, API[content-mgmt-api-11]/spec/system value content-management is invalid. Expected Pattern: system:[<optional-namespace>/]<system-name> e.g. system:default/appointment-manager, system:appointment-manager

Doc #3 is invalid

Doc #4 is invalid

Doc #5 is invalid

Doc #6 is invalid

Doc #7 is invalid

Doc #8 is invalid

Doc #9 is invalid

Doc #10 is invalid

Doc #11 is invalid