[Radioig] Extensions and next step of Obscore

BONNAREL FRANCOIS gmail francois.bonnarel at gmail.com
Wed Jun 11 15:49:23 CEST 2025


Dear Markus, all
Le 11/06/2025 à 11:31, Markus Demleitner via dal a écrit :
> 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@?

My list was based on the participants to the ObsCore Extensions plenary.

But as you want.

>
> 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
> (essential

As the "historical" editor of the radio extension document, I have 
nothing against this document to be a REC.

The idea was that the status of endorsed note could fasten the adoption 
of this spec.

But I let that in the  hands of the two other editors (Mark K and 
Mireille) and the TCG

> ly: 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.
Not DAL, DM (that was the group where ObsCORE was ported)
>
>>   * 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.

I think Mireille and Pat were discussing how to push that.

I may not be up to date on the exact status

Cheers

François

>
>>   * 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
>



More information about the Radioig mailing list