<!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, but
here are my 2 cents on the questions raised<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> a ) DAL at IRSA :</div>
<div class="moz-cite-prefix"> - in Obscore there is a
distinction between "observation" identified by obs_id and the
individual unit "dataset" identified by obs_publisher_did</div>
<div class="moz-cite-prefix">This allows to group by a common obs_id
several datasets considered to belong to the same "observation".
The definition of what is an observation is actually provider
dependent. SO in the mapping with CAOM I guess that planeid is
more aligned with obs_publisher_did and the dataset concept.<br>
</div>
<div class="moz-cite-prefix"> - for "fast" DataLink as far as
I understand the question, the ID parameter in the DataLink
service is not required to be obs_publisher_did, so any more
direct index to the CAOM artifact table can be used there. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> b ) How should ObsTAP+DataLink
provide options to retrieve the same product from multiple
locations (including cloud)?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"> - prefered provider : the
DataLink access is not required to be given by the access_url
FIELD (or equivalent) in a data discovery response. It can be
provided through a DataLink service descriptor as a secondary
RESOURCE in the respeonse. In that case the access_url can provide
direct link to the preferred provider. <br>
</div>
<div class="moz-cite-prefix"> - multi provider issue :
with the current standard, I think providing the provider tag in
the local_semantics is the "less bad" solution if not the better.
local_semantics is a free text FIELD, but should repeat the same
strings for different datasets in the main service in order to
identify related or similar raws in the DataLink response. So
something like</div>
<div class="moz-cite-prefix"> ID = id1<br>
</div>
<div class="moz-cite-prefix"> semantics :
#this</div>
<div class="moz-cite-prefix"> content_type
: application/fits</div>
<div class="moz-cite-prefix">
content_qualifier : image</div>
<div class="moz-cite-prefix">
local_semantics : aws</div>
<div class="moz-cite-prefix"> ............<br>
</div>
<div class="moz-cite-prefix"> ID = id1</div>
<div class="moz-cite-prefix"> semantics :
#this <br>
</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">
content_type : application/fits</div>
<div class="moz-cite-prefix">
content_qualifier : image</div>
<div class="moz-cite-prefix">
local_semantics : google</div>
<div class="moz-cite-prefix">
.............</div>
<div class="moz-cite-prefix"> ID = id1</div>
<div class="moz-cite-prefix"> semantics :
#progenitor</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">
content_type : application/fits</div>
<div class="moz-cite-prefix">
content_qualifier : cube<br>
</div>
<div class="moz-cite-prefix">
local_semantics : aws</div>
</div>
</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">
.............</div>
<div class="moz-cite-prefix"> ID = id1</div>
<div class="moz-cite-prefix"> semantics :
#progenitor</div>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">
content_type : application/fits</div>
<div class="moz-cite-prefix">
content_qualifier : cube<br>
</div>
<div class="moz-cite-prefix">
local_semantics : google <br>
</div>
<div class="moz-cite-prefix">
.............<br>
ID = id1<br>
semantics : #progenitor<br>
content_type : hdf5<br>
content_qualifier : cube<br>
local_semantics : aws<br>
.............<br>
ID = id1<br>
semantics : #progenitor<br>
content_type : hdf5<br>
content_qualifier : cube<br>
local_semantics : google <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">and then the same kind of answer
for ID = id2</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">will allow the client : to find out
all accesses to the full (image ) fits format dataset served
by aws (or google or ...)</div>
<div class="moz-cite-prefix"> to
find out all accesses to the (cube) progenitor in fits (or
hdf5) served by google (or aws ...)<br>
</div>
<div class="moz-cite-prefix">
etc....</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Cheers</div>
<div class="moz-cite-prefix">François<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
</div>
</div>
<div class="moz-cite-prefix"> <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 09/12/2024 à 11:10, Grégory Mantelet
via dal a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:32149a04-f222-41e4-91be-218aa12786fb@astro.unistra.fr">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Dear DAL members,<br>
<br>
Here is an announcement for the next DAL Running Meeting.<br>
<br>
Anyone who recently attended the DAL session in Malta may remember
the first<br>
talks given by Anastasia Laity (<a
href="https://wiki.ivoa.net/internal/IVOA/InterOpNov2024DAL/DAL_at_IRSA_Laity.pdf"
moz-do-not-send="true">pdf</a>) and Tess Jaffe (<a
href="https://wiki.ivoa.net/internal/IVOA/InterOpNov2024DAL/NAVO_cloud_DataLink_202411_interop.pdf"
moz-do-not-send="true">pdf</a>). They raise an interesting<br>
question about ways to convey multiple locations for a single
product provided<br>
through Datalink. This question was raised and Tess suggested some
solutions ;<br>
see <a
href="https://wiki.ivoa.net/internal/IVOA/InterOpNov2024DAL/IVOA_Nov24_DAL.pdf"
moz-do-not-send="true">session notes</a>. Unfortunately we did
not have a lot of time for discussions.<br>
Hence this DAL Running Meeting.<br>
<br>
If you are interested by this question, here is the information
about this<br>
Running Meeting:<br>
<br>
<blockquote><font size="5" face="monospace"><b>Date :</b></font><font
face="monospace"> </font>
<style type="text/css"></style><font size="5" face="monospace">Dec
11, 2024<br>
<b>Time :</b> 04:00 PM UTC<br>
<b>Duration:</b> 1 hour<br>
<b>Location:</b> <a
href="https://cnrs.zoom.us/j/92095660540?pwd=3dAHll6Na9X71S8HAgUnNtxzjo3r9v.1"
class="moz-txt-link-freetext" moz-do-not-send="true">https://cnrs.zoom.us/j/92095660540?pwd=3dAHll6Na9X71S8HAgUnNtxzjo3r9v.1</a><br>
</font><font size="4" face="monospace"><i><b>Meeting
ID:</b></i></font><font size="4" face="monospace"><i> 920
9566 0540</i></font><font size="5" face="monospace"><br>
</font><font size="4" face="monospace"><b><i>Passcode</i></b></font><font
size="4" face="monospace"><b><i> :</i></b><i> sjM0h4</i></font><font
size="4" face="monospace"> </font><br>
</blockquote>
<br>
Cheers,<br>
Grégory Mantelet & Joshua Fraustro<br>
</blockquote>
<p><br>
</p>
</body>
</html>