Following the raised issue of missing Catalog, a straightforward way to ensure DCAT-AP 3.0.1 compliance without expanding the core CCMM model is to clarify the catalog binding rule in the CCMM documentation:
When publishing CCMM metadata to a DCAT-AP compliant interface, CCMM datasets are simply encapsulated within a dcat:Catalog object representing the publishing repository (including its mandatory properties dct:title, dct:description, dct:publisher).
See https://semiceu.github.io/DCAT-AP/releases/3.0.1/#Catalogue
Following the raised issue of missing Catalog, a straightforward way to ensure DCAT-AP 3.0.1 compliance without expanding the core CCMM model is to clarify the catalog binding rule in the CCMM documentation:
When publishing CCMM metadata to a DCAT-AP compliant interface, CCMM datasets are simply encapsulated within a dcat:Catalog object representing the publishing repository (including its mandatory properties dct:title, dct:description, dct:publisher).
See https://semiceu.github.io/DCAT-AP/releases/3.0.1/#Catalogue