VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
FutureThe VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard.Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
Implementations Validators
Comments from the IVOA Community during RFC/TCG review period: 2024-April-25 - 2024-June-06The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from Markus Demleitner, 2024-04-30I have skimmed the diffs from commit c6575888 on (hint: git diff -b is a godsend for that). I have found some minor style issues, for which I have created PR #61 (https://github.com/ivoa-std/VOTable/pull/61). Feel free to discard this if you think it does not improve presentatin. I have one actual question: What about getting MIN/MAX parsing fixed in astropy? This would actually be my favourite reference implementation. Is anyone on it? I'm totally not wild on doing this myself (too much tooling in astropy for my taste), but if there are no other volunteers, I might be talked into putting it in. -- MarkusDemleitner - 2024-04-30 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | This is a bug to be fixed later -- AdrianDamian - 2024-06-12 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comment from L.Michel, 2024-05-02 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Is there a way to connect the XSD with the IVOA vocabulary in order to make the system attribute in COOSYS rule machine-readable.This would be very usefull in other contexts (Registry, DM) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Is there a way to connect the XSD with the IVOA vocabulary in order to make the system attribute in COOSYS rule machine-readable.This would be very usefull in other contexts (Registry, DM) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-- LaurentMichel - 2024-05-02 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
In short: We can't, because XML Schema does not understand RDF at all, let alone the way we are using it. There is a longer answer: We could define an IVOA-controlled schema extension, where a short piece of software would take a schema "template" and fill out enumerations from vocabularies. Then this thing could update the schemas when the vocabularies change. There is a lot to be said for that. But there is the important counter argument that the schema files would change "on the fly". Whether that is something we want requires a lot of thought. On the other hand, this is not really much of a practical problem; VOTable validators need to check so much more than the XSD compliance, starting with whether the data content somewhat matches the FIELD-s, that doing the vocabulary validation externally is a relatively minor matter. -- MarkusDemleitner - 2024-06-12 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from TCG members during the RFC/TCG Review Period: 2024-April-25 - 2024-June-06WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
FutureThe VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard.Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementations Validators
Comments from the IVOA Community during RFC/TCG review period: 2024-April-25 - 2024-June-06The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from Markus Demleitner, 2024-04-30I have skimmed the diffs from commit c6575888 on (hint: git diff -b is a godsend for that). I have found some minor style issues, for which I have created PR #61 (https://github.com/ivoa-std/VOTable/pull/61). Feel free to discard this if you think it does not improve presentatin. I have one actual question: What about getting MIN/MAX parsing fixed in astropy? This would actually be my favourite reference implementation. Is anyone on it? I'm totally not wild on doing this myself (too much tooling in astropy for my taste), but if there are no other volunteers, I might be talked into putting it in. -- MarkusDemleitner - 2024-04-30 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comment from L.Michel, 2024-05-02Is there a way to connect the XSD with the IVOA vocabulary in order to make the system attribute in COOSYS rule machine-readable.This would be very usefull in other contexts (Registry, DM) -- LaurentMichel - 2024-05-02 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from TCG members during the RFC/TCG Review Period: 2024-April-25 - 2024-June-06WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
FutureThe VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard.Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
Implementations Validators
Comments from the IVOA Community during RFC/TCG review period: 2024-April-25 - 2024-June-06The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
Comments from Markus Demleitner, 2024-04-30I have skimmed the diffs from commit c6575888 on (hint: git diff -b is a godsend for that). I have found some minor style issues, for which I have created PR #61 (https://github.com/ivoa-std/VOTable/pull/61). Feel free to discard this if you think it does not improve presentatin. I have one actual question: What about getting MIN/MAX parsing fixed in astropy? This would actually be my favourite reference implementation. Is anyone on it? I'm totally not wild on doing this myself (too much tooling in astropy for my taste), but if there are no other volunteers, I might be talked into putting it in. -- MarkusDemleitner - 2024-04-30 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from TCG members during the RFC/TCG Review Period: 2024-April-25 - 2024-June-06WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | My advice: Follow the submission checklist in ivoatexdoc: https://ivoa.net/documents/Notes/IVOATexDoc/20230627/NOTE-ivoatexDoc-1.4-20230627.html#tth_sEc3.12 (or, even better, the checklist from a current checkout of git@github.com:ivoa-std/ivoatexDoc.git) -- MarkusDemleitner - 2024-04-30 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
FutureThe VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard.Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementations Validators
Comments from the IVOA Community during RFC/TCG review period: 2024-April-25 - 2024-June-06The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG members during the RFC/TCG Review Period: 2024-April-25 - 2024-June-06WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
FutureThe VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard.Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
Implementations Validators
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from the IVOA Community during RFC/TCG review period: 2024-04-01 - 2024-05-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from the IVOA Community during RFC/TCG review period: 2024-April-25 - 2024-June-06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from TCG members during the RFC/TCG Review Period: 2024-04-01 - 2024-05-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from TCG members during the RFC/TCG Review Period: 2024-April-25 - 2024-June-06 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
FutureThe VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard.Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
Implementations Validators
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from the IVOA Community during RFC/TCG review period: 2024-03-01 - 2024-04-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from the IVOA Community during RFC/TCG review period: 2024-04-01 - 2024-05-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from TCG members during the RFC/TCG Review Period: 2024-03-01 - 2024-04-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from TCG members during the RFC/TCG Review Period: 2024-04-01 - 2024-05-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
Future | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The VOTableInfo page contains a list of proposed changes that, during the WD phase, were agreed to defer to a future version. When the document maintenance is transitioned to GitHub, those item will be converted to GitHub issues. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The VOTable GitHub Issues page contains a list of issues and proposed future enhancements. It is the main mechanism for contributing to the standard. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reference Interoperable ImplementationsDaCHS produces COOSYSrefposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example:
Implementations Validators
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from the IVOA Community during RFC/TCG review period: 2024-03-01 - 2024-04-20The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG members during the RFC/TCG Review Period: 2024-03-01 - 2024-04-20WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
To Do Upon Approval, Prior to Upload
FutureThe VOTableInfo page contains a list of proposed changes that, during the WD phase, were agreed to defer to a future version. When the document maintenance is transitioned to GitHub, those item will be converted to GitHub issues.Reference Interoperable Implementations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | DaCHS produces COOSYS refposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the prerelease versions of STILTS ( stilts.jar) and TOPCAT ( topcat-full.jar). For example: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | DaCHS produces COOSYS refposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the latest versions of STILTS and TOPCAT. For example: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementations Validators | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments from the IVOA Community during RFC/TCG review period: 2024-03-01 - 2024-04-20The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG members during the RFC/TCG Review Period: 2024-03-01 - 2024-04-20WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
VOTable 1.5 Proposed Recommendation: Request for CommentsVOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.SummaryLatest Draft: VOTable 1.5 (Proposed Recommendation) The main purpose of VOTable 1.5 is to supportrefposition attribute analogous to TIMESYS.
VOTable 1.5 is a backward-compatible revision.
The other main differences between version 1.5 of VOTable and the preceding version 1.4 are:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | See GitHub for a full list of changes. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | See GitHub for a full list of changes. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
To Do Upon Approval, Prior to Upload
FutureThe VOTableInfo page contains a list of proposed changes that, during the WD phase, were agreed to defer to a future version. When the document maintenance is transitioned to GitHub, those item will be converted to GitHub issues.Reference Interoperable Implementations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | DaCHS produces COOSYS refposition in TAP results from the gaia.dr3lite table in the GAVO Data Center TAP service which can be read by the prerelease versions of STILTS ( stilts.jar) and TOPCAT ( topcat-full.jar). For example: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Implementations Validators | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
Comments from the IVOA Community during RFC/TCG review period: 2024-03-01 - 2024-04-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
Comments from TCG members during the RFC/TCG Review Period: 2024-03-01 - 2024-04-20WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee TCG Vote
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|
Group | Yes | No | Abstain | Comments |
TCG | ||||
Apps | ||||
DAL | ||||
DM | ||||
GWS | ||||
Registry | ||||
Semantics | ||||
DCP | ||||
Edu | ||||
KDIG | ||||
Ops | ||||
Radio | ||||
SSIG | ||||
Theory | ||||
TD | ||||
StdProc |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | RegTAP 1.2 Proposed Recommendation: Request for Comments | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | VOTable 1.5 Proposed Recommendation: Request for Comments | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | RegTAP, formally known as the IVOA Registry Relational Schema, is the standard way for clients to query the VO Registry. Version 1.2 adds | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | VOTable is a standard for the interchange of data represented as a set of tables, and includes both table metadata and the data itself.
Summary | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | tables to give the coverage in space, time, and spectrum and a tap_table view intended to replace GloTS. To make use of these features, we require a few optional ADQL features and the extra UDF ivo_interval_overlaps. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Latest version of RegTAP can be found at: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Latest Draft: VOTable 1.5 (Proposed Recommendation) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | RegTAP is a fairly long standard. For review, it is probably advisable | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The main purpose of VOTable 1.5 is to support refposition attribute analogous to TIMESYS. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | to only skim the unchanged text. For the purposes of this RFC, it is probably sufficient to closely inspect sects. 4.5, 7, 8.15 through 8.18, 9, and 10 (in particular 10.13). See also appendix E. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Reference Interoperable Implementations | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | VOTable 1.5 is a backward-compatible revision. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Server-side implementations exist in the TAP services at http://reg.g-vo.org/tap and https://registry.euro-vo.org/regtap/tap. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The other main differences between version 1.5 of VOTable and the preceding version 1.4 are: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
To Do Upon Approval, Prior to Upload | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Client-side code exploiting the new spatial tables is present in pyVO; WIRR also has constraints on coverage in space, time, and spectrum. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
Future | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Support for tap_tables is less common; however, once the data providers fix their metadata records, the content of tap_tables essentially is equivalent to what we already have in GloTS, and hence the editor would | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The VOTableInfo page contains a list of proposed changes that, during the WD phase, were agreed to defer to a future version. When the document maintenance is transitioned to GitHub, those item will be converted to GitHub issues.
Reference Interoperable Implementations | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | argue that all clients using GloTS (e.g., TOPCAT) count as reference implementations of tap_tables. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Implementations Validators | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | A validator is part of the source distribution at https://github.com/ivoa-std/RegTAP. See the validator subdirectory. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Implementations Validators | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Note that it requires a registry seeded with the data provided, and hence the suite can only be used by the service operators. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from TCG members during the RFC/TCG Review Period: 2024-02-01 - 2024-03-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from TCG members during the RFC/TCG Review Period: 2024-03-01 - 2024-04-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes Committee | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | TCG Vote : Bambi eyes - more Bambi eyes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | TCG Vote | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
RegTAP 1.2 Proposed Recommendation: Request for CommentsRegTAP, formally known as the IVOA Registry Relational Schema, is the standard way for clients to query the VO Registry. Version 1.2 adds tables to give the coverage in space, time, and spectrum and a tap_table view intended to replace GloTS. To make use of these features, we require a few optional ADQL features and the extra UDF ivo_interval_overlaps. Latest version of RegTAP can be found at:
Reference Interoperable ImplementationsServer-side implementations exist in the TAP services at http://reg.g-vo.org/tap and https://registry.euro-vo.org/regtap/tap. Client-side code exploiting the new spatial tables is present in pyVO; WIRR also has constraints on coverage in space, time, and spectrum. Support for tap_tables is less common; however, once the data providers fix their metadata records, the content of tap_tables essentially is equivalent to what we already have in GloTS, and hence the editor would argue that all clients using GloTS (e.g., TOPCAT) count as reference implementations of tap_tables.Implementations ValidatorsA validator is part of the source distribution at https://github.com/ivoa-std/RegTAP. See the validator subdirectory. Note that it requires a registry seeded with the data provided, and hence the suite can only be used by the service operators.
Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-20The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from TCG member during the RFC/TCG Review Period: 2024-02-01 - 2024-03-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from TCG members during the RFC/TCG Review Period: 2024-02-01 - 2024-03-20 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : Bambi eyes - more Bambi eyesIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
RegTAP 1.2 Proposed Recommendation: Request for CommentsRegTAP, formally known as the IVOA Registry Relational Schema, is the standard way for clients to query the VO Registry. Version 1.2 adds tables to give the coverage in space, time, and spectrum and a tap_table view intended to replace GloTS. To make use of these features, we require a few optional ADQL features and the extra UDF ivo_interval_overlaps. Latest version of RegTAP can be found at:
Reference Interoperable ImplementationsServer-side implementations exist in the TAP services at http://reg.g-vo.org/tap and https://registry.euro-vo.org/regtap/tap. Client-side code exploiting the new spatial tables is present in pyVO; WIRR also has constraints on coverage in space, time, and spectrum. Support for tap_tables is less common; however, once the data providers fix their metadata records, the content of tap_tables essentially is equivalent to what we already have in GloTS, and hence the editor would argue that all clients using GloTS (e.g., TOPCAT) count as reference implementations of tap_tables.Implementations ValidatorsA validator is part of the source distribution at https://github.com/ivoa-std/RegTAP. See the validator subdirectory. Note that it requires a registry seeded with the data provided, and hence the suite can only be used by the service operators.
Comments from the IVOA Community during RFC/TCG review period: 2024-02-01 - 2024-03-20The comments from the TCG members during the RFC/TCG review should be included in the next section. In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from TCG member during the RFC/TCG Review Period: 2024-02-01 - 2024-03-20WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice ChairApplications Working GroupData Access Layer Working GroupData Model Working GroupGrid & Web Services Working GroupRegistry Working GroupSemantics Working GroupData Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupOperations Interest GroupRadio Astronomy Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupStandards and Processes CommitteeTCG Vote : Bambi eyes - more Bambi eyesIf you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
|