<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Dear all,</div>
<div class="moz-cite-prefix">I will not attend the meeting today.
But as a still-editor of the Radio extension I will add my
personal 2 cents on the points of Obscore extension</div>
<div class="moz-cite-prefix">This si not fully coordinated with the
two other editors (Mark K and Mireille)<br>
</div>
<div class="moz-cite-prefix">Le 12/02/2025 à 15:15, Mathieu
Servillat via dm a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:14541122-236d-448e-976d-34933d937417@obspm.fr">Dear
DMers,
<br>
<br>
Sorry for the wrong time conversion, we agreed to meet at **3pm
UTC**, (4pm CET, 10am EST)
<br>
<br>
Zoom link:
<br>
<a class="moz-txt-link-freetext" href="https://cnrs.zoom.us/j/96082681157?pwd=XAjMGFi22MQaObELHF7laN5J9qibmm.1">https://cnrs.zoom.us/j/96082681157?pwd=XAjMGFi22MQaObELHF7laN5J9qibmm.1</a>
<br>
<br>
Probable topics are: review of actions, ObsCore extension
discussion, </blockquote>
<p>For the radio one, I start by copy/pasting the RadioIG charter
now 5 years old</p>
<p>
<blockquote type="cite">
<p>
<strong>Charter:</strong>
</p>
<p>
The group shall define requirements for the representation of
radio astronomy data in the VO through:
</p>
<p> </p>
<ul>
<li> development of use cases for data discovery, access and
visualization
</li>
<li> identification of metadata concepts needed by radio
astronomy data that are not currently supported by the VO
</li>
<li> the group will provide a well identified point of contact
for radio projects with IVOA, and actively encourage their
use of VO standards and protocols
</li>
<li> the group will organize sessions focused on radio
astronomy data at IVOA meetings
</li>
</ul>
</blockquote>
I think the radioIG group basically succeeded in providing point 2
with the extension PR and the prototypes and implementation at
JIVE. I also appreciate that last version of CAOM integrated most
of the extension attributes in its own scheme in order that
ObsCOre + extension will remain a flat discovery-intended view on
top of it.</p>
<p>The radio extension proposal has been regularly discussed not
only in RIG sessions but also in DM sessions.<br>
</p>
<p>On the other side I understand that now people fill the need to
rework ObsCore and that this upgrade can rearrange the limit
between root Obscore and the radio extension</p>
<p>(not to speak about the time and Heig ones). I think the final
perspective may something like the vision expressed by JJ in a
recent email : a global metadata model and various specific and
one root generic subparts. <br>
</p>
<p>My main concern is that achieving this will take a lot of time
(22 years in the VO showed me that no new project achieves fast,
whatever the intentions are at the beginning. Some unsuspected
aspects always appear in the process). So what is the status of
the radio extension in the mean time ? I think some projects are
ready to use them. Howgive can we give these attributes a
normative status <br>
</p>
<p>As some of you already know my compromise proposal is to publish
the draft spec as an "endorsed note" during the time Obscore 1.2
is discussed. <br>
</p>
<p>Cheers</p>
<p>François<br>
</p>
<blockquote type="cite"
cite="mid:14541122-236d-448e-976d-34933d937417@obspm.fr">CAOM
integration update, MANGO (AOB: Spectrum Errata).
<br>
<br>
Best regards,
<br>
<br>
Mathieu & Mark
<br>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>