|
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:
- 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:
- 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)
Issues:
WG/GWS (BM/GT)
Status:
Issues: (from Feb telecon - needs update)
- XML Schema Versioning - issues to be addressed
WG/Registry (ThD/PLS)
Status:
Issues:
WG/Semantics (ML/MD)
Status:
Issues:
IG/Data Curation & Preservation (AS/TJ)
Status:
Issues:
IG/Education (CC/HH)
Status:
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) |
|
< < |
- TIMESYS
- Discussion over "ref" as a mandatory field or optional is now open.
- How to get feedback from preference of data providers?
- Time Series model & serialization
- Dependance on other models slows the process.
- Observed process for other models is not encouraging.
- Understanding the limit between model and serialization is not straight forward. What goes where? Need to see both model and serializations to understand if all the information needed is existing somewhere.
- Need to have some serialization examples based on VO-DML (at least first attempts). Who is doing that?
- Serialization based on utypes: list of utypes needs to be built (last interop some mistakes were found) and shared with the TDIG.
|
> > | 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?
- TimeSeries Models:
- Coords model / feedback given.
- To be VODMLized: PhotDM, Characterisation.
- TimeSeries Serialisation:
- To solve some very common use cases (light-curves and such) we need a minimum of information on the filter system, the ucds are not enough.
|