<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Dear TAP-, ADQL- and UWS-Lib users,<br>
<br>
This email is an announcement of 5 news <i>(especially #4 and #5)</i>
concerning TAP-,<br>
ADQL- and UWS-Lib.<br>
<br>
I will also speak into more details about these at the Interop next
week. But<br>
because these news may also interest whoever can not attend to this
event, I am<br>
also summing them up in here.<br>
<br>
<tt>--------------------------------------------------------------------------------</tt><br>
<br>
1. NEW RELEASES<br>
<br>
- ADQL-Lib v1.5 - still supporting only ADQL-2.0<br>
- details: <a moz-do-not-send="true"
href="http://cdsportal.u-strasbg.fr/adqltuto/news.html">http://cdsportal.u-strasbg.fr/adqltuto/news.html</a><br>
<br>
- UWS-Lib v4.4 - supporting UWS-1.1<br>
- details: <a moz-do-not-send="true"
href="http://cdsportal.u-strasbg.fr/uwstuto/news.html">http://cdsportal.u-strasbg.fr/uwstuto/news.html</a><br>
<br>
- TAP-Lib v2.3 - still supporting TAP-1.0<br>
- details: <a moz-do-not-send="true"
href="http://cdsportal.u-strasbg.fr/taptuto/news.html">http://cdsportal.u-strasbg.fr/taptuto/news.html</a><br>
<br>
These releases are mostly about fixing few bugs...<br>
<br>
<tt>--------------------------------------------------------------------------------</tt><br>
<br>
2. NEW ADQL/TAP FEATURE: quick fix<br>
<br>
...but there is anyway one new feature now available in ADQL-Lib: a
possibility<br>
to quickly fix ADQL queries. This is particularly interesting if you
often<br>
experience non-qualified column/table names and aliases (e.g. `<tt>public</tt>`
instead<br>
of `<tt>"public"</tt>`, `<tt>distance</tt>` instead of `<tt>"distance"</tt>`,
etc...) ; see the links<br>
below for more explanations.<br>
<br>
You can use this feature in two ways:<br>
<br>
a- directly call the function <tt>ADQLParser.tryQuickFix(String)</tt><br>
<br>
b- in TAP-Lib, set the configuration parameter `<tt>fix_on_fail</tt>`
to `<tt>true</tt>` ;<br>
this will trigger the auto quick-fix only when the parsing of
an ADQL<br>
query fails <i>(this feature is disabled by default)</i>.<br>
<br>
<tt>---</tt><br>
<i>For more details see:</i><i><br>
</i><i> - "Add to the parser a function attempting to quickly fix
an ADQL query."</i><i><br>
</i><i> in </i><i><a moz-do-not-send="true"
href="http://cdsportal.u-strasbg.fr/adqltuto/news.html">http://cdsportal.u-strasbg.fr/adqltuto/news.html</a></i><i><br>
</i><i> - "New feature: automatic quick fix of ADQL queries."</i><i><br>
</i><i> in </i><i><a moz-do-not-send="true"
href="http://cdsportal.u-strasbg.fr/taptuto/news.html">http://cdsportal.u-strasbg.fr/taptuto/news.html</a></i><br>
<br>
<tt>--------------------------------------------------------------------------------</tt><br>
<br>
3. NEW MAJOR RELEASES UNDER-DEVELOPMENT<br>
<br>
The next release of the libraries aims to support ADQL-2.1 and
TAP-1.1.<br>
Developments have already started, and will be regularly pushed on
the GitHub<br>
repository (<a moz-do-not-send="true"
href="https://github.com/gmantele/taplib">https://github.com/gmantele/taplib</a>).<br>
<br>
You can watch the progress using the GitHub Projects:<br>
<a moz-do-not-send="true"
href="https://github.com/gmantele/taplib/projects">https://github.com/gmantele/taplib/projects</a>
(especially those for <a moz-do-not-send="true"
href="https://github.com/gmantele/taplib/projects/10">ADQLLib-1.6</a><br>
and <a moz-do-not-send="true"
href="https://github.com/gmantele/taplib/projects/9">TAPLib-2.4</a>).
I will try to update them as much as I can.<br>
<br>
I will speak into more details about the current progress in
ADQL-2.1.<br>
<br>
Indeed, few API modifications will be required so that supporting
these new IVOA<br>
standard versions (especially for TAP-1.1). In the case of TAP-Lib,
you do not<br>
have much to worry if you are already using the configuration file.
Otherwise,<br>
I recommend you to take some time migrating to this method ; it will
save you<br>
time and energy when upgrading TAP-Lib.<br>
<br>
<tt>--------------------------------------------------------------------------------</tt><br>
<br>
4. VOLLT: NEW NAME FOR THIS LIBRARY-SET<br>
<br>
It was a long time that I was searching for a name to gather all
these<br>
libraries. This research is now over. You can now refer to all these
libraries<br>
as part of the framework/library-set named "VOLLT".<br>
<br>
A name was needed because of the next evolutions to come concerning
this<br>
library-set. More about this at the interop (and later by email for
those who<br>
can not attend).<br>
<br>
The GitHub repository has also been renamed from "taplib" into
"vollt":<br>
<br>
<a moz-do-not-send="true"
href="https://github.com/gmantele/vollt">https://github.com/gmantele/vollt</a><br>
<br>
But don't worry, despite this renaming, the former GitHub link and
name are<br>
still working.<br>
<br>
<tt>--------------------------------------------------------------------------------</tt><br>
<br>
5. DEDICATED MAILING-LIST<br>
<br>
So that not spoiling IVOA mailing lists with news about the VOLLT
libraries, I<br>
created a simple diffusion mailing list:<br>
<br>
<tt><a class="moz-txt-link-abbreviated" href="mailto:vollt-announce@astro.unistra.fr">vollt-announce@astro.unistra.fr</a></tt><br>
<br>
To subscribe, just send an email to<br>
<br>
<tt><a class="moz-txt-link-abbreviated" href="mailto:sympa@astro.unistra.fr">sympa@astro.unistra.fr</a></tt><br>
<br>
with only the subject "<tt>subscribe</tt>" (eventually followed by
your first name and<br>
surname ; example: "<tt>subscribe John Doe</tt>"). The following
link should also work<br>
for mailing clients accepting HTML<br>
<a moz-do-not-send="true"
href="mailto:sympa@astro.unistra.fr?subject=subscribe">mailto:sympa@astro.unistra.fr?subject=subscribe</a><br>
<br>
Its sole purpose is to let me broadcast information to only
interested persons.<br>
It is not a <i>discussion</i> but a <i>diffusion</i><i> list</i>
used by me to send newsletters to<br>
you ; thus, you will not be able to send any email to this address.<br>
<br>
But, as until now, if you have questions, comments or suggestions,
keep sending<br>
me emails directly or keep writing GitHub issues or pull-requests. I
will be<br>
glad to answer to you as quickly as I can.<br>
<br>
<tt>--------------------------------------------------------------------------------</tt><br>
<br>
Cheers, and for some of you, see you in Paris next week,<br>
Grégory<br>
<br>
</body>
</html>