IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGStandards and Related
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgrades Pending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution project The GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms.
https://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisation Identify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible. Execution interface Identify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control execution Credentials Delegation Review of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...) Plan for 2023: - Update Execution Planner note to convert it to a formal draft, including a more complex definition - Draft for November meeting - Study on workflow standards - Draft for November meeting
Registry WG
Semantics WG
Data Curation Preservation IG
Education IG2023
Knowledge Discovery IG
Operations IGOngoing activity:
Radio IG | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Solar System IG
Theory IGTime Domain IGPriority in this first semester is to review status of recommendation level and working draft level documents of relevance for time domain, and decide on priorities based on current status of the field of time domain astrophysics. In particular, upcoming surveys (LSST, LIGO) and the increase number of transient alerts across wavelengths (including high energy transients, of relevance in multi-messenger science), as well as the emergence of spectral time-domain surveys, such SDSS-V, set the following priorities:
Standard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> | ||||||||
Deleted: | ||||||||
< < |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Applications WGStandards and Related
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgrades Pending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution project The GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms.
| ||||||||
Changed: | ||||||||
< < | https://wiki.ivoa.net/twiki/bin/view/IVOA/ComputingServicesAPI | |||||||
> > | https://wiki.ivoa.net/twiki/bin/view/IVOA/ComputingServicesAPI | |||||||
The preliminary items to be analysed are: Execution planner | ||||||||
Changed: | ||||||||
< < | Currently, a note has been prepared at https://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. | |||||||
> > | Currently, a note has been prepared at https://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. | |||||||
Endorsement of a standard for workflow serialisation
Identify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.
Execution interface
Identify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control execution
Credentials Delegation
Review of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies
For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)
Plan for 2023: - Update Execution Planner note to convert it to a formal draft, including a more complex definition - Draft for November meeting - Study on workflow standards - Draft for November meeting
Registry WG
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Semantics WG
Data Curation Preservation IG | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
Education IG2023
Knowledge Discovery IG
Operations IGOngoing activity:
Radio IG
Solar System IG
Theory IGTime Domain IGPriority in this first semester is to review status of recommendation level and working draft level documents of relevance for time domain, and decide on priorities based on current status of the field of time domain astrophysics. In particular, upcoming surveys (LSST, LIGO) and the increase number of transient alerts across wavelengths (including high energy transients, of relevance in multi-messenger science), as well as the emergence of spectral time-domain surveys, such SDSS-V, set the following priorities:
Standard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGStandards and Related
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WG | ||||||||
Deleted: | ||||||||
< < | Pending upgrades | |||||||
Added: | ||||||||
> > | Pending upgrades | |||||||
Pending Update SSO 2.1, including issues at: https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. | ||||||||
Deleted: | ||||||||
< < | Cross-science platforms execution project | |||||||
Changed: | ||||||||
< < | The GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are: | |||||||
> > | Cross-science platforms execution project | |||||||
Deleted: | ||||||||
< < | Execution planner | |||||||
Added: | ||||||||
> > | The GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms.
| |||||||
Currently, a note has been prepared at https://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. | ||||||||
Deleted: | ||||||||
< < | Endorsement of a standard for workflow serialisation | |||||||
Added: | ||||||||
> > | Endorsement of a standard for workflow serialisation | |||||||
Identify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible. | ||||||||
Deleted: | ||||||||
< < | Execution interface | |||||||
Added: | ||||||||
> > | Execution interface | |||||||
Identify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control execution | ||||||||
Deleted: | ||||||||
< < | Credentials Delegation | |||||||
Added: | ||||||||
> > | Credentials Delegation | |||||||
Review of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | Plan for 2023: - Update Execution Planner note to convert it to a formal draft, including a more complex definition - Draft for November meeting - Study on workflow standards - Draft for November meeting | |||||||
Registry WG
Semantics WG
Data Curation Preservation IGEducation IG2023
Knowledge Discovery IG
Operations IGOngoing activity:
Radio IG
Solar System IG
Theory IGTime Domain IGPriority in this first semester is to review status of recommendation level and working draft level documents of relevance for time domain, and decide on priorities based on current status of the field of time domain astrophysics. In particular, upcoming surveys (LSST, LIGO) and the increase number of transient alerts across wavelengths (including high energy transients, of relevance in multi-messenger science), as well as the emergence of spectral time-domain surveys, such SDSS-V, set the following priorities:
Standard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> | ||||||||
Added: | ||||||||
> > |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGStandards and Related
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG
Semantics WG
Data Curation Preservation IGEducation IG2023
Knowledge Discovery IG
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Operations IGOngoing activity:
Radio IG
Solar System IG
Theory IGTime Domain IGPriority in this first semester is to review status of recommendation level and working draft level documents of relevance for time domain, and decide on priorities based on current status of the field of time domain astrophysics. In particular, upcoming surveys (LSST, LIGO) and the increase number of transient alerts across wavelengths (including high energy transients, of relevance in multi-messenger science), as well as the emergence of spectral time-domain surveys, such SDSS-V, set the following priorities:
Standard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Applications WGStandards and Related
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG
Semantics WG
Data Curation Preservation IGEducation IG2023 | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | * How to join WGs (turn up to the Session, subscribe to mail list...) * How to join a mail list * Explain how the working groups work together at the example of a specific topic of the running interop. * One question raised was that the established IVOA people seem to be friends, which makes it harder for newcomers to fit in. This might be influenced by Bologna being the first in person meeting after 3.5 years. Yet, maybe it's possible that we have a handful of volunteers who would attend the newcomers session and introduce themselves | |||||||
Knowledge Discovery IG
Operations IGOngoing activity:
Radio IG
Solar System IG
Theory IGTime Domain IG | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | Priority in this first semester is to review status of recommendation level and working draft level documents of relevance for time domain, and decide on priorities based on current status of the field of time domain astrophysics. In particular, upcoming surveys (LSST, LIGO) and the increase number of transient alerts across wavelengths (including high energy transients, of relevance in multi-messenger science), as well as the emergence of spectral time-domain surveys, such SDSS-V, set the following priorities: | |||||||
Added: | ||||||||
> > |
| |||||||
Standard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGStandards and Related
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG
Semantics WG
Data Curation Preservation IGEducation IG2023
Knowledge Discovery IG | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
Operations IGOngoing activity:
Radio IG
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WG | ||||||||
Added: | ||||||||
> > | Standards and Related
| |||||||
Data Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG
Semantics WG
Data Curation Preservation IGEducation IG2023
Knowledge Discovery IGOperations IG | ||||||||
Changed: | ||||||||
< < | Ongoing activity:
| |||||||
> > | Ongoing activity:
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | Specific focus:
| |||||||
> > | Specific focus:
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Radio IG
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG
Semantics WG
Data Curation Preservation IGEducation IG2023
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
2024/2025
Knowledge Discovery IGOperations IG | ||||||||
Added: | ||||||||
> > | Ongoing activity:
| |||||||
Radio IG
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG | ||||||||
Deleted: | ||||||||
< < | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Semantics WG
| ||||||||
Deleted: | ||||||||
< < | ||||||||
Data Curation Preservation IGEducation IG | ||||||||
Added: | ||||||||
> > |
2023
| |||||||
Knowledge Discovery IGOperations IGRadio IG
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG
Semantics WG
Data Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> | ||||||||
Deleted: | ||||||||
< < |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WG | ||||||||
Added: | ||||||||
> > |
| |||||||
Semantics WG
Data Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGPrimary: Spectrum 1.2 RFE:
Grid and Web Services WGPending upgradesPending Update SSO 2.1, including issues at:https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WGSemantics WG | ||||||||
Added: | ||||||||
> > |
| |||||||
Data Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG
Solar System IG
Theory IGTime Domain IGStandard and Processes<!--* Set ALLOWTOPICRENAME = TWikiAdminGroup --> | ||||||||
Added: | ||||||||
> > |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WG | ||||||||
Added: | ||||||||
> > | Primary:
Spectrum 1.2 RFE:
| |||||||
Grid and Web Services WG | ||||||||
Changed: | ||||||||
< < | Pending upgrades | |||||||
> > | Pending upgrades | |||||||
Pending Update SSO 2.1, including issues at: https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...)Registry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Solar System IG
Theory IGTime Domain IGStandard and Processes | ||||||||
Changed: | ||||||||
< < | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> | |||||||
> > | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGGrid and Web Services WG | ||||||||
Added: | ||||||||
> > | Pending upgrades | |||||||
Added: | ||||||||
> > | Pending Update SSO 2.1, including issues at: https://github.com/ivoa-std/SSO/issues Also, reformat of GitHub repository. Cross-science platforms execution projectThe GWS WG is going to start a project to identify the main changes and new standards to allow remote execution on different astronomical science platforms. The preliminary items to be analysed are:Execution plannerCurrently, a note has been prepared athttps://github.com/ivoa/ExecutionPlannerNote This note should be either converted into a standard or, at least, upgraded making it a more powerful interface. To do that, it is necessary to standardise: Characterisation of software (in terms not only of software dependencies but, also, dependencies that could affect execution like memory, requirements on computing architecture (e.g. CPUs and GPUs), data location, etc. Software should be exposed in a portable format Metadata characterisation of the science platform node is also a requirement Access to this metadata should be also characterised as per the definition of a software discovery service and a science platform resources discovery service. The execution planner could use metadata of both types to decide the best place to execute a certain workflow. For the software characterisation and discovery, other CI/CD solutions could be expanded and already have the connections between code and containers. For the science platform node service, we need to have a dynamic service to capture the real-time status of the resources. The execution planner and the science platform discovery service could be integrated into the same service and the software discovery looks to be a different one. Endorsement of a standard for workflow serialisationIdentify one standard for workflow serialisation (e.g. CWL) and endorse it for the IVOA. This format should have software to parse and decompose a workflow in smaller executable elements in different languages if possible.Execution interfaceIdentify an execution interface that could abstract the internal execution interfaces of the different science platforms. Probably something based on IVOA UWS could be used to control executionCredentials DelegationReview of related standards for authentication/authorisation combined with the execution interface. This could be a problem for a general approach as some computing centres have their local access policies For this exercise, SKA Regional Centre Network members are available to collaborate, lead and implement although it would be also needed to have members of other projects that are implementing (or already have) running science platforms to create another independent implementation (candidates Vera Rubin, ESA, CADC, Gaia UK,...) | |||||||
Registry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | recent progress and additional implementations (projects such as NRAO, GBT, SKA, IRAM, SpanifhVO, etc...) | |||||||
Solar System IG
Theory IGTime Domain IGStandard and Processes | ||||||||
Changed: | ||||||||
< < |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | * revision of existing text * addition of projects such as NRAO, GBT, SKA, IRAM, SpanifhVO, etc... | |||||||
> > | recent progress and additional implementations (projects such as NRAO, GBT, SKA, IRAM, SpanifhVO, etc...)
| |||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
Solar System IG
Theory IGTime Domain IGStandard and Processes<--
|
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
LineTAP
Data Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IG | ||||||||
Added: | ||||||||
> > |
| |||||||
Solar System IG
Theory IGTime Domain IGStandard and Processes<--
|
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGPrimary:ADQL
| ||||||||
Added: | ||||||||
> > |
| |||||||
SODA 1.1
| ||||||||
Added: | ||||||||
> > |
| |||||||
Secondary LineTAP
Data Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IGSolar System IG
Theory IGTime Domain IGStandard and Processes<--
|
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WG | ||||||||
Added: | ||||||||
> > | Primary: ADQL
LineTAP
| |||||||
Data Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IGSolar System IG
Theory IGTime Domain IGStandard and Processes<--
| ||||||||
Deleted: | ||||||||
< < |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGData Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGKnowledge Discovery IGOperations IGRadio IGSolar System IG | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
Theory IGTime Domain IGStandard and Processes<--
| ||||||||
Added: | ||||||||
> > |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Deleted: | ||||||||
< < | ||||||||
Applications WGData Access Layer WGData Model WG | ||||||||
Added: | ||||||||
> > | ||||||||
Grid and Web Services WG | ||||||||
Added: | ||||||||
> > | ||||||||
Registry WGSemantics WGData Curation Preservation IGEducation IG | ||||||||
Added: | ||||||||
> > | Knowledge Discovery IG | |||||||
Operations IGRadio IGSolar System IGTheory IGTime Domain IGStandard and Processes | ||||||||
Deleted: | ||||||||
< < | ||||||||
<--
|
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Applications WGData Access Layer WGData Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGOperations IGRadio IGSolar System IGTheory IGTime Domain IGStandard and Processes<--
| ||||||||
Deleted: | ||||||||
< < |
IVOA Roadmap for 2023AThis outlines the roadmap for development activities by the various IVOA working and interest groups between the May 2023 and Nov 2023 Interops.Applications WGData Access Layer WGData Model WGGrid and Web Services WGRegistry WGSemantics WGData Curation Preservation IGEducation IGOperations IGRadio IGSolar System IGTheory IGTime Domain IGStandard and Processes<--
|