<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri Light",sans-serif;
color:#1F3763;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="DE" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Many thanks François.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">I think it would be useful to change the text of SIA regarding the FORMAT parameter.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">SIA specifies:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">"The FORMAT parameter specifies response format(s) (the access_format column from the ObsCore [7] data model). This column describes the format of the response from the access_url (see
</span><a href="http://www.ivoa.net/documents/SIA/20151223/REC-SIA-2.0-20151223.html#bkmRefHeading200962138146524"><span lang="EN-US">3.1.3</span></a><span lang="EN-US">) so the values could be data file types (e.g. application/fits) or they could be the DataLink
[8] MIME type."<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The initial part of the sentence mentions "response format(s)", which that greatly overlaps,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">and generates confusion (at least in my mind), with the following DALI specification:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">"The RESPONSEFORMAT parameter is used so the client can specify the format of the response (e.g. the output of the job)."<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The SIA FORMAT and the DALI RESPONSEFORMAT are two different things, and I think that should be better clarified<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">in the text of the next SIA version. Could that be done?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Many thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Alberto<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">François Bonnarel <francois.bonnarel@astro.unistra.fr><br>
<b>Date: </b>Monday, 11. March 2019 at 19:09<br>
<b>To: </b>Alberto Micol <amicol@eso.org>, DAL mailing list <dal@ivoa.net><br>
<b>Subject: </b>Re: SIAv2: FORMAT?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Hi Alberto, all<o:p></o:p></p>
<p>I understand the concern, but the logic of SIAP 2.0 (I instit on .0) is that it is not forcing outputs but only selecting.**<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">SO interprtaion 1 ) is correct. If you ask FORMAt=jpeg and everything is in application/fits you select .... nothing.<br>
<br>
Allowing virtual data in SIAP 2.1 (which I hope tio happen, ASAP) will change the behavior of FORMAT to force the output to be be jpeg.<br>
<br>
My 2 cents<br>
Cheers<br>
François<o:p></o:p></p>
<div>
<p class="MsoNormal">Le 11/03/2019 à 18:56, alberto micol a écrit :<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<h3 style="normal;orphans: 2;widows: 2"><span style="font-size:10.5pt;font-weight:normal">Dear DAL,</span><o:p></o:p></h3>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt">I have a question regarding the FORMAT input parameter described in SIAv2.0:</span><o:p></o:p></p>
</div>
<div>
<h3 style="normal;orphans: 2;widows: 2">2.1.17 FORMAT<o:p></o:p></h3>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
The FORMAT parameter specifies response format(s) (the access_format column from the ObsCore [7] data model). This column describes the format of the response from the access_url (see <a href="http://www.ivoa.net/documents/SIA/20151223/REC-SIA-2.0-20151223.html#bkmRefHeading200962138146524" target="_blank" title="http://www.ivoa.net/documents/SIA/20151223/REC-SIA-2.0-20151223.html#bkmRefHeading200962138146524">3.1.3</a>)
so the values could be data file types (e.g. application/fits) or they could be the DataLink [8] MIME type. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">It is unclear to me how to read that.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I have two possibilities in mind:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">1) The FORMAT input param is used to add a constraint onto the access_format, e.g.:<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
...&FORMAT=application/fits<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
gets translated into a constraint like: <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
SELECT ... WHERE access_format = 'application/fits<o:p></o:p></p>
<div>
<p class="MsoNormal">but that does not seem to have much sense, as some data providers might have decided that access_format in the ObsCore table is always the datalink mime type, delegating and delaying the specification of the correct mime type to datalink. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">In such case, the result of the above query will always be an empty set.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
2) a different way of reading 2.1.17 is that FORMAT determines which access_format will be used in output, that is...<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
if ...&FORMAT=application/fits<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
then the returned votable will contain:<o:p></o:p></p>
<div>
<p class="MsoNormal">access_format=application/fits<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">access_url=the URL to directly download the FITS file (and not a datalink)<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;normal;orphans: 2;widows: 2">
while if FORMAT=application/x-votable+xml;content=datalink<o:p></o:p></p>
<div>
<p class="MsoNormal">then the access_format will be "application/x-votable+xml;content=datalink”<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and the access_url will return the datalink link.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Could you please help me understand the 2.1.17 specification?<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">I would go for interpretation (2) above, but I see that some of you have implemented (1) instead...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">Many thanks in advance,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Alberto<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>