<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello Yan , hello Semantics members,<br>
<br>
Thanks for bringing this use-case .<br>
<br>
I understand you need a ucd to tag your ePIC pid column .<br>
In terms of content descriptor , I understand you manipulate a
meta.id .<br>
but it's a persistent one , defined by ePIC .<br>
So a general UCD for this could be <br>
P meta.pid a general persistent identifier<br>
<br>
Vizier also uses PIDs , but resolved following the doi standard. The
UCD here is the existing <i>meta.ref.doi</i> <br>
which implies this ref can be resolved according to this standard .
<br>
<br>
The same would apply to ORCID , and we could define a new ucd : <br>
P meta.ref.orcid An pid resolved by ORCID compliant tools<br>
<br>
It is definitely interesting to know more about your data release
and what you do with these PIDs in terms of<br>
definition , attribution, resolver, maintenance .<br>
<br>
Cheers, Mireille<br>
<br>
<div class="moz-cite-prefix">Le 09/11/2021 à 09:54, Yan Grange a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:f0502b57-bd4a-ebdf-91f3-ab8f8f67da5d@astron.nl">Hi
Mireille (and semantics working group),
<br>
<br>
I could immagine that for ORCID it should not be too hard to find
a use case (maybe Markus has ideas). For me the apparant use case
is simple: I've got an upcoming data release and we minted EPIC
PIDs for each of our data products. I've got those in a table and
I am looking for a UCD to map them. Based on what Marco says I
could use a handle.net URL, but I think the handle.net part is not
necessarily guaranteed to be persistent so that may actually break
the idea of a PID. If you think that is useful I can give a few
details on my data relase :)
<br>
<br>
Cheers
<br>
<br>
Yan
<br>
<br>
On 09/11/2021 09:18, Mireille LOUYS wrote:
<br>
<blockquote type="cite">Hi Yan , hi Semantics ,
<br>
<br>
That sounds useful and reasonable to add this UCD term in the
UCD tree .
<br>
<br>
I agree.
<br>
Is there a use case /example that we could describe together to
include this in a VEP-UCD?
<br>
<br>
many thanks,
<br>
Mireille
<br>
<br>
Le 08/11/2021 à 19:24, Yan Grange a écrit :
<br>
<blockquote type="cite">Hi Semantics people,
<br>
<br>
What do you think of the following concept for a UCD? Looking
forward to your feedback!
<br>
<br>
==============8<==============
<br>
<br>
Vocabulary:
<a class="moz-txt-link-freetext" href="https://raw.githubusercontent.com/ivoa-std/UCDList/v1.4-EN/ucd-list.txt">https://raw.githubusercontent.com/ivoa-std/UCDList/v1.4-EN/ucd-list.txt</a>
<br>
Author: <a class="moz-txt-link-abbreviated" href="mailto:grange@astron.nl">grange@astron.nl</a>
<br>
Date: 2021-11-08
<br>
New Term: meta.ref.pid
<br>
Action: Addition
<br>
Label: Persistent Identifier
<br>
<br>
Description: Persistent Identifier (dereferenceable)
<br>
<br>
Rationale: The current UCD list does contain a way to refer to
persistent identifiers of type DOI (meta.ref.doi). However
other persistent identifiers (e.g. EPIC PIDs, ORCIDs, etc) are
not covered by this. Since all PIDs can in principle be
resolved by all resolvers, no functional difference should
exist between them and therefore I propose to inculde a
general pid term in stead of having one entry per PID type.
For backwards compatibility I propose not to change anything
to meta.ref.doi and keep it in place.
<br>
<br>
==============8<==============
<br>
<br>
Cheers,
<br>
<br>
Yan Grange
<br>
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
--
Mireille Louys, MCF (Associate Professor)
Centre de données CDS IPSEO, Images, Laboratoire Icube
Observatoire de Strasbourg Telecom Physique Strasbourg
11 rue de l'Université 300, Bd Sebastien Brandt CS 10413
F- 67000-STRASBOURG F-67412 ILLKIRCH Cedex
Tel: +33 3 68 85 24 34</pre>
</body>
</html>