| |
| META TOPICPARENT |
name="IvoaTCG" |
TCG Meeting (online) - April 7 2025 @ 21:00 UTC |
|
<
< | |
>
> |
|
| | |
|
<
< | |
>
> |
- Attendees : Marco, Tom, Adrian, André, Gus, Baptiste, Francesca, Gilles, Grégory, Janet, Jesus, JJ, Joshua, Mark CD, Mark K, Markus, Pierre F, Renaud, Sara, Steve, Sébastien, Tamara, Tess
|
| |
|
|
<
< | |
>
> | Actions: |
|
>
> |
- Marco: Start update to DocStd with Markus and appropriate group regarding errata and other known issues.
- All (for Interop planning):
|
| | Agenda
- (standing item): documents on track
- RFC
- VOResource-1.2 - approved 2025-04-06
|
|
>
> |
-
-
-
- This is approved, buy more feedback came in during the exec approval. That is not the normal process, but we don't want to ignore the input, so proposed to have a rapid-turnaround update and release for 1.3 limited only to the late feedback.
- Markus: One point was "why do you only allow DOIs as alt identifiers", so maybe not worth a release. A couple minor points being addressed in a PR address some other minor points. A response to other comments explaining why documentation changes are not needed should complete the updates.
- Tom: Can we find a way to quickly release 1,2 now as voted on and approved, then quickly release a 1.2.1 in an erratum-like process?
- Markus: Given tagging and version control capabilities we have, we could release new version instead of errata. Maybe just bake in the errata but don't bother with the minor rev.
- JJ, Do the errata not get baked into a new copy of the doc? Why not?
- Markus: We didn't have the infrastructure for that, but with ivoatex and github we do now.
- Conclusion: Let's just notify exec of the new updates and ask for reapproval. Updates to DocStd to bake in errata to the doc can happen at a comfortable pace. Marco to take the lead.
|
| |
-
-
- VOEvent-2.1 - status check
|
|
<
< | |
>
> | |
| |
|
|
<
< | |
>
> |
-
- RFC Template has been updated. Please start from there with new RFCs.
|
|
>
> | |
| |
- June Interop planning
- who is planning to be there in person/remotely?
|
|
>
> |
-
-
- Please notify Marco, Francesca, Tom of your attendance and whether it is in-person, especially for Sunday.
- On the exec, we have heard that Marco/INAF will attend, ESAC will send some, China will send 2. CDS will not send anyone, and probably not much from France.
- Please register as soon as possible. Will send a reminder pretty soon but not right away.
- Some people will only attend a subset of sessions. Send Marco requests for specific requests for remote attendance of specific sessions.
|
| | |
|
>
> |
-
-
-
- This general call for abstracts is new based on feedback from the last meeting to make the call for participation a little more open.
- Please send out a call for participation to your groups.
|
| | |
|
<
< | |
>
> |
-
-
- Add planning notes, session requests, etc. here as it comes up so that we can start drafting a program.
|
|
>
> |
-
-
- Local and CSP will be combined plenary dealing with NASA missions and data challenges.
- DM will request at least 2 sessions
- DAL, probably 2
|
| |
- Data Models organisations
- open discussion (based on Mark CD report at the last TCG)
|
|
>
> |
-
- Mark- Two main options:
- Take the approach of building block models (that are not necessarily useful on their own), what are the implications to documents, maintenance, etc.
- Use case based models. They may overlap quite a bit.
- Marco: This relates also to the questions about what constitutes validators and interoperable implmentations
- Markus: Favors modular approach, and implementations are easier with PyVO
- Mark: PyVO and Laurent's work really help with the implementations, but also relied on quite a bit of work and help.
- Gilles: Many times I just need a small part of the model. This was the idea of MANGO
- Adrian: Parallel with s/w dev where you want to separate out different pieces. With s/w/dev we have tools and so on to test the impacts of changes throughout the dependency chain. How do we handle that with standards?
- Mark: Good analogy.
- Marco: Maybe this brings up a broader discussion about RFC processes...
|
| |
- Other ongoing activities / Open topics
- Major version transitioning in Registry
- astronet.ru publishing registry
|
|
>
> |
-
-
- Need to wait a few more months
|
| | |
|
>
> | |
| |
-
- statistics on clients (agents) for TAP (and other protocols): OPS/DAL/Apps
|
|
<
< | |
>
> | |
|
>
> |
-
-
- Name change can be handled by admin at ivoadoc, but requires stopping mail servers for part of a day.
|
| |
-
- IVOA static website rebuilding
|
|
>
> |
-
-
- Before interop, the new website will replace the old one
|
| |
- AOB
- Date for the next TCG vconf
|
|
<
< |
-
- proposed: -- 5-7 May 2025 @ 13:00 UTC -- consolidate topic and evaluate schedule status, after Exec vconf & plan topics for the in person TCG
|
>
> |
-
- proposed: -- 5-7 May 2025 @ 13:00 UTC -- consolidate topic and evaluate schedule status, after Exec vconf & plan topics for the in person TCG
|
|
>
> |
-
-
- May 5 would not be good for some.
- Pencil in Tuesday, May 6. Mention conflicts via e-mail if needed.
|
| |
-
- and the subsequent *21-23 May 2025 @ 20 UTC° IF NEEDED: finalise program
|
|
<
< |
|
| | <--
--> |
