<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi ,</p>
<p>the contributor type has not been selected in Data Origin yet - I
didn't thought about it .<br>
but may be there are some interests in EPN (or in VESPA who
provides a compilation of datasets) ? <br>
</p>
<p>My feeling on contributors is that it concerns the data producers
and not the data-centers - It is an interesting information, but
difficult to have I think.</p>
<p><br>
</p>
<p>If I could suggest an other request more focused on data
dissemination.<br>
</p>
<br>
<p>For instance, in VizieR, we add authors without any additional
information and we complete the information with the bibcode to
link the journal (content.source in ivoa registry)<br>
The journal is not clearly specified. <br>
</p>
<p>We do the same for data coming from space agencies (for instance
Gaia) - but in that case, the reference is not adapted and could
be improved using relationship/relationshiptype.</p>
<p>eg:</p>
<p><relationship><br>
<relationshipType><span style="color: rgb(0, 0, 0);
font-family: sans; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(238, 238,
255); text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">IsDerivedFrom</span></relationshipType><br>
<relatedResource
altIdentifier="doi:10.5270/esa-qa4lep3">ESA Gaia
DR3</relatedResource><br>
</relationship><br>
</p>
<p>This information is not provided by VizieR yet, and I am not sure
it is often used today - neither in registry, nor in datacite.<br>
However, it could be a way to improve an interconnected network in
a machine-readble way.<br>
</p>
<p><br>
</p>
<p>Gilles<br>
</p>
<p><br>
</p>
<p>Le 08/12/2022 à 10:00, Markus Demleitner a écrit :</p>
<blockquote type="cite"
cite="mid:20221208090055.q7fuvyxlixwhqs6t@victor">
<pre class="moz-quote-pre" wrap="">Dear Renaud,
On Wed, Dec 07, 2022 at 04:48:37PM +0100, Renaud Savalle wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">There is a growing interest (from some EPN-TAP providers) to add
contributor types (possibly controled by a Vocabulary) in the
VOResource schema (similar to what can be done with DataCite - see
line 7a of Table 4 in
<a class="moz-txt-link-freetext" href="http://schema.datacite.org/meta/kernel-4.3/doc/DataCite-MetadataKernel_v4.3.pdf">http://schema.datacite.org/meta/kernel-4.3/doc/DataCite-MetadataKernel_v4.3.pdf</a>)
This is somewhat related to the note "Data Origin in the VO"
currently being drafted by the DCP WG:
<a class="moz-txt-link-freetext" href="https://github.com/gilleslandais/ivoa-dcp-data-origin">https://github.com/gilleslandais/ivoa-dcp-data-origin</a>
Now, it might be too early for VOResource 1.2, as I understand that
more discussions are planned about "Data Origin in the VO" during
the next Interop meeting in 2023.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
My take on this would be that *if* we add contributor types, it
should almost certainly be a copy of what DataCite does, as everyone
would justifiably cross with us if we pulled up something that is
similar but subtly different.
Given that, it would be really simple to add a vr:Contributor
extending vr:ResourceName (contributor's current type) type
that has an contributorType attribute which would say: "See the
latest version of the DataCite metadata kernel for the values allowed
here". That would suck a bit for validators that would need extra
code if they wanted to validate that, but as long as this is not used
operationally, I think we could live with having it not validated.
But that brings me to the central question: Why would we want this?
I've never been really clear on why one would want this contributor
thing in the Registry -- what sort of discovery would become possible
with it? Or should that cover a non-discovery use case?
One scenario I could follow is when people generate DataCite metadata
from VOResource records (which is lossy but not hard; see
<a class="moz-txt-link-freetext" href="https://volute.g-vo.org/svn/trunk/projects/registry/dois">https://volute.g-vo.org/svn/trunk/projects/registry/dois</a>) *and* want
these contributor types in the datacite records (where I can imagine
a few uses for them). But does anyone actually plan to do this?
So... say if someone comes up with a concrete plan what to do with
contributorType in VOResource I'd not argue against having it in
version 1.2 -- but a "might be useful some day" wouldn't be strong
enough in my book to accept the somewhat odd construct referencing a
vocabulary written in an external and moving standard.
-- Markus
</pre>
</blockquote>
</body>
</html>