Trouble with a deprecated default
Markus Demleitner
msdemlei at ari.uni-heidelberg.de
Mon Feb 3 13:52:56 CET 2025
Dear Gilles,
On Mon, Feb 03, 2025 at 10:37:44AM +0100, gilles landais via registry wrote:
> Thank you to take into account DataCite-IVOA compatibility.
>
> I agree that "Collected" sounds enough generic to be used. So (b) sounds
> acceptable to reduce compatibility problem and to manage the existing.
>
> I don't know how the Date role is used in the registry. Are there exotic
> values ?
There shouldn't be, but the RofR validator does not yet evaluate the
vocabularies (shame on me). In reality, here's what roles we have
according to RegTAP (where "representative" already shows up as
"collected" according to RegTAP's policy of honouring the
vocabularies' UseInstead triples):
+-----------------------+-------+
| value_role | n |
+-----------------------+-------+
| updated | 27594 |
| created | 26711 |
| collected | 1175 |
| release | 96 |
| inspected | 41 |
| exportrequested | 10 |
| authority established | 1 |
| availability | 1 |
| project end | 1 |
| project start | 1 |
+-----------------------+-------+
> According to the existent, is it possible to force the role value with a
> controlled vocabulary?
Well, it's what VOResource says, so Records using either of the four
terms with just one match are VOResource-invalid. But then,
invalidity at a level of 10^-4 is really, really good in this
business...
Thanks,
Markus
(who will now do the change to the VOResource schema)
More information about the registry
mailing list