voql-teg: Minutes of VOQL-TEG Meeting #1

From: Pedro Osuna <Pedro.Osuna-at-sciops.esa.int>
Date: Tue, 24 Oct 2006 11:45:00 +0200

Dear all,

I send you finally the minutes of the VOQL-TEG meeting that we celebrated on Oct 10th. Sorry for the delay, but there has been loads of things in between.

Please take note of your actions, and remember to send any discussions to the list voql-teg-at-ivoa.net, where we will keep discussing items.

The notes only reflect points we discussed without making them too explicit. The list of actions, though, should be clear enough. In case they are not, please let me know.

VOQL-TEG Meeting #1

(Teleconf)
(Phone number: +34 91 398 38 52)
(Pin number: 	872450)

Present:

YS,KA,DT,BG,PD,AS,IO,PO,FO (see below for acronyms list) Notes by: PO

0) Point number 0 of agenda (Approval of previous meeting) ignored

Introduction to the group done by PO. Then, people introduced themselves briefly.
Summary of new structure given by PO.
- Agree on separation of Language, protocol and Servicve
- Agree on only having one single name for the language. From now on, only ADQL.
Discussion on ADQL
- IO gives a summary on a possible view for the new structure of the
ADQL language. Basically it is described as being one single specification, BNF based. With core and extension.
- some disagree on having an XML serialisation even as an example or an
appendix. I believe we agreed on not having an XML serialisation in the document.
- KA says they are working on a BNF to XML translator
**(see VOQL-TEG-1/AI#1)
- AS comments he basically agrees with IO exposition.
- KA comments on whether the Group by, order by, etc., should be in the extension or in the core. AS comments that they should be in the extension. For instance, for federated joins (two servers) an order by could be very uncomfortable.
- a discussion is had on whether region should be part of Core or not. **(see VOQL-TEG-1/AI#2)
- a proposal to include region as a new ADQL clause is mentioned on behalf of YS. General disagreement of this proposal, as it would brake already exisiting services. Nevertheless, an action is set on YS to explain in written form the benefits he sees on such an approach. **(see VOQL-TEG-1/AI#3)
- an action is set up on YS, IO and PO to start the rewriting of the ADQL doc **(see VOQL-TEG-1/AI#8)
Discussion on TAP
- we go through Ray Plant's presentation on Moscow on the NVO team
research and possible inputs for the TAP.
- we discuss about whether REST or SOAP transports for the TAP should be compulsory or otherwise. KA argues on whether the REST should be the default, and DT has a different view. We agree to discuss it in the list. **(see VOQL-TEG-1/AI#4)

NOTE: for discussion in the list, we should all send inputs on what we think "Compulsory" should mean in terms of both a Protocol and in the Language.

KA argues on whether SQL native should be in the protocol or outside. No action noted here but people should send their inputs if any.
UPLOAD not part of the language, but part of the protocol or the service. However, YS disagrees. **(see VOQL-TEG-1/AI#5, VOQL-TEG-1/AI#6)
we initiate discussion on Cross-match issues. However, we all agree that AS presence is required in the discussion, and as AS had to interrupt the teleconf at some prior point, we agree to relegate the discussion to next VOQL-TEG-2 meeting.
FO mentions his worry on how to retrieve metadata from the service using TAP. DT agrees this has to be addressed. **(VOQL-TEG-1/AI#7) 5) AOB: None.

List of VOQL-TEG-1 Action Items:

+VOQL-TEG-1/AI#1 on KA: To distribute BNF --> XML translator to the list

+VOQL-TEG-1/AI#2 on ALL: To send to the list (voql-teg-at-ivoa.net) where to put REGION

+VOQL-TEG-1/AI#3 on YS: To send to the list why he believes REGION should be a new ADQL clause

+VOQL-TEG-1/AI#4 on KA/DT: To send note on why REST and/or SOAP should be considered Compulsory or optional

+VOQL-TEG-1/AI#5 on YS: To sen dnote to the list on why he believes UPLOAD should be part of the language

+VOQL-TEG-1/AI#6 on ALL: To send to list inputs on preferences to have the UPLOAD (whether in the Protocol or in the Service)

+VOQL-TEG-1/AI#7 on FO (plus DT/KA): to propose a mechanism for getting table metadata within the TAP and possible output format

+VOQL-TEG-1/AI#8 on YS/IO/PO to initiate the refurbishing of the ADQL spec to have it as a basis

+VOQL-TEG-1/AI#9 on PO/DT: to start writing the TAP document

+VOQL-TEG-1/AI#10 on PO: To change IVOA wiki pages

List of personal acronyms:

AS:	Alex Szalay
BG:	Benjamin Gufler
DT:	Doug Tody
FO:	Frnacois Ochsenbein
IO: 	Inaki Ortiz
KA:	Kona Andrews
PD:	Pat Dowler
PO:	Pedro Osuna	
YS:	Yuji Shirasaki

-- 
Pedro Osuna Alcalaya

European Space Agency (ESA)
European Space Astronomy Centre (ESAC)
Research and Scientific Support Department (RSSD)
Astronomy Science Operations Division (SCI-SD)
e-mail: Pedro.Osuna-at-esa.int
Tel + 34 91 813 13 14    Fax: +34 91 813 11 72
-------------------------------------------------                                                                                
European Space Astronomy Centre (ESAC)
P.O. Box 50727
E-28080 Villafranca del Castillo
MADRID - SPAIN

================================================================================================
This message and any attachments are intended for the use of the addressee or addressees only. The
unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content
is prohibited. If you received this message in error, please delete it from your system and notify
the sender. E-mails can be altered and their integrity cannot be guaranteed. ESA shall not be liable
for any e-mail if modified.
=================================================================================================

Received on 2006-10-24Z11:48:19