- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 May 2021 07:33:03 +0000
- To: public-dxwg-wg@w3.org
I suggest dropping the `rdfs:member` reference. That is a by-way of rdfs which no-one much uses and it is a bit unclear what meta-level it is supposed to represent. However, these kinda belong together: ``` dcat:service rdfs:domain :Catalog ; rdfs:subPropertyOf dcterms:hasPart ; . ``` The generic relationship of a catalog to its parts is through `dcterms:hasPart`. `dcat:service`, `dcat:dataset` and `dcat:catalog` are specializations of 'has-part' for different kinds of catalogued thing - i.e. this sub-property axiom applies in the context of a Catalog. The sub-property relationship probably would not apply to a link to services in other contexts. But after all, DCAT is primarily about data catalogs, so perhaps you should not expect `dcat:service` to a be a free-floating predicate that you can pick and use in a non-catalog context. (While I agree that SHACL etc may be a better way to _implement_ such constraints, and can be tuned to different contexts, DCAT is currently _specified_ in RDFS and OWL, not SHACL.) -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1363#issuecomment-844806375 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 May 2021 07:33:06 UTC