[Heig] Extensions and next step of Obscore

[Markus Demleitner]

Dear Colleagues,

Whoa, that's a wide distribution right there.  May I suggest to
have discussions on the immediate future on radioig@ and heig@, and
the wider future on dm@?

On Fri, Jun 06, 2025 at 12:28:00AM +0200, BONNAREL FRANCOIS gmail via dal wrote:
> My answer (after session) : I see this as a multistep thing.
>
>  *   1 ) Radio extension and maybe others can be published as endorsed
>    notes. They include a description  of how to discover the extension
>    in regsitry and how to join that to Obscore. Take care than Common
>    attributes should have same name and VOTAble attributes and definition

I still don't see any reason why these should be endorsed notes and
not RECs.  They are very clearly in close analogy with Obscore
(essentially: lists of normative columns), and while I give you IGs
cannot do RFCs, that just means there needs to be a sponsoring WG.
Since DAL has done Obscore, so should it sponsor the extensions.

>  * 2 ) ObsCore 1.2 in parallel should have a limited scope and can be
>    developed fast
>
>      * include IVOA product type vocabulary in dataproduct_type FIELD
>
>      * move the discovery of Obscore in registry to the table/schema
>        utype mode in tableset
>
>      * adopt additions and all changes which make consensus
>
>      * describe in a generic way how any kind of extension can be
>        declared and joined to the ObsCore 1.2 root table

Agreed.  Will Mireille be editor?  I'm happy to provide PRs for the
first two of François' items as soon as I get a signal to that
effect.

>  * 3 ) Then take time to have ObsCOre 2.0

Well, let's get 1.2 out of the door first and then see if there's
really anything so fundamentally wrong with obscore 1 that a
breaking change is unavoidable.

Thanks,

            Markus