[Even list/ event ] stabilizing the name of a data set containing lists of events

[Mireille LOUYS]

Dear all ,
There are currently differences in the way we consider data products 
containing lists of events in the VO ecosystem .
This came up in a discussion started about VO high energy data sets last 
june.

1- ObsCore :
reference document : https://ivoa.net/documents/ObsCore/20170509/index.html
dataproduct_type = event
definition :

  *

    event An event-counting (e.g. X-ray or other high energy) dataset of
    some sort. Typically this is instrumental data, i.e., "event data".
    An event dataset is often a complex object containing multiple files
    or other substructures. An event dataset may contain data with
    spatial, spectral, and time information for each measured event,
    although the spectral resolution (energy) is sometimes limited.
    Event data may be used to produce higher level data products such as
    images or spectra.

comment= considered as a collection of detections with time, space, 
spectral, polarimetry, etc.  information .
should be better named '/eventlist/' to highlight that it is multiple .

2- IVOA Vocabularies:
reference document 
:https://www.ivoa.net/rdf/product-type/2023-06-26/product-type.html
definition :

event (Preliminary) 	Event 	A collection of some sort of observed 
events, such as high-energy particles observed. A row in an event list 
is typically characterised by spatial, spectral, and time information. 
#temporally-resolved-dataset 
<https://www.ivoa.net/rdf/product-type/2023-06-26/product-type.html#temporally-resolved-dataset> 



comment: this definition also considers a collection of single events. 
Similar to Obscore event data set.

3- EPNCore :
reference document : 
https://ivoa.net/documents/EPNTAP/20220822/REC-EPNTAP-2.0.html#tth_sEc2.1.2
definition :

  * *ev*(= event): introduces individual VOevents formatted according to
    IVOA standard (or possibly events with other formatting).
    Characteristics are provided via the event_* parameters

comment:
     considered as one individual event , with astronomical context 
information (ex: FRB,...), propagated in an alert system.
     currently the VOevent format is taken into account.
EPN can gather several event in a catalog of items , each of them beeing 
an event.

For clarity,  we need to homogeneize the terms and  definition:
so my proposal is to :

- update Obscore to clearly use the term  'eventlist' instead of event , 
as well as the /product-type/ IVOA Vocabulary.
- change the label 'event' to 'eventlist'  in the product-type vocabulary
- introduce  'event'  in the IVOA product-type vocabulary as defined in 
EPN Core.


Eager to read your comments about this proposal.

I'll be on vacation next week and wish you a pleasant summer time.
Cheers , Mireille


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20230722/fed4951c/attachment.htm>