<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Paul,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Whether or not it's a session talk, I'd love to help MAST coordinate with you and Grégory on this.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We (MAST, but also myself and Joshua directly) are indeed working from a fork of VOLLT, using only the ADQL library portion. The library runs only ADQL-to-database-specific query translation in a Java microservice in our otherwise Python-based TAP stack. No
matter where the canonical upstream code lives, we'll probably have to keep working from a fork in the medium term (until we finish migrating away from MAST-specific spatial infrastructure in classes we include) but having a common base to work from separate
from the other included libraries would be an improvement. I do like the idea of a codebase used across so many archives and integrated into reference implementations of IVOA standards having a home there if the primary author and github org maintainers support
it.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof">Cheers,</div>
<div class="elementToProof">--Tessa</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="display: inline-block; width: 98%;">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b>From:</b> interop on behalf of Paul Harrison via interop<br>
<b>Sent:</b> Thursday, April 2, 2026 3:34 AM<br>
<b>To:</b> MANTELET Grégory (OBAS); Joshua Fraustro<br>
<b>Cc:</b> DAL WG; interop@ivoa.net<br>
<b>Subject:</b> Re: Call for contributions to DAL WG session at June 2026 Interop
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div>Hi,</div>
<div><br>
</div>
<div>I am not sure if this is absolutely worth a talk, but it concerns you both - my group and I believe MAST have been working off a fork of the VOLLT library with the principal aim of using the most recent ADQLLib - which has been living off on a branch in
the main repository - I have created <a href="https://github.com/Javastro/ADQLLib" target="_blank" id="OWAcca6b26b-0e48-28c6-0409-0dc0db57bc34" class="OWAAutoLink" rel="noopener noreferrer" data-auth="NotApplicable">
https://github.com/Javastro/ADQLLib</a> which has merged the branch and done a few minor cleanups, and most importantly deleted the UWS and TAP code to allow ADQLLib to evolve at its own pace - I would like to propose moving this to the
<a href="https://github.com/ivoa" target="_blank" id="OWAeb36f514-1c10-24dd-5f7e-9934eca11651" class="OWAAutoLink" rel="noopener noreferrer" data-auth="NotApplicable">
https://github.com/ivoa</a> organisation to allow greater collaboration and participation. There are some open questions such as</div>
<div><br>
</div>
<div>* publishing to a maven repository</div>
<div>* moving any existing documentation to be within the same repository.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Paul.</div>
<div><br>
</div>
<blockquote>
<div>On 1 Apr 2026, at 13:57, Gregory MANTELET via interop <interop@ivoa.net> wrote:</div>
<div><br>
</div>
<p style="margin-top: 1em; margin-bottom: 1em;">Dear DAL and IVOA members,</p>
<p style="margin-top: 1em; margin-bottom: 1em;">The <a href="https://urldefense.com/v3/__https://indico.ict.inaf.it/event/3454/overview__;!!PDiH4ENfjr2_Jw!CuyXtJeX_qFTXMbstyNvxhqj4KVkHm0l7pUIo_PXTeo-rWdlpvVJ2N6J_FZtQBIeSg4qK4Kmk9A2ixG7w2afq3j_$" target="_blank" id="OWAe732c761-542a-5175-f6fd-dedc5b986185" class="x_external-link OWAAutoLink" rel="noopener nofollow noreferrer" style="margin-top: 0px; margin-bottom: 0px;" data-auth="NotApplicable" data-tooltip-position="top">
June IVOA Interoperability Meeting [indico.ict.inaf.it]</a> will take place in Strasbourg (France) from the 8th to the 12th of June 2026. Remote attendance is supported.</p>
<p style="margin-top: 1em; margin-bottom: 1em;">As a reminder, if you want to participate to this meeting, do not forget to
<a href="https://urldefense.com/v3/__https://indico.ict.inaf.it/event/3454/registrations/1551/__;!!PDiH4ENfjr2_Jw!CuyXtJeX_qFTXMbstyNvxhqj4KVkHm0l7pUIo_PXTeo-rWdlpvVJ2N6J_FZtQBIeSg4qK4Kmk9A2ixG7w8dmueAo$" target="_blank" id="OWA28a4db47-db2d-caea-afd6-38d29865d196" class="x_external-link OWAAutoLink" rel="noopener nofollow noreferrer" style="margin-top: 0px; margin-bottom: 0px;" data-auth="NotApplicable" data-tooltip-position="top">
register on the meeting website [indico.ict.inaf.it]</a> (even you plan to attend remotely).</p>
<p style="margin-top: 1em; margin-bottom: 1em;">With this email, Joshua and I invite you to contribute to DAL sessions with a DAL related topic.</p>
<blockquote>
<p style="margin-top: 1em; margin-bottom: 1em;"><i>DAL stands for Data Access Layer. This Working Group aims to define standards and protocols to access data in an interoperable way. Here are few examples of well-known DAL standards: (Simple) Cone Search, SIA
(image access), SSA (spectra access), TAP (Table Access Protocol) and ADQL (SQL-like language to query a database). The full list of DAL standards is available on the
</i><a href="https://urldefense.com/v3/__https://www.ivoa.net/documents/__;!!PDiH4ENfjr2_Jw!CuyXtJeX_qFTXMbstyNvxhqj4KVkHm0l7pUIo_PXTeo-rWdlpvVJ2N6J_FZtQBIeSg4qK4Kmk9A2ixG7wwlkDDit$" target="_blank" id="OWAdfa1750f-fc9c-8026-fa20-b62b47f4912e" class="x_external-link OWAAutoLink" rel="noopener nofollow noreferrer" style="margin-top: 0px; margin-bottom: 0px;" data-auth="NotApplicable" data-tooltip-position="top"><i>IVOA
Documents page [ivoa.net]</i></a><i>.</i></p>
</blockquote>
<p style="margin-top: 1em; margin-bottom: 1em;">During this interop., you can contribute, remotely or in-person, with a talk presenting implementations, sharing your experience as user, presenting and discussing progress on a DAL standards, or presenting use-cases.</p>
<p style="margin-top: 1em; margin-bottom: 1em;">If you are interested, please send your contribution to
<a href="mailto:gregory.mantelet@astro.unistra.fr" id="OWA0bde1cde-a3f7-0ffa-f453-4448bef54321" class="x_external-link x_moz-txt-link-freetext OWAAutoLink" style="margin-top: 0px; margin-bottom: 0px;" data-tooltip-position="top">
gregory.mantelet@astro.unistra.fr</a> and <a href="mailto:jfraustro@stsci.edu" id="OWA7fb0d6de-9d74-894d-76df-192b9ee351e7" class="x_external-link x_moz-txt-link-freetext OWAAutoLink" style="margin-top: 0px; margin-bottom: 0px;" data-tooltip-position="top">
jfraustro@stsci.edu</a> with:</p>
<ul>
<li>a speaker name,</li><li>a title,</li><li>ideally an abstract.</li></ul>
<p style="margin-top: 1em; margin-bottom: 1em;">If you are unsure about the suitability of a talk, or are a first time contributor, please get in contact with us.</p>
<p style="margin-top: 1em; margin-bottom: 1em;">Cheers,<br>
Grégory Mantelet and Joshua Fraustro</p>
<div><br>
</div>
</blockquote>
<div><br>
</div>
</body>
</html>