IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006 | |||||||||||
Changed: | |||||||||||
< < | VO Query Language (IvoaVOQL) Sessions | ||||||||||
> > | VO Query Language (VOQL) Sessions | ||||||||||
Open Plenary sessionThe Open Plenary session slides can be found here | |||||||||||
Changed: | |||||||||||
< < | IvoaVOQL-1 Session - Tuesday morning 11:00-12:30 | ||||||||||
> > | VOQL-1 Session - Tuesday morning 11:00-12:30 | ||||||||||
Minutes of the session (notes by J. Salgado) | |||||||||||
Changed: | |||||||||||
< < | Future work for the IvoaVOQL groupThe main idea in the new direction of the IvoaVOQL group is to sepaerate the language | ||||||||||
> > | Future work for the VOQL groupThe main idea in the new direction of the VOQL group is to sepaerate the language | ||||||||||
from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. | |||||||||||
Changed: | |||||||||||
< < | To try to remove these incompatibilities, the IvoaVOQL group has decided to separate | ||||||||||
> > | To try to remove these incompatibilities, the VOQL group has decided to separate | ||||||||||
completely languag and access, and work consequently in the following three
areas:
| |||||||||||
Changed: | |||||||||||
< < | | ||||||||||
> > | | ||||||||||
| |||||||||||
Changed: | |||||||||||
< < | The first two will be dealt by the IvoaVOQL group directly. The third one will | ||||||||||
> > | The first two will be dealt by the VOQL group directly. The third one will | ||||||||||
be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. | |||||||||||
Changed: | |||||||||||
< < | We have created a IvoaVOQL Technical Experts Group (IvoaVOQL-TEG) to deal with all | ||||||||||
> > | We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all | ||||||||||
the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. | |||||||||||
Changed: | |||||||||||
< < | The IvoaVOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes | ||||||||||
> > | The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes | ||||||||||
of the discussions within the group will be fed to the community periodically,
to get proper feedback.
An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
| |||||||||||
Changed: | |||||||||||
< < | IvoaVOQL/DAL joint Session - Tuesday afternoon 16:00-17:30 | ||||||||||
> > | VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30 | ||||||||||
Changed: | |||||||||||
< < | In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the IvoaVOQL-1 sesion (see the presentation) on the future Table Access Protocol. | ||||||||||
> > | In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the VOQL-1 sesion (see the presentation) on the future Table Access Protocol. | ||||||||||
Roadmap | |||||||||||
Changed: | |||||||||||
< < | It is not easy to predict at this stage the possible roadmap for the IvoaVOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so: | ||||||||||
> > | It is not easy to predict at this stage the possible roadmap for the VOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so: | ||||||||||
| |||||||||||
Changed: | |||||||||||
< < | | ||||||||||
> > | | ||||||||||
the TAP | |||||||||||
Changed: | |||||||||||
< < | | ||||||||||
> > | | ||||||||||
|
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006 | |||||||||||
Changed: | |||||||||||
< < | VO Query Language (VOQL) Sessions | ||||||||||
> > | VO Query Language (IvoaVOQL) Sessions | ||||||||||
Open Plenary sessionThe Open Plenary session slides can be found here | |||||||||||
Changed: | |||||||||||
< < | VOQL-1 Session - Tuesday morning 11:00-12:30 | ||||||||||
> > | IvoaVOQL-1 Session - Tuesday morning 11:00-12:30 | ||||||||||
Minutes of the session (notes by J. Salgado) | |||||||||||
Changed: | |||||||||||
< < | Future work for the VOQL groupThe main idea in the new direction of the VOQL group is to sepaerate the language | ||||||||||
> > | Future work for the IvoaVOQL groupThe main idea in the new direction of the IvoaVOQL group is to sepaerate the language | ||||||||||
from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. | |||||||||||
Changed: | |||||||||||
< < | To try to remove these incompatibilities, the VOQL group has decided to separate | ||||||||||
> > | To try to remove these incompatibilities, the IvoaVOQL group has decided to separate | ||||||||||
completely languag and access, and work consequently in the following three
areas:
| |||||||||||
Changed: | |||||||||||
< < | | ||||||||||
> > | | ||||||||||
| |||||||||||
Changed: | |||||||||||
< < | The first two will be dealt by the VOQL group directly. The third one will | ||||||||||
> > | The first two will be dealt by the IvoaVOQL group directly. The third one will | ||||||||||
be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. | |||||||||||
Changed: | |||||||||||
< < | We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all | ||||||||||
> > | We have created a IvoaVOQL Technical Experts Group (IvoaVOQL-TEG) to deal with all | ||||||||||
the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. | |||||||||||
Changed: | |||||||||||
< < | The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes | ||||||||||
> > | The IvoaVOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes | ||||||||||
of the discussions within the group will be fed to the community periodically,
to get proper feedback.
An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
| |||||||||||
Changed: | |||||||||||
< < | VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30 | ||||||||||
> > | IvoaVOQL/DAL joint Session - Tuesday afternoon 16:00-17:30 | ||||||||||
Changed: | |||||||||||
< < | In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the VOQL-1 sesion (see the presentation) on the future Table Access Protocol. | ||||||||||
> > | In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the IvoaVOQL-1 sesion (see the presentation) on the future Table Access Protocol. | ||||||||||
Roadmap | |||||||||||
Changed: | |||||||||||
< < | It is not easy to predict at this stage the possible roadmap for the VOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so: | ||||||||||
> > | It is not easy to predict at this stage the possible roadmap for the IvoaVOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so: | ||||||||||
| |||||||||||
Changed: | |||||||||||
< < | | ||||||||||
> > | | ||||||||||
the TAP | |||||||||||
Changed: | |||||||||||
< < | | ||||||||||
> > | | ||||||||||
<--
|
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006VO Query Language (VOQL) SessionsOpen Plenary sessionThe Open Plenary session slides can be found hereVOQL-1 Session - Tuesday morning 11:00-12:30 | |||||||||
Changed: | |||||||||
< < | Minutes of the session (notes by J. Salgado) | ||||||||
> > | Minutes of the session (notes by J. Salgado) | ||||||||
Future work for the VOQL groupThe main idea in the new direction of the VOQL group is to sepaerate the language from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. To try to remove these incompatibilities, the VOQL group has decided to separate completely languag and access, and work consequently in the following three areas:
The first two will be dealt by the VOQL group directly. The third one will be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes of the discussions within the group will be fed to the community periodically, to get proper feedback. An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the VOQL-1 sesion (see the presentation) on the future Table Access Protocol.RoadmapIt is not easy to predict at this stage the possible roadmap for the VOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so:
<--
| |||||||||
Added: | |||||||||
> > |
| ||||||||
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006VO Query Language (VOQL) SessionsOpen Plenary sessionThe Open Plenary session slides can be found hereVOQL-1 Session - Tuesday morning 11:00-12:30 | ||||||||
Added: | ||||||||
> > | Minutes of the session (notes by J. Salgado) | |||||||
Future work for the VOQL groupThe main idea in the new direction of the VOQL group is to sepaerate the language from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. To try to remove these incompatibilities, the VOQL group has decided to separate completely languag and access, and work consequently in the following three areas:
The first two will be dealt by the VOQL group directly. The third one will be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes of the discussions within the group will be fed to the community periodically, to get proper feedback. An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the VOQL-1 sesion (see the presentation) on the future Table Access Protocol.RoadmapIt is not easy to predict at this stage the possible roadmap for the VOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so:
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006VO Query Language (VOQL) SessionsOpen Plenary sessionThe Open Plenary session slides can be found hereVOQL-1 Session - Tuesday morning 11:00-12:30Future work for the VOQL groupThe main idea in the new direction of the VOQL group is to sepaerate the language from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. To try to remove these incompatibilities, the VOQL group has decided to separate completely languag and access, and work consequently in the following three areas:
The first two will be dealt by the VOQL group directly. The third one will be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes of the discussions within the group will be fed to the community periodically, to get proper feedback. An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30 | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | ||||||||
In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the VOQL-1 sesion (see the presentation) on the future Table Access Protocol.
Roadmap | ||||||||
Added: | ||||||||
> > | It is not easy to predict at this stage the possible roadmap for the VOQL group, in view of the new structure and documents that the group will be preparing. The following, nevertheless, is an attempt to do so:
| |||||||
<--
|
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006VO Query Language (VOQL) SessionsOpen Plenary sessionThe Open Plenary session slides can be found hereVOQL-1 Session - Tuesday morning 11:00-12:30Future work for the VOQL groupThe main idea in the new direction of the VOQL group is to sepaerate the language from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. To try to remove these incompatibilities, the VOQL group has decided to separate completely languag and access, and work consequently in the following three areas:
The first two will be dealt by the VOQL group directly. The third one will be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes of the discussions within the group will be fed to the community periodically, to get proper feedback. An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30
| ||||||||
Added: | ||||||||
> > | In this session, Ray Plante presented the outcomes from an NVO meeting where they discussed on possible inputs for an eventual Table Access Protocol. A lot of commonalities and only a few of possible discrepancies where clearly shown with respect to the ideas shown in the VOQL-1 sesion (see the presentation) on the future Table Access Protocol. | |||||||
Roadmap | ||||||||
Deleted: | ||||||||
< < | VOQL Group future activities | |||||||
Deleted: | ||||||||
< < | ||||||||
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006VO Query Language (VOQL) Sessions | ||||||||
Changed: | ||||||||
< < | Schedule | |||||||
> > | Open Plenary session | |||||||
Added: | ||||||||
> > | The Open Plenary session slides can be found here | |||||||
Deleted: | ||||||||
< < | ||||||||
VOQL-1 Session - Tuesday morning 11:00-12:30 | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > | Future work for the VOQL group | |||||||
Added: | ||||||||
> > | The main idea in the new direction of the VOQL group is to sepaerate the language from the access. There has currently been an intermingling of specifications that were mixing the Language (ADQL) with the access (SkyNode). The impossibility to separate one from the other was leading to inconsistencies in both the language and the access. To try to remove these incompatibilities, the VOQL group has decided to separate completely languag and access, and work consequently in the following three areas:
The first two will be dealt by the VOQL group directly. The third one will be worked on, probably in relation to the TAP research. It is still not clear in which IVOA group this one should follow. We have created a VOQL Technical Experts Group (VOQL-TEG) to deal with all the aforementioned issues, in the definition of the standards as well as in the construction of reference implementations, and/or tools necessary to widespread the VO Query Language and applied uses. The VOQL-TEG will meet regularly (normally by teleconference) and the aoutcomes of the discussions within the group will be fed to the community periodically, to get proper feedback. An e-mail distribution list will be created for the reduced group, and the mails will be archived as usual at the IVOA pages.
| |||||||
Added: | ||||||||
> > | ||||||||
VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30
| ||||||||
Added: | ||||||||
> > | Roadmap | |||||||
Added: | ||||||||
> > | VOQL Group future activities | |||||||
Deleted: | ||||||||
< < | ||||||||
<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
IVOA Interoperability MeetingMoscow, Russia, 18-20 September 2006VO Query Language (VOQL) SessionsScheduleVOQL-1 Session - Tuesday morning 11:00-12:30
VOQL/DAL joint Session - Tuesday afternoon 16:00-17:30
<--
|