womullan at skysrv.pha.jhu.edu
Tue Feb 24 06:35:43 PST 2004
Tony thanks for jolting this back into view ..
I agree we need to move forward on this - we have been looking to slightly simplify ADQL/XML. We may present this in the next couple of days.
I would like the BNF to become part of the ADQL standard document and
that for now at least we keep ADQL XML and strings in sync.
Its a busy time over here with proposals and SDSS work so sorry for not advancing the above. There are a few minor mods and clarifications which the document needs which can wait a little - this I think is important and what Masatoshi also wants. But I would like until the weeks end to see if we may present an even slightly simplified XSD for ADQL. Otherwise lets move ahead with
the last one. This does require settling the region issue though.
This may easily be supported by any given service by having the "into" as
a separate param so
Query(ADQL qry) returns the Response
QueryMyspace(ADQL qry, MYSAPCEref ref)
puts the answer in mysapce
QueryMyDB(ADQL qry, MYDBref ref)
puts it in my db
We do not particularly need into in ADQL - you will simply parse it out
to enable operations such as above in any case.
REGARDING DML (create, drop ...)
Likewise DML may be handled in this manner if we are only making
These however we should probably be added. I do not see this as a major problem. I think we should agree on the query format make some prototypes
really get happy with it then add CREATE DROP etc.
This requires a whole other level of sophistication on the server side.
At this point we could also add into.
More information about the voql