|
META TOPICPARENT |
name="IvoaTCG" |
IVOA TCG Telecon - Tue, 16 Apr 2019 @15:00 UTC
last edit - Apr12 - JE
- Mar 29 - Seeded mtg page - JE
- Apr 03 & 12 - Updated agenda, added to regrets - JE
Attendees
Agenda
- Regrets for not attending: Christophe, Ada, Kai, Mark
- Review Actions (List below)
- Document review
- On Going Recommendation review
- Errata :
- Notes:
- Registry - Discovering Data Collections (Markus)
- IVOA Architecture Document
- WG/IG Status/Issues
- May Interop Planning
- AOB
IVOA TCG Telecon - 15:00 UTC - WebEx info
SystemsTuesda"> Hosted by CXC Data Systems Tuesday, Apr 16, 2019 11:00 am | 2 hours | (UTC-05:00) Eastern Time (US & Canada) Meeting number: 735 581 056 Password: IVOA2019 https://sao.webex.com/sao/j.php?MTID=m72105f006eafd105bdec6238b92fa7f5 Join by phone 1-877-668-4493 Call-in toll-free number (US/Canada) 1-650-479-3208 Call-in toll number (US/Canada) Access code: 735 581 056
Roadmap
Document Submission Logs (since last Interop)
Previous Actions:
- 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. OPEN
- ACTION-F0518-8: DM/PD - Prototype hosting a document standard and issue tracking in GitHub. WORKING
- ActionT0219-1: JE/PD action to review and suggest updates to TCG charter, then follow through
- ActionT0219-2: PD - send email to review and consider ObsCore/STC errata at next telecon
- 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,
- ActionT0219-5: PD/JE - kick off the Architecture doc effort effort and distribute tasks to team
- ActionT2019-6: PD/JE: Ask DOC to transfer links to new Publishing on the VO doc when time is right
New Actions
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.)
- polygon CCW: modelling seems solved (errata in other WGs), data providers side, how to proceed?
WG/DM (MCD/LM)
Status: |