- From: Jakub Klímek via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jul 2019 09:05:03 +0000
- To: public-dxwg-wg@w3.org
During the translation to Czech, I came across the annotations of external vocabularies and there is an issue with this approach. We SHOULD NOT annotate external properties and classes (such as DCTERMS) with DCAT specific texts, as those statements then apply to ALL instances of those properties, regardless of DCAT. Example: I have an endpoint where I use `dcterms:issued` for the date a book was issued in some library dataset. Now I use the same endpoint to store some DCAT metadata, and I load the DCAT vocabulary there. Suddenly, when someone looks at a record about a book, they see for instance `This indicates the date of listing the dataset in the catalog and not the publication date of the dataset itself.`, which makes no sense in this context. Therefore, if we absolutely need to state this information about the properties, we would have to create DCAT subproperties for everything and make the statements about them. Otherwise we should refrain from stating specific things about external vocabularies to avoid creating mess. The argument that "the user can choose to separate DCAT vocabulary with those annotations into a separate graph` IMHO does not hold, as we should not presume any particular named graph use case. -- GitHub Notification of comment by jakubklimek Please view or discuss this issue at https://github.com/w3c/dxwg/issues/725#issuecomment-513154247 using your GitHub account
Received on Friday, 19 July 2019 09:05:05 UTC