The case for XML ADQL

[Tony Linde]

Hi Masatoshi,

> In JVO, we can edit ADQL/s on a user's window. This is so 
> useful because users can save her/his previous ADQL/s as 
> files in her/his client machine, can load the files into the 
> client interface, and then edit, if necessay.

Do you have a ADQL/s -> ADQL/x parser/translator? (preferably in Java)

Cheers,
Tony. 

> -----Original Message-----
> From: Masatoshi OHISHI [mailto:masatoshi.ohishi at nao.ac.jp] 
> Sent: 05 February 2004 10:12
> To: Tony Linde; voql at ivoa.net
> Subject: RE: The case for XML ADQL 
> 
> 
> Hi Tony,
> 
> At 09:52 04/02/05 +0000, Tony Linde wrote:
>  >Welcome back Masatoshi,
> 
> Long way to come back here (^_^!!
> 
> I haven't got the reason why you found that your translator 
> was so slow.
> 
>  >should *not* have two different names or versions of the 
> language (and I  >believe it was accepted). The only query 
> language is ADQL, its primary  >format is the xml form and we 
> will specify how the xml form can be  >translated into a text 
> form for display purposes.
> 
> Yes, we need to aviod any confusion, whatever the name is.
> 
> So, at this moment, I call ADQL/s (s stands for string) and ADQL/x.
> 
> In JVO, we can edit ADQL/s on a user's window. This is so 
> useful because users can save her/his previous ADQL/s as 
> files in her/his client machine, can load the files into the 
> client interface, and then edit, if necessay.
> 
> This method is much faster for users when repeating queries 
> with a little modification.
> 
> Cheers,
> 
>    Masatoshi 
> 
>