Voc in the VO 2 / remarks

[François Bonnarel]

Dear all,

After some experience with VEP and the extension of lists of terms 
(mainly DataLink semantics vocabulary but also having dataproduct_type 
in mind)  I would like to propose some improvment to the process

       1 ) VEI instead of VEP : "Vocabulary Enhancment Issue", instead 
of Vocabulary Enhancment Proposal   : The issue will be centered on a 
rationale and not on a single term. Some discussions have shown that a 
term can be preferred to another one with the same rationale and 
definition. A term can also become the head term of a whole hierachy 
during the discussion

For example the "VEP" I proposed on May the 22nd at 8:40 UTC could 
become the  "VEI" written as below. rationale will come first and 
prposed Alternative terms and possible child terms belong to the same 
VEI. The end of the process would be to converge on one single hierarchy 
of terms.

       2 ) for the  same reason (incomplete discussion) "Preliminary" 
terms should not be set in the "official" vocabulary list even with the 
"preliminary" tag. Examples using those terms should be provided in 
prototype services or realistic example files.

Cheers

François


VEI-006

Vocabulary:http://ivoa.net/rdf/datalink/core
Author: François Bonnarel
Date: 2020_05-22
Supercedes: VEI-001

Rationale:
     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.
     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 ....
Main New Term proposal: counterpart
Action: Addition
Label: counterpart dataproduct
Description: Data products  that are related to #this for various 
interpretation purposes.

Used-in:
      various SVO ConeSearch services (Cortesy Carlos Rodrigo / SVO )

       CATlib spectral library 
(http://svo2.cab.inta-csic.es/vocats/v2/catlib/)

      ----> Datalink example : 
http://svo2.cab.inta-csic.es/vocats/v2/catlib/dl.php?ID=BD-+01+2582

       MILES spectral library ( 
http://svo2.cab.inta-csic.es/vocats/v3/miles/ )

        ---> DataLink example 
(http://svo2.cab.inta-csic.es/vocats/v3/miles/dl.php?ID=HD102634)

      Could be used by VizieR for their "associated data" in the future

Alternate proposed term : associated-data

Alternate proposed term : see-also

Alternate proposed term : compared-to

Possible Child term : #isObservationOf / in case #this is a source and  
we link an observation of the source

Possible Child term : #contains / in case the source is contained in the 
linked dataset

Possible Child term : #followup / in case the #this observation dataset 
is repeated at later time

Possible Child term : #cross-associated / in cas the two sides of the 
DataLink are cross associated.

Discussion:

      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.

       The original proposed term was #associated-data borrowed to 
VizieR (VEP-001). This one was considered too vague.