SODA1.0-Next page.
SODA-1.0 feedback, issues and proposalsOn GitHub: https://github.com/ivoa-std/SODA
meta.ref.url;meta.curation.SODAThis is not a valid UCD both for the, probably, typo of the added .SODA part and the fact that meta.curation identifies a man/organization responsible for the data as per the UCD vocabulary. To remedy the situation we propose here to use meta.id;meta.dataset instead. This achieves:
<PARAM name="POL" ucd="meta.code;phys.polarization" datatype="char" arraysize="*" ''value=""> '<DESCRIPTION>Polarization states to be extracted.</DESCRIPTION> <VALUES> <OPTION>I</OPTION> <OPTION>V</OPTION> </VALUE> </PARAM>My understanding of the VOTable standard is that the correct way should instead be (see the sentence "All three MIN, MAX and OPTION sub-elements store their value corresponding to the minimum, maximum, or ``special value'' in a value attribute." In the paragraph at: http://www.ivoa.net/documents/VOTable/20191021/REC-VOTable-1.4-20191021.html#sec:values ): <PARAM name="POL" ucd="meta.code;phys.polarization" datatype="char" arraysize="*" value=""> <DESCRIPTION>Polarization states to be extracted.</DESCRIPTION> <VALUES> <OPTION value="I"/> <OPTION value="V"/> </VALUE> </PARAM>Alberto was perfectly right !!! This has been fixed with SODA erratum 2 : https://wiki.ivoa.net/twiki/bin/view/IVOA/SODA10Err2
There are proposed subsections for issues #3, #4, #7, #14, #15 in PR #16<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
SODA1.0-Next page.
| ||||||||
Added: | ||||||||
> > | November 2023 Tucson interop: https://wiki.ivoa.net/internal/IVOA/InterOpNov2023DAL/DAP-SODA-status.pdf | |||||||
Added: | ||||||||
> > | ||||||||
SODA-1.0 feedback, issues and proposalsOn GitHub: https://github.com/ivoa-std/SODA | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
Point made by MarcoMolinaro on 2019-04-18
The SODA (version 1.0) protocol uses the ID parameter to specify opaque identifiers to the dataset or file to be accessed.
Three-factor semantics (Name, UCD, Unit) was mainly thought for interpretation of custom parameters in service descriptors. In the case of a parameter that is part of a standard, like the above SODA ID, the definition of the parameter is unambiguous. However a 3-factor description is still useful for homegeneity and comparison to other parameters.
The UCD specified in the SODA-embedded 3-factor semantics is reported in the REC text as
meta.ref.url;meta.curation.SODAThis is not a valid UCD both for the, probably, typo of the added .SODA part and the fact that meta.curation identifies a man/organization responsible for the data as per the UCD vocabulary. To remedy the situation we propose here to use meta.id;meta.dataset instead. This achieves:
| |||||||
ON January the 16th 2020 Alberto Micol discovered : Page 19 of the SODA standard shows: | ||||||||
Added: | ||||||||
> > | ||||||||
' | ||||||||
Added: | ||||||||
> > | ||||||||
My understanding of the VOTable standard is that the correct way should instead be (see the sentence "All three MIN, MAX and OPTION sub-elements store their value corresponding to the minimum, maximum, or ``special value'' in a value attribute." In the paragraph at: http://www.ivoa.net/documents/VOTable/20191021/REC-VOTable-1.4-20191021.html#sec:values ): | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
| ||||||||
Added: | ||||||||
> > | ||||||||
Changed: | ||||||||
< < | Alberto is perfectly right !!! | |||||||
> > | Alberto was perfectly right !!! This has been fixed with SODA erratum 2 : https://wiki.ivoa.net/twiki/bin/view/IVOA/SODA10Err2 | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
This appeared in a discussion between Alberto Micol and Markus on the dal Mailing list MIN and MAX cannot be single values as in the example It should be an array. But an array of what ? | ||||||||
Changed: | ||||||||
< < | An array of minimal values and an array of maximal values (Markus) | |||||||
> > | An array of minimal values and an array of maximal values (Markus) ? | |||||||
Changed: | ||||||||
< < | An array of minimal length interval and an array of maximal length interval (Alberto) | |||||||
> > | An array of minimal length interval and an array of maximal length interval (Alberto) ? | |||||||
Changed: | ||||||||
< < |
| |||||||
> > | After long discussion (see github issue) this appeared to be an example of MIN/MAX usage for array of values. | |||||||
Added: | ||||||||
> > | By default the MIN and MAX value will be a single number minimizing or maximizing the whole array values.
It will be different foir some xtypes only (for example circle) but not for the xtype=interval we encounter here.
Ths is now explained in SODA erratum 3: https://wiki.ivoa.net/twiki/bin/view/IVOA/SODA10Err3
| |||||||
Considered for version 1.0 but delayed to stay simple (due to syntax problems) Asked by CASDA , others Ranges can be given by SODA service descriptor or computed from ObsCore Which syntax ? | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
This was possible in SIA1.0 for the spatial axis (only) could be done by ADDing standard parameters to SODA for Spatial resolution : SPATRES Rotation : ROTA Sky Projection : PROJ or Alternatively by providing a WCS = (full text of WCS part of FITS header) Skyview + CDS (SIA on top of Hips2FITS) have this functionality | ||||||||
Changed: | ||||||||
< < | Should we stabdardize it ? | |||||||
> > | Should we standardize it ? | |||||||
And If yes should we extend it to SIA2 in virtual mode (SIA issue #8) ? Or should we let it as a mixture of SIAP2 and SIAP1 parameters ? | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
MOC (as well as STMOC, and maybe STEMOC) has proven to be a very efficient way to describe the coverage of data and is used for discovery of data. It has been often discussed and also during last interop that it should be useful to query SODA services by MOC? It should probably be with a new parameter and not via POS considering that it is probably more useful to have STMOC or STEMOC, than spatial MOC alone. This is also valid for SIA of course (SIA Issue #9). Of course, the behaviour for SODA will be very different than the one with SIA. SODA-(ST)MOC will extract a subset matching the (ST)MOC while SIA-MOC will only select datasets intersecting with the MOC. I wonder if this new parameter should not be standardized by DALI | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | eventually this has been implemented in the draft with the https://github.com/ivoa-std/SODA/pull/11 PR | |||||||
Added: | ||||||||
> > |
| |||||||
When several of the PARAM queries (POS, BAND, etc...) are multiple we are facing a cartesian product issue: how do we retrieve all these results. Seems to be easy in async mode which is built to manage multiple results? But in sync? MEF formats? archive files? VOTable containing pointers? What about using UPLOAD functionality (DALI, 3.4.5 UPLOAD) for this? | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
First implementations already provide various flavours of cutouts from cubes. Some cutout interface can extract subcubes from a large cube. Some others could create spectra or images (dimension reduction). An idea could be to use the DPTYPE parameter designed for SIAP2 to force this product_type conversion. This has been discussed for TimeSeries there: http://www.ivoa.net/documents/Notes/TimeSeriesDiscoveryAndAccess/index.html | ||||||||
Added: | ||||||||
> > |
As a server side operation for data access protocol, SODA should provide format transformation :
FITS to png or jpeg looks rather classical.
FrancoisBonnarel 2023-11-09
Fits to HiPS (operating HipS generation) or HIPS to fits SHOULD be more and more useful.
There are proposed subsections for issues #3, #4, #7, #14, #15 in PR #16 | |||||||
<--
|
SODA1.0-Next page.
SODA-1.0 feedback, issues and proposalsOn GitHub: https://github.com/ivoa-std/SODA
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
SODA1.0-Next page.
SODA-1.0 feedback, issues and proposalsOn GitHub: https://github.com/ivoa-std/SODA
<--
|