- From: Riccardo Albertoni via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Jun 2021 12:55:43 +0000
- To: public-dxwg-wg@w3.org
It seems there is no agreement on having `dcat:keyword` sub-property of `dcterm:subject`. I would suggest accepting that "we agree that we disagree" and solve the issue merging #PR 1385. PR #1385 aligns HTML and RDFs as it was meant by DCAT 2 , it removes the `dcat:keyword` sub-property of `dcterm:subject` from the RDF files. > I still think it is safer to just drop the range constraint for `dcat:keyword`: @andrea-perego I haven't understood why dropping the range for `dcat:keyword`. At the moment, `dcat:keyword` ranges in `rdfs:Literals`, and in the RDF files, the property is also defined as an `owl:DatatypeProperty`. What is the rationale behind the suggestion? -- GitHub Notification of comment by riccardoAlbertoni Please view or discuss this issue at https://github.com/w3c/dxwg/issues/175#issuecomment-866810728 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 June 2021 12:56:03 UTC