-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for MOC #9
Comments
Use cases for which I use MOCs to filter tables and get fast results:
|
I do agree with Ada, and in addition I would add the STMOC as well at least as an experiment in order to cover both the time and the spatial coverage. Of course it would have to be potentially revised once the STMOC is an IVOA standard. But the basic principles are the same. This would be really powerful. |
Well -- given this spec ought to go out of the door just about now, I don't think we should put in anything new; implementation of MOC or even STMOC can continue nevertheless (DaCHS 2.2 will come with MOC support in ADQL, for instance). The one thing we could do right now is either reserve the words MOC and STMOC right away or at least announce that we will reserve them in 2.2. I give you reserving new words is an incompatible change, but if we make a new major version each time we reserve a new word, we'll kill the usefulness of major version steps. And not reserving MOC will open up a lot of syntactic ambiguities, so let's not do that either. |
MOC (and eventually STMOC) is something I intend to add for the next version after ADQL-2.1. So, not for the current version we are working on...hence the milestone But right, we could prepare its addition by reserving the word |
Several people have expressed interest in supporting MOC as search criteria in ADQL.
Please add your use cases in comments for this issue and we will try to bring them together into a plan.
The text was updated successfully, but these errors were encountered: