rdfs:domain conflict: dcatcim:Statemenents vs dcat:Dataset

[VladimirAlexiev]

https://github.com/entsoe/application-profiles-library/blob/main/NCP/RDFS/DatasetMetadata-AP-Voc-RDFS2020.rdf#L687 and
https://raw.githubusercontent.com/entsoe/application-profiles-library/refs/heads/ncp-v2-4-2/NCP/RDFS/DatasetMetadata-AP-Voc-RDFS2020.rdf :

  <rdf:Description rdf:about="http://purl.org/dc/terms/title">
    <rdfs:domain rdf:resource="https://cim4.eu/ns/dcatcim#Statements"/>
    <rdfs:domain rdf:resource="http://www.w3.org/ns/dcat#Dataset"/>

(@HarisVranaj I assume NCP 2.4.2 is the latest NCP).

This is another rdfs:domain conflict.
So with RDFS reasoning, anything with dct:title (eg a CIM Ontology) will become dcatcim:Statemenents and dcat:Dataset

Related to

• DatasetMetadata RDFS: URI-typed Dataset attributes have no rdfs:domain since 489c5c5 — class binding not derivable from RDFS, while SHACL still requires them #92
• DatasetMetadata: express reused-term class linkage with schema:domainIncludes (fixes #92) #99