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

Markus Demleitner msdemlei at ari.uni-heidelberg.de
Mon Jul 24 15:04:55 CEST 2023


Dear DM and Semantics,

On Sat, Jul 22, 2023 at 09:04:19PM +0200, Mireille LOUYS wrote:
> 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've never been a big fan of the word "event" in the obscore
dataproduct_type terms, exactly because, as you say, we'll most
likely have *lists* of events in obscore.

On the other hand, changing class labels in standards (and databases)
is always painful, and if we do it, we need to have a plan for how to
move the installed base.

I've just done an all-VO query for dataproduct_type='event', and of
the registered Obscore services, only two have datasets labeled as
"event":

  ivo://jvo/isas/darts/hitomi/hitomaster_v1

and

  ivo://padc.obspm.he/tap

If these two promise they'll update when we approve an erratum (or
pass obscore 1.2), then changing "event" to "event-list" (I'd prefer
if there was a dash in there) would be ok with me.

As to re-adding "event" designating the concept of a single event
description this time: Aw, you know about my skepticism on creating
concepts before someone wants to use them.  That's particularly true
in this case -- I'd much rather if there weren't a flag day when
"event" changed its meaning in obscore.  Perhaps we can deprecate it
first and then see if, when people actually want to publish, say,
VOEvents in this way, there's a name for it that carries less
historical baggage?

Thanks,

           Markus


More information about the dm mailing list