New release of TAP-, ADQL- and UWS-Lib

[Gregory MANTELET]

Dear TAP-, ADQL- and UWS-Lib users,

This email is an announcement of 5 news /(especially #4 and #5)/ 
concerning TAP-,
ADQL- and UWS-Lib.

I will also speak into more details about these at the Interop next 
week. But
because these news may also interest whoever can not attend to this 
event, I am
also summing them up in here.

--------------------------------------------------------------------------------

1. NEW RELEASES

     - ADQL-Lib v1.5 - still supporting only ADQL-2.0
         - details: http://cdsportal.u-strasbg.fr/adqltuto/news.html

     - UWS-Lib v4.4 - supporting UWS-1.1
         - details: http://cdsportal.u-strasbg.fr/uwstuto/news.html

     - TAP-Lib v2.3 - still supporting TAP-1.0
         - details: http://cdsportal.u-strasbg.fr/taptuto/news.html

These releases are mostly about fixing few bugs...

--------------------------------------------------------------------------------

2. NEW ADQL/TAP FEATURE: quick fix

...but there is anyway one new feature now available in ADQL-Lib: a 
possibility
to quickly fix ADQL queries. This is particularly interesting if you often
experience non-qualified column/table names and aliases (e.g. `public` 
instead
of `"public"`, `distance` instead of `"distance"`, etc...) ; see the links
below for more explanations.

You can use this feature in two ways:

     a- directly call the function ADQLParser.tryQuickFix(String)

     b- in TAP-Lib, set the configuration parameter `fix_on_fail` to 
`true` ;
        this will trigger the auto quick-fix only when the parsing of an 
ADQL
        query fails /(this feature is disabled by default)/.

---
/For more details see://
//    - "Add to the parser a function attempting to quickly fix an ADQL 
query."//
//      in //http://cdsportal.u-strasbg.fr/adqltuto/news.html//
//    - "New feature: automatic quick fix of ADQL queries."//
//      in //http://cdsportal.u-strasbg.fr/taptuto/news.html/

--------------------------------------------------------------------------------

3. NEW MAJOR RELEASES UNDER-DEVELOPMENT

The next release of the libraries aims to support ADQL-2.1 and TAP-1.1.
Developments have already started, and will be regularly pushed on the 
GitHub
repository (https://github.com/gmantele/taplib).

You can watch the progress using the GitHub Projects:
https://github.com/gmantele/taplib/projects (especially those for 
ADQLLib-1.6 <https://github.com/gmantele/taplib/projects/10>
and TAPLib-2.4 <https://github.com/gmantele/taplib/projects/9>). I will 
try to update them as much as I can.

I will speak into more details about the current progress in ADQL-2.1.

Indeed, few API modifications will be required so that supporting these 
new IVOA
standard versions (especially for TAP-1.1). In the case of TAP-Lib, you 
do not
have much to worry if you are already using the configuration file. 
Otherwise,
I recommend you to take some time migrating to this method ; it will 
save you
time and energy when upgrading TAP-Lib.

--------------------------------------------------------------------------------

4. VOLLT: NEW NAME FOR THIS LIBRARY-SET

It was a long time that I was searching for a name to gather all these
libraries. This research is now over. You can now refer to all these 
libraries
as part of the framework/library-set named "VOLLT".

A name was needed because of the next evolutions to come concerning this
library-set. More about this at the interop (and later by email for 
those who
can not attend).

The GitHub repository has also been renamed from "taplib" into "vollt":

https://github.com/gmantele/vollt

But don't worry, despite this renaming, the former GitHub link and name are
still working.

--------------------------------------------------------------------------------

5. DEDICATED MAILING-LIST

So that not spoiling IVOA mailing lists with news about the VOLLT 
libraries, I
created a simple diffusion mailing list:

vollt-announce at astro.unistra.fr

To subscribe, just send an email to

sympa at astro.unistra.fr

with only the subject "subscribe" (eventually followed by your first 
name and
surname ; example: "subscribe John Doe"). The following link should also 
work
for mailing clients accepting HTML
mailto:sympa at astro.unistra.fr?subject=subscribe

Its sole purpose is to let me broadcast information to only interested 
persons.
It is not a /discussion/ but a /diffusion//list/ used by me to send 
newsletters to
you ; thus, you will not be able to send any email to this address.

But, as until now, if you have questions, comments or suggestions, keep 
sending
me emails directly or keep writing GitHub issues or pull-requests. I will be
glad to answer to you as quickly as I can.

--------------------------------------------------------------------------------

Cheers, and for some of you, see you in Paris next week,
Grégory

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20190509/787a05b2/attachment.html>