SIA issues

1
SIA issues

• F.Bonnarel
• In behalf of
• Next slide please !

2

• P.Osuna (ESAC) M.Dolensky (ESO)
• J.Salgado (ESAC) F.Pierfederici (ESO)
• T.Boch (CDS) L.Michel (Obs
  Stras)
• P.Fernique (CDS) H.Nguyen(Obs Stras)
• M.Louys (ULP) D.Cavaroc(ObsStr)
• D.Durand (CADC) D.Tody ( DAL chair)
• L.Simard (CADC)
• A.Micol (ECF)

3
SIA 1.0

• SIA 1.0 solved the availability problem
• SIA 1.0 in VO registries
• SDSS
• MAST
• Dozens .
• SIA 1.0 augmented graphics use of the SIA WCS
  fields to build astromertric calibration on top
  of JPEG images. ESO/CDS joint VOTECH project -gt
  Francesco

4
Availability problem
5
Towards SIA 1.1

• SIA Query reponse should contain everything
  necessary for a basic selection of the data
  dataset, curation, target, characterization
  (level 1 and 2), access description, like in SSA
• Special case of WCS basic usage withe graphic
  formats (simple WCS)
• Extension mechanism needed for detailed, complex
  or heterogeneous description of the metadata.

6
SIA extension use cases

• Large common metadata ( data collections
  descriptions)
• Level 3 and 4 of characterization (e.g.
  observation detailed FOV)
• Complex relationships between observations
• Heterogeneous data relationships (images towards
  spectra or sources)
• Complex structure observations
• Full DataAccessAndViews issues extended cutouts
  in cubes, previews, retrieval pages, etc..
• Provenance details (instrument or software)
• Calibration description

7
Extensions basic principle

• Main RESOURCE like in SIA 1.0 or SSA 0.9.
• Additional RESOURCES admitted including new
  tables, groups and xml elements
• Associations made by VOTABLE ID/ref mechanism
• From fields in the main section to elements in
  the Extensions
• From fields in the Extensions towards the main
  section
• Utypes are qualifying the associations
• Observation/identifier (dataset/id)
• CharaxisFrame/ucdpos/coverage/support

8
Test Implementations

• Overall comments using utypes on elements to
  generate VO client behavior, eg stc ones. Only
  Aladin as a client (others?)
• CGPS at CADC on line since May 2005, Radio Cube
  slicer.
• Detailed FOV ESO/CDS see demo by Francesco
• Heterogeneous data access, based on SAADA (ADASS
  focus demo)
• Ongoing cfhtls, others ?

9
CGPS Metadatatree in Aladin From SIA with
extensions
10
CGPS HI cube slice/access From SIA with extensions
11
Test Implementations

• Overall comments using utypes on elements to
  generate VO client behavior, eg stc ones. Only
  Aladin as a client (others?)
• CGPS at CADC on line since May 2005, Radio Cube
  slicer.
• Detailed FOV ESO/CDS see demo by Francesco
• Heterogeneous data access, based on SAADA (ADASS
  focus demo)
• Ongoing cfhtls, others ?

12
(No Transcript)
13
(No Transcript)
14
(No Transcript)
15
Test Implementations

• Overall comments using utypes on elements to
  generate VO client behavior, eg stc ones. Only
  Aladin as a client (others?)
• CGPS at CADC on line since May 2005, Radio Cube
  slicer.
• Detailed FOV ESO/CDS see demo by Francesco
• Heterogeneous data access, based on SAADA (ADASS
  focus demo)
• Ongoing cfhtls, others ?

16
(1) Link to the selected image
(3) Link to a Saada view of the correlated
spectra
(2) Link to the correlated sources with
an anchor on Saada for each of them
(4) Link to a Specview view of the correlated
spectra
17
Is SSA still different from SIA?

• SSA and SIA can share most of the query response
  fields dataset, curation, target, access and
  characterization
• Extension mechanism valid for both.
• But
• Query parameters (MUST and SHOULD) may stay
  different. (Roys keep it simple )
• WCS status is different for SIA and SSA. Exemple
  of cubes versus IFU.