W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > August 2018

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

From: Jakub Klímek via GitHub <sysbot+gh@w3.org>
Date: Wed, 22 Aug 2018 06:14:40 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-352816321-1534918479-sysbot+gh@w3.org>
jakubklimek has just created a new issue for https://github.com/w3c/dxwg:

== dcat:Catalog/dct:hasPart inconsistent with DCAT-AP v1.1 ==
In [DCAT-AP v1.1](https://joinup.ec.europa.eu/release/dcat-ap-v11) 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 https://github.com/w3c/dxwg/issues/116#issue-297283045. 

In [DCAT revision](https://w3c.github.io/dxwg/dcat/#Property:catalog_hasPart), 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 #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.

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/319 using your GitHub account
Received on Wednesday, 22 August 2018 06:14:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:45 UTC