- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Jun 2021 09:29:20 +0000
- To: public-dxwg-wg@w3.org
@aisaac , I see your point, and I agree that the formal definition of `dcterms:subject` does not prevent it from being used with literals. My concern is whether this was the actual intention. DCTERMS has so far kept a clear distinction between object and datatype properties, so I wonder whether the current version has changed this approach. Should this be the case, it might be worth stating this more explicitly in property definitions. Said that, I still think it is safer to just drop the range constraint for `dcat:keyword`: not making it a sub-property of `dcterms:subject` does no harm, but has the advantage of avoiding misunderstandings on how this property should be used. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/175#issuecomment-864525561 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 21 June 2021 03:34:59 UTC