<--
DAL Future - discussion pageThis page is meant to gather opinions, feedback and proposals for DAL future (see Trieste 2016 Fall Interop presentation). The underlying question is what will be the main evolution of the DAL protocols in a near future (SIA, SODA, TAP, ADQL, DataLink, etc.). The main drivers are: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | Properties to consider: | |||||||
| ||||||||
Changed: | ||||||||
< < | (please, when creating a page to link from a topic here, use a DALFutureTopic TWiki name for the new page) | |||||||
> > | (please, when creating a page to link from a topic here, use a DALFutureTopic TWiki name for the new page) | |||||||
Data Type | ||||||||
Deleted: | ||||||||
< < | Add Time Domain (HIGHEST Scientific priority: see CSP Time Series use cases) | |||||||
Added: | ||||||||
> > | Add Time Domain ( HIGHEST Scientific priority: see CSP Time Series use cases) | |||||||
Functionalities
Software DesignInterface design | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Pushing code to the data | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Formats and Languages
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
TAP evolution
Position in IVOA landscape | ||||||||
Changed: | ||||||||
< < | Merging DAL protocols, HiPS and MOC | |||||||
> > | Merging DAL protocols, HiPS and MOC | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Data Models
| ||||||||
Added: | ||||||||
> > |
Updating SCSSCS still requires VOTable 1.1 and has some other quirks that makes it needlessly incompatible with the rest of the DAL landscape (in particular, it's totally DALI-incompatible). We should figure out how we can evolve it to be less odd with minimal disruption to existing services and clients (e.g., relaxing VOTable requirements, support for DALI MAXREC, RESPONSEFORMAT, metadata discovery). -- MarkusDemleitner - 2017-03-01 |