# DALI/TAP/ADQL session and splinter

## Session (Tuesday May 10 - plenary)
DALI-1.1, TAP-1.1 and ADQL-2.1 WD reports.
DALI and TAP implementations at CADC.
/examples endpoint presentation by Markus.
Cosmopterix Docker-based project to help ADQL tests against various backends.

### DALI-1.1
- arraysize for intervals must be 2
- more flexibility on VOSI endpoint names, easier public/authenticated access implementations, /availability even more flexible (not related to base URL)
- polygon interpretation: single winding direction (to be reference/repeated in ADQL)
- /examples using RDFa to have machine and human readability
- more geometry types is DALI: ellipses YES, but moved to DALI-1.2, box NO

- timestamp 'Z' pushed to TCG decision: impacts various standards from multiple WGS

### TAP-1.1
- datatype mapping moved to DALI xtypes, some checks still TODO for clob/blob DBMS types. Mapping move to DALI cleans up specs dependencies. Suggest array mapping best practice.
- highly recommend default endpoints (e.g. /tables) for primary iterface
- unnamed columns: highly recommand unique column name in output
- duplicate columns: allow, but warn against unspecified behaviour
- allow delimited identifiers in UPLOAD
- WARNING: all the 3 above have an impact on VOTable too

### ADQL-2.1
#### draw a line to go PR on:
- adds BOOLEAN, HEX, OFFSET
- DISTANCE overload
- COORDSYS string deprecated (overloads 2.0 ones)
- include text to describe recommended syntax for performing cross match 

#### contentious:
- REGION: keep or drop?

#### to startup version 2.2
- no POINT overloading to geometric functions overload
- no POINT in polygons in 2.1
- {} syntax for point literal, pushed for further discussion
- value expression in ORDER BY, ...

#### other:
- unnamed/duplicate column issues from TAP impacts here, of course