32. Assign clear governance to each NVS collection about argovocabs_meetings HOT 3 CLOSED

@mscanderbeg is now set up on the NVS Vocabulary Editor to manage the Trajectory tables:

• R15
• RMC
• RTV

@catsch is now set up on the NVS Vocabulary Editor to manage the parameter codes table:

• R03

@RomainCancouet and @catsch are now set up on the NVS Vocabulary Editor to manage the Configuration parameter names (Romain core, Catherine bgc):

• R18

@tcarval, @MKrieger29, @ClareBellingham and @roswri are now set up on the NVS Vocabulary Editor to manage the Argo reference tables:

• R01
• RR2
• RD2
• RP2
• R04
• R05
• R06
• R07
• R08
• R09
• R10
• R11
• R12
• R13
• R16
• R19
• R20
• R21
• R22
• R23
• R24
• R25
• R26
• R27
• R28 (WIP)
• R40 (PI_NAME - WIP)

from argovocabs_meetings.

Following the latest AVTT meeting (https://github.com/nvs-vocabs/ArgoVocabs_Meetings/blob/main/AVTT_meetings/2023-05-30-agenda.md), an action on @vpaba to resume work with @nvs-vocabs/oceanops started in 2022 around cross-domain vocabularies.

For reference, information on the 2022 series of meetings with OceanOps can be found in files named 'Argo_NVS_OceanOps…' here: https://github.com/nvs-vocabs/ArgoVocabs_Meetings/tree/main/telecons.

The AVTT group suggested that any new cross-domain vocabulary created should have OceanOps as governance, if OceanOps agrees.

A new meeting with OceanOps is being planned in the next few weeks.

from argovocabs_meetings.

The Editors for each Argo NVS collection can be found here: https://github.com/nvs-vocabs/ArgoVocabs/

from argovocabs_meetings.