W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > January 2019

[dxwg] Comments to DCAT identifier section (#675)

From: Andrea Perego via GitHub <sysbot+gh@w3.org>
Date: Sun, 20 Jan 2019 00:40:01 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-401049642-1547944799-sysbot+gh@w3.org>
andrea-perego has just created a new issue for https://github.com/w3c/dxwg:

== Comments to DCAT identifier section ==
A couple of comments on the current version of the [DCAT section about identifiers](https://w3c.github.io/dxwg/dcat/#Dereferenceable-identifiers):

1. The text mentions as examples of ID schemes DOIs, ELIs, and arXiv. This are all about documents, datasets, and, in general, creative works. But in the same section it is also said that IDs can apply to any entity in DCAT (see also the relevant discussion in https://github.com/w3c/dxwg/issues/67). Considering the importance of IDs also to identify "actors", I think it is worth mentioning ID schemes as ORCID, VIAF, ISNI, etc., and possibly include them in examples.

2. One of the topics addressed in that section is to use URIs for identifiers whenever available. The problem here is that the URI pattern to be used for this purpose is not always unique. E.g., for DOIs, people use `http://doi.org/`, `http://dx.doi.org/`, `https://doi.org/`. So, I wonder whether we could provide some guidance on that (e.g., the current recommendation in CrossRef and DataCite is to use the URI prefix `https://doi.org/`). In case it could turn to be useful, at JRC we drafted a mapping table for the ID schemes supported in DataCite - you can find it here: 
This table (or a revised version of it) could be included in appendix to the DCAT spec as a non-normative guidance

3. The section refers to the `info:` URI scheme in the text and examples. I wonder whether we should avoid mentioning it, as the info Namespace Registry has been closed in 2010.

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/675 using your GitHub account
Received on Sunday, 20 January 2019 00:40:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 April 2019 13:45:06 UTC