BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//adass2023//speaker//BDHDQL
BEGIN:VTIMEZONE
TZID:US/Arizona
BEGIN:STANDARD
DTSTART:20221106T000000
TZNAME:MST
TZOFFSETFROM:-0700
TZOFFSETTO:-0700
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:PEG-ify ADQL - Markus Demleitner\, Grégory Mantelet
DTSTART;TZID=US/Arizona:20231106T083000
DTEND;TZID=US/Arizona:20231106T083000
DTSTAMP:20260816T100248Z
UID:pretalx-adass2023-WKS7HP@pretalx.com
DESCRIPTION:ADQL is a language defined by the IVOA for querying astronomic
 al data. It stands for Astronomical Data Query Language. It is a fork of S
 QL-92 in which only the query features are used. Astronomical functions an
 d operators have been added\, in particular to query data by position. Thi
 s language is mainly used in the IVOA protocol called TAP for querying rel
 ational astronomical data.\n\nUntil now\, the ADQL grammar has been descri
 bed in a BNF (Backus-Naur-Form)-inspired formalism\, largely following SQL
 -92 itself. However\, in its current form it is not actually used by any i
 mplementation for several reasons\, including some minor mistakes and lacu
 nae\, which were in practice filled borrowing from other SQL implementatio
 ns. Also\, the lack of stringent tokenisation rules resulted in differing 
 interpretations of corner cases (e.g. the string literal '49a').\n\nIn the
  next version of ADQL\, it is therefore proposed to change the ADQL langua
 ge notation from BNF to PEG (Parsing Expression Grammar). In PEG\, parsing
  and tokenisation are specified in a uniform way\, and PEG's own grammar i
 s standardised sufficiently well that multiple interoperating implementati
 ons can be used off the shelf to obtain parse trees of ADQL clauses (at le
 ast conceptually).\n\nThis poster aims to show what are the difference bet
 ween the two notations and what improvements this implies for ADQL.
LOCATION:Posters
URL:https://pretalx.com/adass2023/talk/WKS7HP/
END:VEVENT
BEGIN:VEVENT
SUMMARY:Discover your astronomical data from python – simply! - Markus D
 emleitner\, Renaud Savalle\, Hendrik Heinl
DTSTART;TZID=US/Arizona:20231106T083000
DTEND;TZID=US/Arizona:20231106T083000
DTSTAMP:20260816T100248Z
UID:pretalx-adass2023-MK7PEP@pretalx.com
DESCRIPTION:The VO Registry is a set of about 30\,000 metadata records of 
 astronomical resources.  It is queryable using the powerful RegTAP protoc
 ol requiring users to write ADQL. A friendlier interface using that proto
 col has recently been written a part of the pyVO astropy affiliated packag
 e. In this poster\, we briefly introduce the standards this is implemented
  against. The new API can be used by astronomers to discover data based on
  various constraints\, ranging from free text to physical concepts and are
 as in space\, time\, and spectrum.
LOCATION:Posters
URL:https://pretalx.com/adass2023/talk/MK7PEP/
END:VEVENT
BEGIN:VEVENT
SUMMARY:All your shapes in ADQL: MOCs in the TAP ecosystem - Markus Demlei
 tner
DTSTART;TZID=US/Arizona:20231106T083000
DTEND;TZID=US/Arizona:20231106T083000
DTSTAMP:20260816T100248Z
UID:pretalx-adass2023-ZXYCCW@pretalx.com
DESCRIPTION:MOCs\, the HEALPix-based Multi-Order Coverage maps\, are a pow
 erful tool\nfor representing arbitrary shapes on the sphere with user-sele
 ctable\nfidelity and remarkable compactness.  Their most salient feature i
 s that\noperations such as union and intersection\, nightmarish with conve
 ntional\ngeometries\, are just a few lines of readable code with MOCs.  Th
 is makes\nMOC support a natural complement for the Virtual Observatory's A
 stronomy\nData Query Language ADQL.  Indeed\, the latest version of the AD
 QL-based\nRegistry discovery protocol RegTAP already makes use of MOCs.  T
 his\nposter describes some proposed ADQL extensions to make MOCs even more
 \nuseful in TAP and ADQL and discusses these extensions' implementation\ns
 tatus.
LOCATION:Posters
URL:https://pretalx.com/adass2023/talk/ZXYCCW/
END:VEVENT
END:VCALENDAR