- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Mar 2021 23:56:27 +0000
- To: public-dxwg-wg@w3.org
> > 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 > > Wouldn't it be simpler to stick to one property for everything, qualified if need be (thus indicating `adms:idnetifier`, rather than `dct:identifier`) as surely it will confuse users to see two properties with the same ID but different namespaces and different modes of use. > > So use `adms:identifier` for 'the identifier assigned to the resource in the catalogue' but create some scoping for that (perhaps that's just the un-qualified use of the property). @nicholascar , I think `dcterms:identifer` / `adms:identifier` are already playing these roles - i.e., `dcterms:identifier` being used as the un-qualified form of `adms:identifier`. -- GitHub Notification of comment by andrea-perego Please view or discuss this issue at https://github.com/w3c/dxwg/issues/771#issuecomment-803487220 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 20 March 2021 23:56:29 UTC