Hola Mar'ia,
As you may pass this email around, I'll write in english. I have a concern respect to the case in which column names contain "funny" characters ( (), [], ' and ", -, . etc ). I've seen a number of them deployed in our registry and they're obviously valid names in their home databases. The problem, however, arises when one wants to parse ADQL-s to ADQL-x, when interpreters start complaining about non-existing functions ( eg, M(B) ) or they think it's an arithmetics operation (eg, B-V, -logF etc).
If this has been discussed, can you point me out to some reference? And if it hasn't, can this be addressed before registries get overpopulated ? Going back then will be quite painful.
The problem I mention seems to be exclusively a problem in how to handle the queries, eg, ADQL, registries don't have any problem in accepting the name of these columns.
Cheers,
Patricio
On Wed, 21 Sep 2005, Maria A. Nieto-Santisteban wrote:
> Dear all,
>
> Here it is the prospective agenda for the VOQL session. The main topic will
> be the ADQL and SkyNodes WDs.
>
> We have allocated 40 to 45 minutes for those who would like to present
> their work in the area. Please let us know if you wish to give a short
> presentation.
>
> See you soon
>
> Yuji Shirasaki and Maria Nieto-Santisteban
>
> ==========================================================================
> VOQL agenda
>
> IVOA interoperability meeting
> San Lorenzo del Escorial, Madrid, Spain
> Friday, October 10th, 9:30 - 13:00
>
> Maria Nieto-Santisteban & Yuji Shirasaki
>
> 1. Road Map: (Yuji & Maria: 10')
> - Where are we?
> - Meeting goals
>
> 2. Review ADQL and SkyNode specifications WD: (All: 60')
> - ADQL v1.0
> * SQL 92
> - The SELECT statement
> - BNF independent from language (Post C# as a
> external reference)
> * XMATCH function(s) syntax
> * Single & Multi node queries
>
> - SkyNode v1.0
> * XMATCH function(s) algorithms
> * Architecture Decoupling (Cascade and Parallel)
> * Add a mechanism to transmit "messages" in addition to
> data
> * Content standardization in returned VOTable
>
> 3. Metadata. How enforce quality? (Maria: 10')
>
> 4. Discuss schedule to upgrade skynodes from 0.7 to 1.0 (All: 10')
>
> - break -
>
> 5. Short presentations (No more than 40 - 45'; 10' to 15' each depending
> on quantity )
>
> 6. Future - Brief discussion (As time permits)
>
> * The '!' operator problem. Need for proper footprints. (Maria:
> 10')
>
> * VOQL needs diversity: equivalent implementations of Open
> SkyQuery portals accepting distributed queries
>
> * XMATCH function(s) algorithms (How do we include errors?)
>
> * How do we deal with big query results? The path to VOStore
>
> * Xmatch works only between primary table from SkyNode
> (What needs to be done to allow xmatch with others?)
>
> * Table data model (standard column names) Where does the Catalog
> Data Model WG stand?
>
> * Query by ucd and utype
>
> 7. Update Road Map
>
>
--- Patricio F. Ortiz pfo-at-star.le.ac.uk Department of Physics & Astronomy Phone: +44 (0)116 252 2015 University of Leicester Leicester, LE1 7RH, UKReceived on 2005-09-21Z11:10:55