IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.Applications
Data Access LayerSCS 1.1 :
Data ModelVO-DML-1.0
Grid and Web ServicesPriority 1:
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.Semantics | ||||||||
Changed: | ||||||||
< < | Data Curation & Preservation | |||||||
> > | Data Curation & Preservation | |||||||
The Data Curation \& Preservation IG will continue to be the place where liaison between the IVOA and the Research Data Alliance RDA is established, with regular discussion of RDA activities, their relevance to the IVOA, and the IVOA activities relevant to the RDA (eg Provenance). This is a standing item for the IG session at each IVOA Interoperability meeting. The DataCP IG also hosts discussions on topics such as DOI usage in astronomy.
EducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time DomainTop priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions.
In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2).
Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers.
Standard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.Applications
Data Access LayerSCS 1.1 :
Data ModelVO-DML-1.0
Grid and Web ServicesPriority 1:
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & Preservation | ||||||||
Added: | ||||||||
> > | The Data Curation \& Preservation IG will continue to be the place where liaison between the IVOA and the Research Data Alliance RDA is established, with regular discussion of RDA activities, their relevance to the IVOA, and the IVOA activities relevant to the RDA (eg Provenance). This is a standing item for the IG session at each IVOA Interoperability meeting. The DataCP IG also hosts discussions on topics such as DOI usage in astronomy. | |||||||
EducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time DomainTop priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions.
In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2).
Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers.
Standard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.Applications | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Added: | ||||||||
> > |
| |||||||
Data Access LayerSCS 1.1 :
Data ModelVO-DML-1.0
Grid and Web ServicesPriority 1:
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time DomainTop priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions.
In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2).
Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers.
Standard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
| ||||||||
Deleted: | ||||||||
< < | ||||||||
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerSCS 1.1 :
| ||||||||
Deleted: | ||||||||
< < | ||||||||
SLAP 1.1:
| ||||||||
Changed: | ||||||||
< < | Discussion on the mailing list on « recognizing DataLink outside DAL context »: | |||||||
> > | Discussion on the mailing list on « recognizing DataLink outside DAL context »:
| |||||||
Deleted: | ||||||||
< < |
| |||||||
| ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ADQL 2.1: | |||||||
Deleted: | ||||||||
< < | ADQL 2.1: | |||||||
Deleted: | ||||||||
< < | ||||||||
MOC in TAP (and ADQL):
| ||||||||
Deleted: | ||||||||
< < | ||||||||
DAL for Time Series (and other dataproducts types)
| ||||||||
Deleted: | ||||||||
< < | ||||||||
TAP 1.1:
Data Model | ||||||||
Added: | ||||||||
> > | VO-DML-1.0
| |||||||
Grid and Web ServicesPriority 1:
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time Domain | ||||||||
Changed: | ||||||||
< < | Top priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions. | |||||||
> > | Top priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions. | |||||||
Changed: | ||||||||
< < | In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2). | |||||||
> > | In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2). | |||||||
Changed: | ||||||||
< < | Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers. | |||||||
> > | Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers. | |||||||
Added: | ||||||||
> > | ||||||||
Standard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
| ||||||||
Added: | ||||||||
> > | ||||||||
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access Layer | ||||||||
Added: | ||||||||
> > |
SCS 1.1 :
| |||||||
Data ModelGrid and Web ServicesPriority 1:
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time Domain Top priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions.
In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2).
Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers.
Standard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web ServicesPriority 1:
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time Domain | ||||||||
Added: | ||||||||
> > | Top priority for TDIG is the support the ongoing effort in the DAL and DM working groups to standardize a data model and discovery & access mechanisms for time series data within the context of the VO. TDIG will focus on developing and curating scientific use cases and engaging with the working groups to assist in developing and evaluating prototype solutions.
In addition, we will begin to draft a modest revision to the VOEvent to address non-urgent issues which have arisen over the six years since VOEvent 2.0 was standardized. This will include clearer definition of the semantics of the IVOID/IVORN in the context of VOEvent and more powerful and expressive description of space-time coordinates (e.g. by integrating STC2).
Finally, we will continue to work with the wider astronomical community, and in particular major facilities, to assess our longer term goal of evolving the VOEvent standard and associated infrastructure to address the needs of future high-volume event producers. | |||||||
Standard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web ServicesPriority 1: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
Priority 2:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
Nice to have:
| ||||||||
Deleted: | ||||||||
< < | ||||||||
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time DomainStandard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData Model | ||||||||
Changed: | ||||||||
< < | Grid and Web Sevices | |||||||
> > | Grid and Web Services | |||||||
Added: | ||||||||
> > |
Priority 1:
| |||||||
RegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesWe intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop.OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time DomainStandard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistryRegistry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months.SemanticsData Curation & PreservationEducationKnowledge Discovery in Databases | ||||||||
Added: | ||||||||
> > | We intent to build a task force that identifies key activities / challenges to focus on In addition important knowledge discovery uses cases should be identified and collected to be reported at the next interop meeting. If possible, prototype implementations of services should be developed and presented that cover some of the discussed topics at the Shanghai interop. | |||||||
OperationsTheoryWork in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018.Time DomainStandard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistry | ||||||||
Changed: | ||||||||
< < | Registry Interfaces 1.1, which in particular lets RegTAP operators | |||||||
> > | Registry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. | |||||||
Deleted: | ||||||||
< < | register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. | |||||||
Changed: | ||||||||
< < | VOResource 1.1: Should go to RFC in the next few weeks. We are still | |||||||
> > | VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. | |||||||
Deleted: | ||||||||
< < | soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. | |||||||
Changed: | ||||||||
< < | RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have | |||||||
> > | RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. | |||||||
Deleted: | ||||||||
< < | first implementations of a proposed extension of the schema. A working draft should be published July-ish. | |||||||
Changed: | ||||||||
< < | Discovering Dependent Resources: This is a proposed endorsed note trying | |||||||
> > | Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. | |||||||
Deleted: | ||||||||
< < | to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. | |||||||
Changed: | ||||||||
< < | Standards records: We will continue to work with the chairs of the other | |||||||
> > | Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). | |||||||
Deleted: | ||||||||
< < | IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). | |||||||
TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. | ||||||||
Changed: | ||||||||
< < | Maintenance: We will keep making sure the registry system runs; in | |||||||
> > | Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months. | |||||||
Deleted: | ||||||||
< < | particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months. | |||||||
SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheory | ||||||||
Added: | ||||||||
> > | Work in the "Implemementation Note" for SimDAL. We intend to describe several implementations, done by different groups, about different types of simulations. It is expected to have the note finished by Spring, 2018. | |||||||
Time DomainStandard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities<--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistry | ||||||||
Added: | ||||||||
> > | Registry Interfaces 1.1, which in particular lets RegTAP operators register their services as registries (registration as TAP services with RegTAP data in them, of course, can continue). That, however, builds on the Discovering Dependent Resources note, so that would probably have to be endorsed before RI 1.1 can actually become REC. VOResource 1.1: Should go to RFC in the next few weeks. We are still soliciting takeup of the new features. To make this more attractive, the RofR will investigate installing the new schema so registries already using new features do not become invalid. RegTAP 1.1: This puts new VOResource 1.1 features into RegTAP. We have first implementations of a proposed extension of the schema. A working draft should be published July-ish. Discovering Dependent Resources: This is a proposed endorsed note trying to solve the problem of properly discovering data collections that are published through other services, the prime use case so far being TAP tables. The central concept here are auxiliary capabilities, essentially saying "this data can be accessed via TAP/SIAP/whatever in a services with the following access URL". There is some takeup of the proposed scheme, and TOPCAT already supports discovery through it. To make it a valid replacement for current workarounds (i.e., GloTS), more takeup is necessary; various registry operators have pledged to work towards it. Standards records: We will continue to work with the chairs of the other IVOA working groups to ensure that they register their standards as envisioned by StandardsRegExt (cf. WriteAStandardsRecord). TAPRegExt 1.1 will be kept in lockstep with TAP 1.1. Maintenance: We will keep making sure the registry system runs; in particular, the anomalies diagnosed by the ESA registry have been diagnosed and, where there is a potential for later functionality problems, will be addressed in the coming months. | |||||||
SemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainStandard and ProcessesFollow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes.Science Priorities | ||||||||
Changed: | ||||||||
< < | <!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> | |||||||
> > |
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistrySemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainStandard and Processes | ||||||||
Added: | ||||||||
> > | Follow-up of the Document Standards V2.0: real-life adjustment of the standardisation, endorsed notes and errata processes. | |||||||
Science Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> <--
|
IVOA Roadmap for 2017AThis outlines the roadmap for development activities by the various IVOA working and interest groups in 2017 between the Shanghai and Santiago Interops.ApplicationsData Access LayerData ModelGrid and Web SevicesRegistrySemanticsData Curation & PreservationEducationKnowledge Discovery in DatabasesOperationsTheoryTime DomainStandard and ProcessesScience Priorities<!-- * Set ALLOWTOPICRENAME = TWikiAdminGroup --> <--
|