Difference: 2014ARoadmap (1 vs. 11)
Revision 112021-04-13 - GiuliaIafrate
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data Model | ||||||||
| Changed: | ||||||||
| < < | PhotDM 1.0 | |||||||
| > > | PhotDMv1-1 1.0 | |||||||
| TCG was recommendation on October 2013 | ||||||||
| Changed: | ||||||||
| < < | PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach | |||||||
| > > | PhotDMv1-1 will be adapted at certain point (October 2014 interop?) following VO-DML approach | |||||||
Spectral DM 2.0
"Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014
Characterization DM 2.0
Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop.
Changes done to be presented during Spring 2014 (technical support)
Image DM
Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop
VO-DML
Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops
Stable/final version distributed to WG before Spring 2014 interop
Grid and Web Sevices* PDL:
RegistryRegTAP We will integrate the feedback from RFC into the RegTAP PR and circulate it for TCG review. Although the list of changes after RFC was fairly substantial, most of the changes were actually clarifications for fringe cases. We hope to have RegTAP ready for REC by Banff. There are now about four implementations of RegTAP. We plan to have them all pass the validation suite by Banff. Registry Interface and RegTAP With RegTAP becoming REC, the Registry Interfaces document will need revision. There is a working draft on volute that retains the standard OAI protocol for harvesting from publishing registries, but it will remove the search capabilities and instead refer to standards like RegTAP and a planned simple REST registry interface. VOEventRegExt While the actual authoring a registry extension for VOEvents, VOEventRegExt, is in the hands of GWS, RWG will continue to work closely with the authors. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Identifiers We plan to issue an essentially minor update of the Identifiers recommendation; it will remove the obsolte XML form of identifiers and add text on the recommended forms for standard and dataset identifiers. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. The RWG also keeps monitoring the health of the registry system as a whole, working with the operators of the publishing registries to resolve problems as they crop up. -- MarkusDemleitner - 2014-06-26SemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document. Status after mai InterOp SimDAL has been presented by David Languignon at the may InterOp at ESAC and has been discussed during two sessions. A general agreement has been found on what has been presented : http://wiki.ivoa.net/internal/IVOA/InterOpMay2014Theory/InterOpESAC14_Theory_SimDAL.pdf Now, planning is : 1) discuss with Registry W.G. to identify possible overlaps / complementarities between SimDAL repository and registries 2) try to prepare a first version of a WD for next InterOp on some parts of the SimDAL standard (depends on the available time of David Languignon) 3) continue implementations in France, Spain, Italy on various services.EducationEdu IG prompted the development of VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas. Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy. Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers. -- MassimoRamellaINAF - 2014-05-18Time DomainA note endorsing the use of SimpleTimeSeries for representing time series data within the context of the VO was issued in May 2014. When the new version of the Document Standards defines the appropriate procedure, this note will be put forward for approval by the TCG. An advanced working draft of VOEventRegExt was issued in May 2014. At the May 2014 InterOp, the TDIG agreed to advance this to PR status (as soon as a few minor formatting issues are resolved). We have now received additional feedback from Registry WG members, and are considering a further revision of this document. A PR is expected to follow shortly. An advanced draft of the VOEvent Transport Protocol was issued in May 2014. This draft will undergo a further round of discussion within the TDIG before advancing to PR. We expect it to be ready for PR mid-2014. -- JohnSwinbank - 2014-06-16Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 102018-06-20 - GiuliaIafrate
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistryRegTAP We will integrate the feedback from RFC into the RegTAP PR and circulate it for TCG review. Although the list of changes after RFC was fairly substantial, most of the changes were actually clarifications for fringe cases. We hope to have RegTAP ready for REC by Banff. There are now about four implementations of RegTAP. We plan to have them all pass the validation suite by Banff. Registry Interface and RegTAP With RegTAP becoming REC, the Registry Interfaces document will need revision. There is a working draft on volute that retains the standard OAI protocol for harvesting from publishing registries, but it will remove the search capabilities and instead refer to standards like RegTAP and a planned simple REST registry interface. VOEventRegExt While the actual authoring a registry extension for VOEvents, VOEventRegExt, is in the hands of GWS, RWG will continue to work closely with the authors. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Identifiers We plan to issue an essentially minor update of the Identifiers recommendation; it will remove the obsolte XML form of identifiers and add text on the recommended forms for standard and dataset identifiers. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. The RWG also keeps monitoring the health of the registry system as a whole, working with the operators of the publishing registries to resolve problems as they crop up. -- MarkusDemleitner - 2014-06-26SemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 | ||||||||
| Changed: | ||||||||
| < < | Data Curation & Preservation | |||||||
| > > | Data Curation & Preservation | |||||||
The IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document. Status after mai InterOp SimDAL has been presented by David Languignon at the may InterOp at ESAC and has been discussed during two sessions. A general agreement has been found on what has been presented : http://wiki.ivoa.net/internal/IVOA/InterOpMay2014Theory/InterOpESAC14_Theory_SimDAL.pdf Now, planning is : 1) discuss with Registry W.G. to identify possible overlaps / complementarities between SimDAL repository and registries 2) try to prepare a first version of a WD for next InterOp on some parts of the SimDAL standard (depends on the available time of David Languignon) 3) continue implementations in France, Spain, Italy on various services.EducationEdu IG prompted the development of VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas. Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy. Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers. -- MassimoRamellaINAF - 2014-05-18Time DomainA note endorsing the use of SimpleTimeSeries for representing time series data within the context of the VO was issued in May 2014. When the new version of the Document Standards defines the appropriate procedure, this note will be put forward for approval by the TCG. An advanced working draft of VOEventRegExt was issued in May 2014. At the May 2014 InterOp, the TDIG agreed to advance this to PR status (as soon as a few minor formatting issues are resolved). We have now received additional feedback from Registry WG members, and are considering a further revision of this document. A PR is expected to follow shortly. An advanced draft of the VOEvent Transport Protocol was issued in May 2014. This draft will undergo a further round of discussion within the TDIG before advancing to PR. We expect it to be ready for PR mid-2014. -- JohnSwinbank - 2014-06-16Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 92014-06-26 - MarkusDemleitner
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
Registry | ||||||||
| Changed: | ||||||||
| < < | SimpleDALRegExt 1.0 | |||||||
| > > | RegTAP | |||||||
| Changed: | ||||||||
| < < | SimpleDALRegExt has become a REC. | |||||||
| > > | We will integrate the feedback from RFC into the RegTAP PR and circulate | |||||||
| Added: | ||||||||
| > > | it for TCG review. Although the list of changes after RFC was fairly substantial, most of the changes were actually clarifications for fringe cases. We hope to have RegTAP ready for REC by Banff. | |||||||
| Changed: | ||||||||
| < < | VOEventRegExt | |||||||
| > > | There are now about four implementations of RegTAP. We plan to have | |||||||
| Added: | ||||||||
| > > | them all pass the validation suite by Banff. | |||||||
| Deleted: | ||||||||
| < < | In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. | |||||||
| Registry Interface and RegTAP | ||||||||
| Changed: | ||||||||
| < < | The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. | |||||||
| > > | With RegTAP becoming REC, the Registry Interfaces document will need | |||||||
| Added: | ||||||||
| > > | revision. There is a working draft on volute that retains the standard OAI protocol for harvesting from publishing registries, but it will remove the search capabilities and instead refer to standards like RegTAP and a planned simple REST registry interface. | |||||||
| Added: | ||||||||
| > > | VOEventRegExt While the actual authoring a registry extension for VOEvents, VOEventRegExt, is in the hands of GWS, RWG will continue to work closely with the authors. | |||||||
| An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints | ||||||||
| Changed: | ||||||||
| < < | The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. | |||||||
| > > | The RWG will continue to have discussions and evolve the current | |||||||
| Added: | ||||||||
| > > | standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. | |||||||
| Added: | ||||||||
| > > | Identifiers We plan to issue an essentially minor update of the Identifiers recommendation; it will remove the obsolte XML form of identifiers and add text on the recommended forms for standard and dataset identifiers. | |||||||
| Registry Operations and Curation | ||||||||
| Changed: | ||||||||
| < < | The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. | |||||||
| > > | The Registry WG continues to drive regular discussions during | |||||||
| Added: | ||||||||
| > > | Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. | |||||||
| Changed: | ||||||||
| < < | -- GretchenGreene - 12 February 2014 last update | |||||||
| > > | The RWG also keeps monitoring the health of the registry | |||||||
| Added: | ||||||||
| > > | system as a whole, working with the operators of the publishing registries to resolve problems as they crop up. -- MarkusDemleitner - 2014-06-26 | |||||||
SemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document. Status after mai InterOp SimDAL has been presented by David Languignon at the may InterOp at ESAC and has been discussed during two sessions. A general agreement has been found on what has been presented : http://wiki.ivoa.net/internal/IVOA/InterOpMay2014Theory/InterOpESAC14_Theory_SimDAL.pdf Now, planning is : 1) discuss with Registry W.G. to identify possible overlaps / complementarities between SimDAL repository and registries 2) try to prepare a first version of a WD for next InterOp on some parts of the SimDAL standard (depends on the available time of David Languignon) 3) continue implementations in France, Spain, Italy on various services.EducationEdu IG prompted the development of VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas. Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy. Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers. -- MassimoRamellaINAF - 2014-05-18Time DomainA note endorsing the use of SimpleTimeSeries for representing time series data within the context of the VO was issued in May 2014. When the new version of the Document Standards defines the appropriate procedure, this note will be put forward for approval by the TCG. An advanced working draft of VOEventRegExt was issued in May 2014. At the May 2014 InterOp, the TDIG agreed to advance this to PR status (as soon as a few minor formatting issues are resolved). We have now received additional feedback from Registry WG members, and are considering a further revision of this document. A PR is expected to follow shortly. An advanced draft of the VOEvent Transport Protocol was issued in May 2014. This draft will undergo a further round of discussion within the TDIG before advancing to PR. We expect it to be ready for PR mid-2014. -- JohnSwinbank - 2014-06-16Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 82014-06-16 - JohnSwinbank
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
| ||||||||
| Changed: | ||||||||
| < < |  | |||||||
| > > | | |||||||
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document. Status after mai InterOp SimDAL has been presented by David Languignon at the may InterOp at ESAC and has been discussed during two sessions. A general agreement has been found on what has been presented : http://wiki.ivoa.net/internal/IVOA/InterOpMay2014Theory/InterOpESAC14_Theory_SimDAL.pdf Now, planning is : 1) discuss with Registry W.G. to identify possible overlaps / complementarities between SimDAL repository and registries 2) try to prepare a first version of a WD for next InterOp on some parts of the SimDAL standard (depends on the available time of David Languignon) | ||||||||
| Changed: | ||||||||
| < < | 3) continue implementations in France, Spain, Italy on various services. | |||||||
| > > | 3) continue implementations in France, Spain, Italy on various services. | |||||||
EducationEdu IG prompted the development of VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas. Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy. Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers. -- MassimoRamellaINAF - 2014-05-18Time Domain | ||||||||
| Changed: | ||||||||
| < < | The TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. | |||||||
| > > | A note endorsing the use of SimpleTimeSeries for representing time series data within the context of the VO was issued in May 2014. When the new version of the Document Standards defines the appropriate procedure, this note will be put forward for approval by the TCG. | |||||||
| Changed: | ||||||||
| < < | -- MatthewGraham - 2013-05-09 | |||||||
| > > | An advanced working draft of VOEventRegExt was issued in May 2014. At the May 2014 InterOp, the TDIG agreed to advance this to PR status (as soon as a few minor formatting issues are resolved). We have now received additional feedback from Registry WG members, and are considering a further revision of this document. A PR is expected to follow shortly. | |||||||
| Changed: | ||||||||
| < < | -- JohnSwinbank - 2014-02-11 | |||||||
| > > | An advanced draft of the VOEvent Transport Protocol was issued in May 2014. This draft will undergo a further round of discussion within the TDIG before advancing to PR. We expect it to be ready for PR mid-2014. | |||||||
| Added: | ||||||||
| > > | -- JohnSwinbank - 2014-06-16 | |||||||
Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 72014-06-03 - FranckLePetit
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document. | ||||||||
| Added: | ||||||||
| > > | Status after mai InterOp SimDAL has been presented by David Languignon at the may InterOp at ESAC and has been discussed during two sessions. A general agreement has been found on what has been presented : http://wiki.ivoa.net/internal/IVOA/InterOpMay2014Theory/InterOpESAC14_Theory_SimDAL.pdf Now, planning is : 1) discuss with Registry W.G. to identify possible overlaps / complementarities between SimDAL repository and registries 2) try to prepare a first version of a WD for next InterOp on some parts of the SimDAL standard (depends on the available time of David Languignon) 3) continue implementations in France, Spain, Italy on various services. | |||||||
EducationEdu IG prompted the development of VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas. Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy. Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers. -- MassimoRamellaINAF - 2014-05-18Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 62014-05-20 - MassimoRamellaINAF
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document.Education | ||||||||
| Changed: | ||||||||
| < < | Edu IG is developing VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. | |||||||
| > > | Edu IG prompted the development of VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. | |||||||
A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas.
Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy.
Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers.
-- MassimoRamellaINAF - 2014-05-18
Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 52014-05-18 - MassimoRamellaINAF
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document.Education | ||||||||
| Changed: | ||||||||
| < < | EduIG is developing VESPA, a web procedure that offers educational telescopes the possibility of an easy publication of a service and of data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified but VESPA is required to deal also with SSAP beside the already implemented SIAP. | |||||||
| > > | Edu IG is developing VESPA (VO Educational Service Publisher and Archive), a web procedure offering managers of educational telescopes the possibility of an easy publication of their data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified, but the user requires VESPA to implement SSAP beside the already implemented SIAP. | |||||||
| Changed: | ||||||||
| < < | -- MassimoRamellaINAF - 2013-03-25 | |||||||
| > > | A related task for Edu IG is to propose solutions and desirables for the curation of educational resources inside or along standard registries. Most of the relevant aspects of this task are the subject of a Note available in the Edu IG page Ideas. | |||||||
| Added: | ||||||||
| > > | Education is a field where the localization of documents in different languages is essential. There is no immediate solution to this problem but we plan to start developing ideas and strategies in order to tackle it. The already mentioned Note on Educational Resources already considers the existence of multilingual documents and their hierarchy. Edu IG continues to collect desiderata and ideas from educators and the general public and to propose them to VO, possibly leading to an even wider diffusion of VO resources toward communities other than professional astronomers. -- MassimoRamellaINAF - 2014-05-18 | |||||||
Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 42014-05-18 - MassimoRamellaINAF
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document.Education | ||||||||
| Changed: | ||||||||
| < < | The newly formed Edu IG is planning to discuss its Roadmap during the Heidelberg 2013 Interop. The basis for the discussion are the Terms of Reference that can be read in the IG's web page together with the Rationale. At the Heidelberg Interop, the Edu IG will have both a morning and an afternoon session on Thursday May 16. At least one of the two sessions will be devoted to discussions of the Roadmap and its implementation. Contributions from anybody interested will be most welcome. | |||||||
| > > | EduIG is developing VESPA, a web procedure that offers educational telescopes the possibility of an easy publication of a service and of data in the VO. At the moment VESPA is an advanced prototype which we plan to develop into an official first version before the next interop meeting. In order to do so we need to test the application with a real interested user. The user has already been identified but VESPA is required to deal also with SSAP beside the already implemented SIAP. | |||||||
-- MassimoRamellaINAF - 2013-03-25
Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11Standard and ProcessesA new version of the Document Standards is foreseen in 2014 to:
| ||||||||
| Deleted: | ||||||||
| < < | ||||||||
-- FrancoiseGenova - 2014-05-18
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 32014-05-18 - FrancoiseGenova
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG was recommendation on October 2013 PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Changes done to be presented during Spring 2014 (technical support) Image DM Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop VO-DML Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops Stable/final version distributed to WG before Spring 2014 interopGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document.EducationThe newly formed Edu IG is planning to discuss its Roadmap during the Heidelberg 2013 Interop. The basis for the discussion are the Terms of Reference that can be read in the IG's web page together with the Rationale. At the Heidelberg Interop, the Edu IG will have both a morning and an afternoon session on Thursday May 16. At least one of the two sessions will be devoted to discussions of the Roadmap and its implementation. Contributions from anybody interested will be most welcome. -- MassimoRamellaINAF - 2013-03-25Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11 | ||||||||
| Added: | ||||||||
| > > | ||||||||
Standard and Processes | ||||||||
| Changed: | ||||||||
| < < | No evolution of the standards forseen in 2013. | |||||||
| > > | A new version of the Document Standards is foreseen in 2014 to: | |||||||
| Added: | ||||||||
| > > |
| |||||||
Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 22014-05-18 - JesusSalgado
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
| ||||||||
| Changed: | ||||||||
| < < | | |||||||
| > > | | |||||||
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 | ||||||||
| Changed: | ||||||||
| < < | TCG review started on July 2012. | |||||||
| > > | TCG was recommendation on October 2013 | |||||||
| Changed: | ||||||||
| < < | Work stopped due to coupling with utypes Tiger Team work as PhotDM was intended to be in line with utypes recommendation. Process of adaptation to the ongoing discussions within Tiger Team. | |||||||
| > > | PhotDM will be adapted at certain point (October 2014 interop?) following VO-DML approach | |||||||
| Deleted: | ||||||||
| < < | It is decided (12/05/2013 TCG meeting) to decouple both activities, update PhotDM with the comments obtained during TCG review and encourage TCG members to comment on it (to be done before the end of Spring 2013 interop) PhotDM will be adapted for 2013 Autumn interop following VO-DML approach | |||||||
| Spectral DM 2.0 | ||||||||
| Changed: | ||||||||
| < < | "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process | |||||||
| > > | "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process, RFC process started May 2014 | |||||||
| Characterization DM 2.0 | ||||||||
| Changed: | ||||||||
| < < | Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Waiting green-light to start RFC process | |||||||
| > > | Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. | |||||||
| Added: | ||||||||
| > > | Changes done to be presented during Spring 2014 (technical support) | |||||||
| Image DM | ||||||||
| Changed: | ||||||||
| < < | Draft to be presented during Spring 2013 interop. Wider list of authors to be identified | |||||||
| > > | Presented during Spring 2013 interop. Connections with DAL. RFC to be started close to 2014 October interop | |||||||
| VO-DML | ||||||||
| Changed: | ||||||||
| < < | Draft to be presented during Spring 2013 interop. Prototypes and comments to be received between Spring and Autumn 2013 interops | |||||||
| > > | Draft presented during Spring 2013 interop. Prototypes and comments received between Spring nd Autumn 2013 interops | |||||||
| Added: | ||||||||
| > > | Stable/final version distributed to WG before Spring 2014 interop | |||||||
Grid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document.EducationThe newly formed Edu IG is planning to discuss its Roadmap during the Heidelberg 2013 Interop. The basis for the discussion are the Terms of Reference that can be read in the IG's web page together with the Rationale. At the Heidelberg Interop, the Edu IG will have both a morning and an afternoon session on Thursday May 16. At least one of the two sessions will be devoted to discussions of the Roadmap and its implementation. Contributions from anybody interested will be most welcome. -- MassimoRamellaINAF - 2013-03-25Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11Standard and ProcessesNo evolution of the standards forseen in 2013.Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
| ||||||||
Revision 12014-05-17 - MatthewGraham
IVOA Roadmap for 2014AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2014 between the Madrid and Banff Interops.Applications
Data Access Layer
The DAL roadmap is simplified to include the capabilities: DataLink, SIA query, SIA metadata (get-gory-details), and accessData (from DAL) as well as dependencies on the DM-WG for ObsCore and imageDM. We expect several versions of SIA-2.x and AccessData-1.x to be produced before all use cases are satisfied.
Data ModelPhotDM 1.0 TCG review started on July 2012. Work stopped due to coupling with utypes Tiger Team work as PhotDM was intended to be in line with utypes recommendation. Process of adaptation to the ongoing discussions within Tiger Team. It is decided (12/05/2013 TCG meeting) to decouple both activities, update PhotDM with the comments obtained during TCG review and encourage TCG members to comment on it (to be done before the end of Spring 2013 interop) PhotDM will be adapted for 2013 Autumn interop following VO-DML approach Spectral DM 2.0 "Trying to be final" version released to the working group in March 2013. No major comments received. To be presented to WG during Spring 2013 interop. Implementation pending to formally start RFC process Characterization DM 2.0 Stable version released to the working group in September 2012. No major comments received. Implementation to be presented during Spring 2013 interop. Waiting green-light to start RFC process Image DM Draft to be presented during Spring 2013 interop. Wider list of authors to be identified VO-DML Draft to be presented during Spring 2013 interop. Prototypes and comments to be received between Spring and Autumn 2013 interopsGrid and Web Sevices* PDL:
RegistrySimpleDALRegExt 1.0 SimpleDALRegExt has become a REC. VOEventRegExt In the context of VOEvent 2.0, a working draft of the VOEventRegExt is currently being finalized for metadata inputs with the VOEvent mailing list group. Matthew Graham is coordinating this effort. The RWG will participate in the RFC process to evaluate the specification in context of the registry standards integration. Registry Interface and RegTAP The RegistryInterface 2.0 (RI-2) working draft has been distributed to the RWG for review and is pending revisions for progression to the next phase for RFC. Our RWG goal for this standard is to move forward into the REC process following review and coordination during the May 2014 interop meeting. RI-2 will retain the standard OAI protocol for Publishing Registry and harvesting from the Publishing registry into the Fully Searchable Registry. This RI-2 standard will deprecate the the earlier SOAP interface support and provide 2 forms of web based REST interfaces, APIs, for the application client community: a TAP protocol based on the RegTAP relational registry model standard, and a SimpleRegREST interface. The later is the key to completion of this updated standard registry interface definition. A consolidated approach based on the integration of the Simple REST prototype via the EuroVO registry and VAO registry REST interface will be proposed. This standard RFC process is a high priority topic of discussion for the May 2014 interoperability meetings with direct impact to IVOA science application tool development that has registry interface dependency. An underlying Registry relational data model, RegTAP, has been developed which describes the core registry metadata to be exchanged using the RI 2.0 standard interface. This document is currently beginning the RFC phase. Registry Metadata for Footprints The RWG will continue to have discussions and evolve the current standards infrastructure in support of metadata for footprint descriptions, i.e. spatial regions of coverage. The advancement in the MOC and STC/s standards definition will be evaluated in the context of footprint representation for support of applications in development of data discovery. Future coordination between IVOA groups will involve potential development for spatial indexing in support of application integration with registry collections. Registry Operations and Curation The Registry WG continues to drive regular discussions during Interoperability meetings about IVOA Registries operations, including curation of VO Resources and validation of DAL services. The Registry WG is pending effort to develop a coordinated plan accepted by TCG and proposed to the Exec for developing the procedures and processes of curating nonresponsive or non-valid registered DAL services. This also includes consistency in Registry managed authorities and harvested resource metadata across the IVOA registry network. -- GretchenGreene - 12 February 2014 last updateSemanticsThe WG will continue to contribute to other WGs and IGs as appropriate.* Extension of the UCD List for planetary data: There are requirements from the Planetary community to use and extend the IVOA UCD list for using these semantic tags while mapping their metadata. Some concepts , current in Planetary science are missing . An effort to propose new possible UCD strings and validate them in the IVOA UCD maintenance group is taking place . Proposed list by May Interop 2014 Data Curation & PreservationThe IG will continue discussions on general topics of interest to the community. Some of the topics we expect to focus on during the next 12 months include:
Knowledge Discovery in DatabasesTheoryThe main goal of the Theory I.G. is to propose an access protocol to discover and retrieve simulated data. From last InterOp, several implementations have been tested. We also had a few teleconferences with some members of the Theory I.G. Search for simulations Some technical difficulties have been identified. The most important of them, is that, contrary to an observationnal data, a simulated data may require several thousands quantities to be described in a way allowing us to answer our usecases. Because RDBMS are not efficient with tables with more than thousands columns, the access protocol for theoretical data should not rely on specific technologies (as TAP/RDBMS). During the second Theory session in Heidelberg InterOp we will discuss this important topic. A possible solution, would be to define a few APIs with a main one, the SEARCH/CUTOUT function, to discover interesting simulations. The query language would be a subset of ADQL. On the other hand, the exchange format will have to be defined. We will discuss the oportunity to use the serialization of SimDM in VO-Tables following the proposal of the utype tiger team. Extraction of data Concerning the extraction of data, the situation is more simple. Services will provide a Datalink document to describe the possible operations on data. This will be presented and discussed in the common DAL / Theory session about datalink. Goals of this InterOp for the Theory I.G. are : 1) conclude on a solution to discover simulations that is independent on the technology used to store metadata, 2) define the large picture about the exchange format document in the communication client / server during the search phase of simulations, 3) advance on the syntax of datalink document.EducationThe newly formed Edu IG is planning to discuss its Roadmap during the Heidelberg 2013 Interop. The basis for the discussion are the Terms of Reference that can be read in the IG's web page together with the Rationale. At the Heidelberg Interop, the Edu IG will have both a morning and an afternoon session on Thursday May 16. At least one of the two sessions will be devoted to discussions of the Roadmap and its implementation. Contributions from anybody interested will be most welcome. -- MassimoRamellaINAF - 2013-03-25Time DomainThe TDIG is working on a note endorsing SimpleTimeSeries as an IVOA-approved format for time series data and also waiting for feedback from the Registry WG on VOEventRegExt (see above). We anticipate participation in the multi-dimensional data discussions. We will issue an update note covering the VOEvent Transport Protocol, and then push that towwards becoming an IVOA-approved standard. -- MatthewGraham - 2013-05-09 -- JohnSwinbank - 2014-02-11Standard and ProcessesNo evolution of the standards forseen in 2013.Science PrioritiesScience priority areas are: Multi-dimensional data, and Time Domain Astronomy. Focus sessions at the May 2013 interop meeting will engage projects and surveys that produce and use multi-dimensional data (including radio astronomy, IFU, high energy and simulation data) and Time Domain data (time series, light curves, transient event reports) in a discussion on the role of VO technologies in these areas. Multi-d and Time Series use cases are being collected as part of this effort.<--
|
View topic | History: r11 < r10 < r9 < r8 | More topic actions...
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback