<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi all<br>
</p>
<p>I come back to this "counterpart" proposal for DataLink semantics
vocabulary<br>
</p>
<p>A few remarks before modifying/completing the VEP-project</p>
<p>1 ) I got the comment by Markus that the numbering should be
given with some caution</p>
<p>2 ) other comments about the rationale and lack of example/</p>
<p>3 ) as for the example I had some private discussions wuith
Carlos from SVO. they have a large number of various conesearch
services with DataLink like that.</p>
<p>Carlos allowed me to use these. Currently what they have in
semantics FIELD is "auxiliary" which I think is the wrong term.
Typically this would be a perfect use case for "counterpart"</p>
<p>4 ) Other terms have been proposed for this kind of use-cases. I
add these alternates terms in the discussion section</p>
<p>Cheers</p>
<p>François</p>
<p>Vocabulary:<a class="moz-txt-link-freetext" href="http://ivoa.net/rdf/datalink/core">http://ivoa.net/rdf/datalink/core</a>
<br>
Author: François Bonnarel
<br>
Date: 2020_05-22<br>
Supercedes: VEP-001
<br>
<br>
New Term: counterpart
<br>
Action: Addition
<br>
Label: counterpart dataproduct
<br>
Description: Data products that are related to #this for various
interpretation purposes.
<br>
Used-in:
<br>
various SVO ConeSearch services (Cortesy Carlos Rodrigo / SVO
)</p>
<p> CATlib spectral library (<a class="moz-txt-link-freetext"
href="http://svo2.cab.inta-csic.es/vocats/v2/catlib/">http://svo2.cab.inta-csic.es/vocats/v2/catlib/)<br>
</a></p>
<p> ----> Datalink example : <a
class="moz-txt-link-freetext"
href="http://svo2.cab.inta-csic.es/vocats/v2/catlib/dl.php?ID=BD-+01+2582">http://svo2.cab.inta-csic.es/vocats/v2/catlib/dl.php?ID=BD-+01+2582</a></p>
<p> MILES spectral library ( <a class="moz-txt-link-freetext"
href="http://svo2.cab.inta-csic.es/vocats/v3/miles/">http://svo2.cab.inta-csic.es/vocats/v3/miles/
)<br>
</a></p>
<p> ---> DataLink example <a
class="moz-txt-link-freetext"
href="http://svo2.cab.inta-csic.es/vocats/v3/miles/dl.php?ID=HD102634">(http://svo2.cab.inta-csic.es/vocats/v3/miles/dl.php?ID=HD102634)</a></p>
<p> Could be used by VizieR for their "associated data"</p>
<p>
Rationale:
<br>
Astronomers often want to associate #this (astronomical
objects, sources or datasets ) with dataproducts of other
provenance (but sharing some common features with them).
The purpose maybe for comparison, cross-corelation, multi-band
interpration, follow-up of changes, checking simulations results
versus observations. <br>
Examples of that are measurements in another band, images,
cubes, spectra, timeseries of a source, same dataproduct type and
location in physical space but at another time, etc .... <br>
</p>
<p>
Discussion: <br>
</p>
<p> The use case there is different from the one considered in
VEP-003/VEP-004 (#sibling , #co-derived, #co-generated) because
there is no common provenance or progenitor between both sides of
the link.</p>
<p> The original proposed term was #associated-data borrowed to
VizieR (VEP-001). This one was considered too vague.<br>
</p>
<p> Other proposed terms : <br>
</p>
<ul>
<li> #isObservationOf, #contains, #followup, #cross-associated,
#see-also , <br>
</li>
</ul>
<p> None of these have been retained : too vague, or too
specific to some more restricted use cases<br>
</p>
<ul>
<li>#compared-to : this one is currently a private communication.
<br>
</li>
</ul>
<p><br>
</p>
<div class="moz-cite-prefix">Le 06/05/2020 à 14:42, François
Bonnarel a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:1a4a14bd-0992-f5fb-8094-8e2555aa7e74@astro.unistra.fr">Hi
Mireille, Markus, all
<br>
<br>
Le 28/04/2020 à 19:02, Mireille LOUYS a écrit :
<br>
<blockquote type="cite">Sounds ok to me.
<br>
<blockquote type="cite">
<br>
Now, vocabularies 2 currently says on VEP review:
<br>
<br>
During the process, all parts of the VEP may be changed
except the
<br>
term(s) proposed.
<br>
<br>
and I still think that's largely a good idea.
<br>
<br>
Hence, before I retract VEP-003 and replace it with an
essentially
<br>
identical VEP-004 with co-generated: Would anyone here object
to that
<br>
or strongly prefer #sibling?
<br>
</blockquote>
<br>
I agree with "co-generated". The meaning is close to "sibling" ,
<br>
<br>
has less connotation towards graphs' theory and may be
understandable for a larger audience.
<br>
</blockquote>
:-)
<br>
<blockquote type="cite">
<br>
<blockquote type="cite">
<blockquote type="cite">p
<br>
<br>
I propose something like "#other" or "#alternate" (
the latter was
<br>
already proposed by Markus ..... in 2015 !!! semantics
session during
<br>
interop In Sydney)
<br>
</blockquote>
#alternate was really intended when #this has multiple
<br>
representations (classic example: a spectrum that you get as
<br>
FITS-array, FITS-table, SDM VOTable, or CSV). I still think
this is
<br>
a good idea because we ought to make it a SHOULD that there's
just
<br>
one #this per ID. But that's for another VEP.
<br>
</blockquote>
<br>
I agree. I understand this term means "same content in a
different representation" while we need a term to mention
<br>
<br>
we link to another dataset interesting to hela /enrich the
interpretation of the data stored in #this.
<br>
<br>
"related_data", "other", "see-also" seem too vague for this ,
but I cannot make up a better term .:-(
<br>
<br>
<br>
<br>
</blockquote>
I was still looking for a word which says it is
<br>
<br>
1 ) not metadata, but data, not calibration data, not
auxiliary (but main information) not documentation, and not a
service
<br>
<br>
2 ) is associated to the #this thing but is neither derived,
nore progenitor , nore co-generated.
<br>
<br>
We have plenty of use cases like that in VizieR, for
XMM, probably for ESO if I remember well an older request from
Alberto Micol. And this also can be valid for "TimeSeries" outside
the Gaia use case well represented by co-generated (see VEP-004)
<br>
<br>
Eventually I found the "counterpart" term.
<br>
<br>
Online Oxford dictionary definition reads "A person or thing
holding a position or performing a function that corresponds to
that of another person or thing in another place"
<br>
<br>
Sounds good to me. Is more general than "contains"
(corresponds to the source #this but in the "image" world")
"followup" (corresponds to #this but in the future) and
"cross-associated," "cross-correlated" ... but is still covering
these terms as an head term if desired.
<br>
<br>
I think with "progenitor", "derived", "co-generated" and
"counterpart" we cover a wide field of relationships between #this
and a linked dataproduct.
<br>
<br>
As you know from the DataLink discussion the actual
dataproduct_type will be given in the mime-type parameter of the
"content-type" field of Datalink response
<br>
<br>
So This is the VEP-005
<br>
<br>
Vocabulary:<a class="moz-txt-link-freetext" href="http://ivoa.net/rdf/datalink/core">http://ivoa.net/rdf/datalink/core</a>
<br>
Author: François Bonnarel
<br>
Date: 2020_05-06
<br>
Supercedes: VEP-001
<br>
<br>
New Term: counterpart
<br>
Action: Addition
<br>
Label: counterpart dataproduct
<br>
Description: Data products holding a position that corresponds to
#this in another data space.
<br>
Used-in:
<br>
VizieR or ESO example to be worked on
<br>
<br>
Rationale:
<br>
Astronomers often want to associate to astronomical objects,
sources or datasets dataproducts of other provenance but sharing
some common features with those.
<br>
<br>
examples of that are measurements in another band, images,
cubes, spectra, timeseries of a source, same dataproduct type and
location in physical space but at another time, etc ....
<br>
<br>
<br>
Cheers
<br>
<br>
François
<br>
<br>
<br>
<br>
<br>
</blockquote>
</body>
</html>