ACTION-F0419-1: MM - Access technical setup of UCD maintenance doc
ACTOIN-F0419-2: JE - Add Review of Provenance at TCG Interop face to face meeting
ACTION-F0419-3 ML - Send TCG page or links to Provenanance Goals and Use Cases for F2F prep
ACTION-F0419-4 JE - Add Data Collections Note to TCG agenda for Paris F2F, 10 minutes
Previous Actions:
OPEN/WORKING
ACTION-F0518-3: FG - Ensure that the important IVOA standards are in the RDA registry of standards (Note added 11/18 - DCP?/Registry?). OPEN
ACTION-F0518-4: MCD - Produce documentation on how the models relate and how to get started with certain use cases. WORKING
ACTION-F0518-8: DM/PD - Prototype hosting a document standard and issue tracking in GitHub. WORKING
<a rel="nofollow" href="https://wiki.ivoa.net/twiki/bin/edit/IVOA/ActionT0219?topicparent=IVOA.IvoaTCG-2019-02-05;nowysiwyg=0" title="ActionT0219 (this topic does not yet exist; you can create it)">ActionT0219</a>-5: PD/JE - kick off the Architecture doc effort effort and distribute tasks to team - WORKING
ActionT2019-6: PD/JE: Ask DOC to transfer links to new Publishing on the VO doc when time is right - OPEN
DONE
ActionT0219-1: JE/PD action to review and suggest updates to TCG charter, then follow through. DONE
Reviewed charter; noted several aspects of process called out; will work toward them and suggest updates if needed
Plan to map tasks from Roadmap in each WG/IG to major goals of each group. Tie to CSP goals. Are more CSP goals needed or help with current goals??
ActionT0219-2: PD - send email to review and consider ObsCore/STC errata at next telecon - DONE
ActionT0219-3: MM - Ask Giulia to remove VOEvent/VODML from active column - DONE
ActionT0219-4: TD - Identify people to make VOEvent changes and rewrite VoEventRegExt, - DONE
Status:
WG/Apps (TD/RD)
Status:
WG/DAL (MM/JD)
Status:
Issues: (from Feb telecon - needs update)
Service Weather report on DAL protocol "SHOULD"s: collected data providers view, need to report (here, e.g.)
From discussion with data providers (just after the College Park interop) the view that turned out is that there's not really the need to act upon the SHOULD-s validation warnings. This is because those SHOULDs can be related to information good to have but maybe not available (especially for old datasets), or because it brings in a feature that is not felt important to the provider. In the end the feeling is that working on those warnings as something to clean from the operational point of view could not be the right approach and modifying existing standards o demote shoulds looks not a good idea. This does not mean validation is not useful, but feature-usage driven checks can show a different picture. The Service Weather report outcome looks like a place to start a DAL/Ops discussion for a report that looks more like a Registry/Ops driven one.
polygon CCW: modelling seems solved (errata in other WGs), data providers side, how to proceed?
initial DAL email didn'twork, turned out in a region discussion turmoil
WG/DM (MCD/LM)
Status:
Errata:
ObsCore-1.1 and STC-1.33 pages created and discussed.. ready for TCG vote.
Coords:
Updated document with variuos feedback items; delivered to WG and doc repository (Mar 21)
Vocabularies installed to semantics workspace.. Semantics group working discussion/review of content with TDIG/SSIG
Example serializations being updated/expanded to newest content.
Transform:
Extensive review/iteration with author list to cover all the requirements.
Folded in the enhanced requirements descriptions noted for Coords model.
'Final' version delivered to author list (Apr); expect this to go to WG and repository in the next couple weeks.
Meas:
Updated model content to current Coords model state
Simplified the levels of abstraction to reduce #boxes
Working document: have general structure, need to add descriptive content to model and process (~1wk job) (by end April).
Prov:
The situation does not allow to define a clear timeline
A compromise model has been proposed by the chair(s) in order to reach a consensus among the authors
A PR#2 document based on that compromise is still discussed.
Our goal remain to open the REC page as soon as possible.
SSDL-2.0
WG response to Feb. drop has been quiet.
working vo-dml processing/validation using current scripts
ready for PR/RFC?
Time Domain
promised new Mapping serializations of all their example files; STILL NOT DONE (resource issue)
An EduIG session is under preparation and a plenary talk is confirmed
Issues:
More people are encouraged to attend to the Interop.
IG/KDD (KP/MG)
Status:
Issues:
IG/Ops (TM/MT)
Status:
Issues:
IG/Solar System (BC/SJ)
Status:
Issues:
IG/Theory (CR)
Status:
Issues:
IG/TDIG (AN/DM)
Status:
Issues: (from Feb telecon - needs update)
Roadmap:
TIMESYS:
Integrated in VOTable1.4
GAVO and VizieR have been collecting metadata for time, and would be ready to use TIMESYS if a Rec.
How to make use of TIMESYS? bring to common frame? Need to developed code to do so.
Time-MOC:
Several hundred T-MOCs already produced by VizieR and user is able to generate them in the beta version of Aladin. * Need to connect to space for fully exploitation. Space-Time-MOC under development and will most likely be shown in Paris.
Generate and add to Mocserver
VOEvents:
Baptiste Cecconi has transformed the doc into an exact tex document, and is part of the editors:
Feedback gathered from specific communities (FRBs, SSO, multi-messenger follow-up) points to the need of further evolution of VOEvents.
How do we discover VOEvents? science driven and/or wavelength driven specification of VOEvents to be able to do TAP like queries?