Radio extension discussion on github.

[BONNAREL FRANCOIS gmail]

Dear all,
Since this email was written, there has been a lot of discussion on the 
various ObsCore extensions and their status with respect the root
ObsCore. In these conditions the Radio extension may become a simple 
endorsed note, before all extensiosn reach their final status.
In these conditions I propose a more conservative provisional solution 
for the extension registration
See https://github.com/ivoa-std/ObsCoreExtensionForRadioData/issues/73 
for discussion
and PR #71 for the proposal (artifact 
https://github.com/ivoa-std/ObsCoreExtensionForRadioData/actions/runs/13605851847 
for the pdf).
Cheers
François
Le 21/01/2025 à 00:11, BONNAREL FRANCOIS gmail a écrit :
>
>
>
>
> Dear all,
>
>    This email to mention there is currently some discussion about how 
> to register the radio extension in a TAP service.
>
>    Markus thinks that it can be done by a specific standardID utype on 
> the table with the radio extension attribute.
>
>    I prefer to allow users to discover that a specific profile of 
> ObsCore (containing the extension attributes an the root attributes) 
> is present in the service by setting a specfic standardID on a table 
> containing all the attributes of the profile
>
>   This table would be empty and only there to announce the list of 
> available attributes. The queries will in practice be done by natural 
> join on root ObsCore table and extension-only table.
>
>
> https://github.com/ivoa-std/ObsCoreExtensionForRadioData/issues/73
>
>
> Cheers
>
> François
>
>