May 2020 IVOA Interop Meeting - Annotations of light curves using VOTable

• When - Tuesday May 05 2020 15:00 UTC
• Where - Zoom https://zoom.us/j/97011177855?pwd=T2F6UU5mZUEvaVg3WjlIWFM3My9BUT09

• Speaker - AdaNebot
• Moderator - DaveMorris

Live discussion document on this EtherPad will be edited and transferred to this wiki page after the meeting is over.

The current version of the TimeSeries note

The document source in GitHub.

Purpose of the Note

• How could the proposed annotation help interoperability?
  • it could allow to combine photometry in same / different filters / missions to help study / classify astronomical sources
  • it could allow to find information of the filter
  • it could allow to find time series in the VO

Topics to discuss

• Do we need to TAG a VOTable Document?
  • Do applications need to know an annotation is consistent with what the Note is specifying?
  • Does it help applications to have a TAG pointing to the document? if so, how?

• Do we want to generalise to annotating other type of time series data?
  • What about radial velocities, or time series of positions?
  • Do we want to tackle this already in the same note or would TIMESYS suffice for now?

• How do we annotate a table with multiple filters in the same column?
  • ForeignKey to reference rows VS several TABLES?
  • ForeignKey or specific usage of GROUPs and double referencing?

• How does an application know this is a timeseries? Usage of simple utypes
  • Inherit utypes from Obscore: dataproduct_type and dataproduct_subtype?
  • If so, where do they go? Global property of VOTable, a RESOURCE or aTABLE?