IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.Applications
Data Access Layer
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
| ||||||||
Changed: | ||||||||
< < | Data Curation & Preservation | |||||||
> > | Data Curation & Preservation | |||||||
The IVOA Data Curation and Preservation Interest Group continues to be the place to discuss topics such as data citation, DOIs, Certification, and to pass information about the activities of the Research Data Alliance relevant to the astronomical community.
EducationThe Education interest group is working on a repository for documents related to education together with its implications for the Registry. On a different line, the Education interest group is considering the possible benefits for the public of citizen science projects, in particular their use as pedagogical projects aimed at the discovery of astronomy in classrooms.Knowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsProvide feedback on the operational implementation of VO standards including the level to which operational implementations pass validation services. Work to promote the development and use of validation services for VO standards. Continue to work to unify the reporting of validation errors.TheorySimDAL 1.0
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesAn update of the IVOA Standard Documents, initially proposed a V1.2, is now discussed a V2.0. It implements the Endorsed Note path and Errata for IVOA documents. The evolution was discussed in Stelleboch in the TCG meeting. RFC before Trieste meeting with the aim to conclude the new version before the end of the year.Science PrioritiesFollowing the May 2016 focus sessions on “Interoperability of data from major astronomy projects” the CSP plans to collect more structured feedback from large projects in the form of a survey. The priority areas remain Multi-dimensional data and Time domain astronomy. The final stages of the development of standards to meet the minimal requirements for multi-d data access are to be followed closely, and their completion will be an important milestone.<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.Applications
Data Access Layer
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationThe IVOA Data Curation and Preservation Interest Group continues to be the place to discuss topics such as data citation, DOIs, Certification, and to pass information about the activities of the Research Data Alliance relevant to the astronomical community.EducationThe Education interest group is working on a repository for documents related to education together with its implications for the Registry. On a different line, the Education interest group is considering the possible benefits for the public of citizen science projects, in particular their use as pedagogical projects aimed at the discovery of astronomy in classrooms.Knowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsProvide feedback on the operational implementation of VO standards including the level to which operational implementations pass validation services. Work to promote the development and use of validation services for VO standards. Continue to work to unify the reporting of validation errors.TheorySimDAL 1.0
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesAn update of the IVOA Standard Documents, initially proposed a V1.2, is now discussed a V2.0. It implements the Endorsed Note path and Errata for IVOA documents. The evolution was discussed in Stelleboch in the TCG meeting. RFC before Trieste meeting with the aim to conclude the new version before the end of the year.Science Priorities | ||||||||
Added: | ||||||||
> > | Following the May 2016 focus sessions on “Interoperability of data from major astronomy projects” the CSP plans to collect more structured feedback from large projects in the form of a survey. The priority areas remain Multi-dimensional data and Time domain astronomy. The final stages of the development of standards to meet the minimal requirements for multi-d data access are to be followed closely, and their completion will be an important milestone. | |||||||
<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.Applications
Data Access Layer
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationThe IVOA Data Curation and Preservation Interest Group continues to be the place to discuss topics such as data citation, DOIs, Certification, and to pass information about the activities of the Research Data Alliance relevant to the astronomical community.Education | ||||||||
Changed: | ||||||||
< < | The Education interest group is working on a repository for documents related to education together with its implications for the Registry. On a different line, the Education interest group is considering the possible benefits for the public of citizen science projects, in particular their use as pedagogical projects aimed at the discovery of astronomy in classrooms. | |||||||
> > | The Education interest group is working on a repository for documents related to education together with its implications for the Registry. On a different line, the Education interest group is considering the possible benefits for the public of citizen science projects, in particular their use as pedagogical projects aimed at the discovery of astronomy in classrooms. | |||||||
Knowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
Operations | ||||||||
Added: | ||||||||
> > | Provide feedback on the operational implementation of VO standards including the level to which operational implementations pass validation services. Work to promote the development and use of validation services for VO standards. Continue to work to unify the reporting of validation errors. | |||||||
TheorySimDAL 1.0
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesAn update of the IVOA Standard Documents, initially proposed a V1.2, is now discussed a V2.0. It implements the Endorsed Note path and Errata for IVOA documents. The evolution was discussed in Stelleboch in the TCG meeting. RFC before Trieste meeting with the aim to conclude the new version before the end of the year.Science Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.Applications
Data Access Layer
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationThe IVOA Data Curation and Preservation Interest Group continues to be the place to discuss topics such as data citation, DOIs, Certification, and to pass information about the activities of the Research Data Alliance relevant to the astronomical community.Education | ||||||||
Added: | ||||||||
> > | The Education interest group is working on a repository for documents related to education together with its implications for the Registry. On a different line, the Education interest group is considering the possible benefits for the public of citizen science projects, in particular their use as pedagogical projects aimed at the discovery of astronomy in classrooms. | |||||||
Knowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheorySimDAL 1.0
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesAn update of the IVOA Standard Documents, initially proposed a V1.2, is now discussed a V2.0. It implements the Endorsed Note path and Errata for IVOA documents. The evolution was discussed in Stelleboch in the TCG meeting. RFC before Trieste meeting with the aim to conclude the new version before the end of the year.Science Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.Applications
Data Access Layer
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & Preservation | ||||||||
Added: | ||||||||
> > | The IVOA Data Curation and Preservation Interest Group continues to be the place to discuss topics such as data citation, DOIs, Certification, and to pass information about the activities of the Research Data Alliance relevant to the astronomical community. | |||||||
EducationKnowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheorySimDAL 1.0
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and Processes | ||||||||
Added: | ||||||||
> > | An update of the IVOA Standard Documents, initially proposed a V1.2, is now discussed a V2.0. It implements the Endorsed Note path and Errata for IVOA documents. The evolution was discussed in Stelleboch in the TCG meeting. RFC before Trieste meeting with the aim to conclude the new version before the end of the year. | |||||||
Science Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.Applications | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Added: | ||||||||
> > | ||||||||
Data Access Layer
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationEducationKnowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheorySimDAL 1.0
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.ApplicationsData Access Layer | ||||||||
Deleted: | ||||||||
< < | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationEducationKnowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheory | ||||||||
Added: | ||||||||
> > | SimDAL 1.0
| |||||||
Time DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops.ApplicationsData Access Layer | ||||||||
Added: | ||||||||
> > |
| |||||||
Data ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationEducationKnowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheoryTime DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016A | ||||||||
Changed: | ||||||||
< < | This outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops. | |||||||
> > | This outlines the roadmap for development activities by the various IVOA working and interest groups in 2016 between the Cape Town and Trieste Interops. | |||||||
ApplicationsData Access LayerData ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsVocabularies / Thesauri / OntologiesIn continuation of previous roadmap: Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
Data Curation & PreservationEducationKnowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheoryTime DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.Semantics | ||||||||
Added: | ||||||||
> > | Vocabularies / Thesauri / Ontologies | |||||||
Added: | ||||||||
> > | In continuation of previous roadmap:
Coordinate and/or influence the development of knowledge bases which support IVOA standards and curation initiatives, in particular
Liaise with DC&PProvide a forum for the joint discussion of standards development outside of the IVOA which influence curation and preservation activities, in particular:
| |||||||
Data Curation & PreservationEducationKnowledge Discovery in DatabasesThe Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
OperationsTheoryTime DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. Grid and Web SevicesSingle Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data".RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsData Curation & PreservationEducationKnowledge Discovery in Databases | ||||||||
Added: | ||||||||
> > | The Knowledge Discovery group keeps on working on redefining its charta. Main questions for 2016 are:
| |||||||
OperationsTheoryTime DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelObsCore-1.1:Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. | ||||||||
Added: | ||||||||
> > | ||||||||
Grid and Web Sevices | ||||||||
Added: | ||||||||
> > | Single Sign-On Profile (SSO) 2.0: Minor updates to are needed on the PR to address feedback received in Cape Town. Specifically, a few more authentication types (authTypes) and their identifiers need to be mentioned and standardized. There should be a mention of the use of "groups" for authorization in the document. It was mentioned that an IVOA note with examples on how to use the various authMethods described in the SSO 2.0 specification would be useful. VOSpace 2.1: Feedback continues to come in from the authors. Once these has been addressed the document will go through the six-week review period before becoming a proposed recommendation. VO Support Interfaces (VOSI) 1.1: Minor changes to be made before this can be made a recommendation. These should be addressed before the meeting in Trieste. UWS 1.1: The document has been sent to the TCG chairs to executive review. The GWS working group is encouraging groups to publish interoperable implementations of the various standards. As per the recommendations from the Focus Sessions held in Cape Town, the GWS working group will work with the Knowledge Discovery Interest Group to examine use cases, technologies, and possible standards in regards to the question of "code to data". | |||||||
RegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData Model | ||||||||
Added: | ||||||||
> > | ObsCore-1.1: Addressing RFC comments, final update expected by end of June. Should be ready for TCG approval by end of July. VODML-1.0: Cape Town discussions indicate the document is PR ready once a 'How To Get Started' style help document is completed. This document is scheduled for completion by end of June. PR period should start in July. Target REC by Trieste. STC-2.0: WD feedback is strongly on the side of needing to split the model to a core package with secondary extensions for higher level packages (like Region and Area). Project scope to be reviewed Jun/Jul, with support of Dataset/NDCube models to be the focus. Need to schedule an external review panel to evaluate model and provide recommendations. DatasetMetadata-1.0: Model is stable, with user implementations/serializations in both VODML Mapping and utype conventions. Focus will be on organizing external interoperable usage of the model in a SIAV2 thead. Target is REC ready by Trieste. NDCube-1.0: Similar to DatasetMetadata, working draft is stable. User implementations to be packaged and uploaded to twiki. Focus will be on organizing external interoperable usage of the model in a SIAV2 thread. Target is REC ready by Trieste. Provenance-1.0: The Dataset/Observation/Provenance models are coming toward a common framework. For Trieste, the goals will be to: a) fanalize the vodml-compliant data model so that it works with only minor modifications for all our use cases. b) deliver working draft model document; including minimum requirements; serialization strategy; and access to Provenance data. c) work relations between SimDM and ProvDM SourceDM-1.0: Team is to organize project goals and scope, summarized to twiki pages. Project should broaden use-case example set beyond Gaia. At present, there is no tageted status for Trieste. | |||||||
Grid and Web SevicesRegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. We will continue maintenance of the Registry system and contents, as well as our validation operations.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainImmediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort.Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistryVOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. | ||||||||
Changed: | ||||||||
< < | Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. | |||||||
> > | Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. | |||||||
We will continue maintenance of the Registry system and contents, as well as our validation operations.
SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime Domain | ||||||||
Added: | ||||||||
> > | Immediately following the Stellenbosch InterOp, VOEvent Transport Protocol 2.0 moved to RFC. We expect to devote the bulk of effort in this period to responding comments and, hopefully, pushing VTP towards full recommendation status. Based on discussions at Stellenbosch, we will continue informally exploring prospects for time series representation within the VO. We will seek to engage with the large facilities represented at the Stellenbosh "focus sessions", and explore how we can best help address their needs. As and when the promised (Ciardi's talk) LSSTC funded alert system study takes place, we will actively engage with this effort. | |||||||
Standard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistry | ||||||||
Changed: | ||||||||
< < | VOResource 1.1: A large number of minor issues are being fixed in this first | |||||||
> > | VOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. | |||||||
Deleted: | ||||||||
< < | overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. | |||||||
Changed: | ||||||||
< < | SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols | |||||||
> > | SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. | |||||||
Deleted: | ||||||||
< < | (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. | |||||||
Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. | ||||||||
Changed: | ||||||||
< < | Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. | |||||||
> > | Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. | |||||||
Changed: | ||||||||
< < | Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. | |||||||
> > | Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. | |||||||
Changed: | ||||||||
< < | We will continue maintenance of the Registry system and contents, as well as our validation operations. | |||||||
> > | Standards records: We would like to finally have StandardsRegExt records for all IVOA recommendation, and we will work with the WG chairs to have them generated. A page at http://wiki.ivoa.net/twiki/bin/view/IVOA/WriteAStandardsRecord has been set up to guide standards authors. | |||||||
Added: | ||||||||
> > | We will continue maintenance of the Registry system and contents, as well as our validation operations. | |||||||
SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainStandard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistry | ||||||||
Added: | ||||||||
> > | VOResource 1.1: A large number of minor issues are being fixed in this first overhaul of VOResource in 10 years. The main new feature is a capability to represent alternative identifiers (DOIs, ORCIDs, etc). Until Trieste, we want to reach consensus on the remaining open questions, with implementations, also in RegTAP following after Trieste. SimpleDALRegExt 1.1: The adaption of SimpleDALRegExt to new DAL protocols (in particular SIAP 2.0) should see PR soon and should be ready for REC by Trieste. Registry Interfaces 1.1: RFC soon [Theresa?] TAPRegExt 1.1: This will be kept in lockstep to the progress of the TAP/ADQL updates. Registering TAP tables: We are encouraging takeup of the Discovering Data Collections Note. Until Trieste, we in particular hope for more feedback from the CDS. Since they would like to link tables and (cone search) services, there is a (weak) link with VOResource 1.1. We believe such links could be done based on record-local tags. Spatial searches in the Registry: We will continue to lay the software foundations in pgSphere (i.e., indexable MOCs). The existing footprintURL mechanism to distribute footprints will be good enough for prototyping. We will continue maintenance of the Registry system and contents, as well as our validation operations. | |||||||
SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainStandard and ProcessesScience Priorities | ||||||||
Changed: | ||||||||
< < | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> | |||||||
> > | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |
IVOA Roadmap for 2016AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 20116 between the Cape Town and Trieste Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistrySemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainStandard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> |