dcat:Catalog/dct:hasPart inconsistent with DCAT-AP v1.1

[jakubklimek]

In DCAT-AP v1.1 the dct:hasPart property on dcat:Catalog has a specified range dcat:Catalog and is used to create a hierarchy of catalogs, specifically, it is described as This property refers to a related Catalogue that is part of the described Catalogue. This is also mentioned in #116 (comment).

In DCAT revision, it currently has a range dcat:Resource. It is used as a superproperty of dcat:dataset for inclusion of datasets in catalogs, and dcat:service for inclusion of services.

However, dcat:Catalog is not a subclass of dcat:Resource, hence the inconsistency.

1. Do we actually need a superproperty of dcat:dataset and dcat:service? Is it abstract (not to be used) or are there now entities other than datasets and services allowed in Catalogs? (related to Change domain or create superclass of dcat:Distribution #317)
2. If so, does it need to be dct:hasPart ? It could be some other property, leaving dct:hasPart as a relation between two catalogs.

[dr-shorthair]

dcat:Catalog is a subclass of dcat:Dataset, which is a subclass of dcat:Resource, so I think there is no major inconsistency here

[jakubklimek]

@dr-shorthair Ow, you're right, I overlooked the edge in the diagram. My fault.