You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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 3.1.3) so the values could be data file types (e.g. application/fits) or they could be the DataLink [8] MIME type."
The initial part of the sentence mentions "response format(s)", which that greatly overlaps,
and generates confusion (at least in my mind), with the following DALI specification:
"The RESPONSEFORMAT parameter is used so the client can specify the format of the response (e.g. the output of the job)."
The SIA FORMAT and the DALI RESPONSEFORMAT are two different things, and I think that should be better clarified
in the text of the next SIA version. Could that be done?
The text was updated successfully, but these errors were encountered:
Bonnarel
changed the title
Possible confusion betwwen FORMAT and RESPONSEFORMAT parameter
Possible confusion between FORMAT and RESPONSEFORMAT parameter
May 8, 2020
Alberto Micol 2019/03/&4 :
SIA specifies:
"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 3.1.3) so the values could be data file types (e.g. application/fits) or they could be the DataLink [8] MIME type."
The initial part of the sentence mentions "response format(s)", which that greatly overlaps,
and generates confusion (at least in my mind), with the following DALI specification:
"The RESPONSEFORMAT parameter is used so the client can specify the format of the response (e.g. the output of the job)."
The SIA FORMAT and the DALI RESPONSEFORMAT are two different things, and I think that should be better clarified
in the text of the next SIA version. Could that be done?
The text was updated successfully, but these errors were encountered: