- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Sun, 14 Mar 2021 13:16:35 +0000
- To: public-dxwg-wg@w3.org
About the proposed usage note: I think that suggesting that `dct:identifier` can be used for multiple identifiers has some issues ([UC11](https://www.w3.org/TR/dcat-ucr/#ID11) gives some background information) and it is not aligned with what said in [ยง7 Dereferenceable identifiers](https://www.w3.org/TR/vocab-dcat-2/#dereferenceable-identifiers), which makes a distinction between primary and secondary identifiers following DCAT-AP (where `dct:identifier` is used for the primary identifier, and `adms:identifier` for secondary/additional identifiers). The relevant usage notes in the DCAT-AP specification: For `dct:identifier`: > This property contains the main identifier for the Dataset, e.g., the URI or other unique identifier in the context of the Catalogue. For `adms:identifier`: > An identifier in a particular context, consisting of the string that is the identifier; an optional identifier for the identifier scheme; an optional identifier for the version of the identifier scheme; an optional identifier for the agency that manages the identifier scheme The distinction between primary / secondary identifiers is present also in other metadata schemas - as DataCite and the metadata guidance for Google Dataset Search. My suggestion is therefore to limit the scope of `dct:identifier` to the primary identifier (the identifier assigned to the resource in the catalogue), and to add `adms:identifier` to the relevant class descriptions - as per https://github.com/w3c/dxwg/issues/761 -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/771#issuecomment-798905066 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 14 March 2021 13:16:37 UTC