VODataService 1.2 Proposed Recommendation: Request for CommentsSummaryVODataService 1.2 is an incremental update to the widely-used VODataService Registry extension (98% of all registry records use VODataService resource types). We expect 100% backward compatibility. We believe there are three main points for TCG review:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
There are also a few minor changes to tableset conventions. This requires review by those familiar with VOSI Tables and TAP.
Changelog since REC-1.1In approximate order of importance:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reference Interoperable ImplementationsOn the production side, DaCHS has been producing records with most of these features for quite some time. As an example, see the Heidelberg data center's OAI endpoint at https://dc.g-vo.org/oai.xmlAlso on the production side, VizieR is producing VODataService 1.2-compliant records, including coverage declaration, on http://cdsweb.u-strasbg.fr/registry/beta/ , which is slated to become the primary VizieR publishing registry in Mid-2021. On the consumption side, the Heidelberg RegTAP service parses the extra information and exposes it in custom RegTAP extensions rr.stc_spatial, rr.stc_spectral, and rr.stc_temporal. The table's nrows attribute shows up in rr.res_tables. Implementation Validators | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The syntax (and a bit of the semantics, too) of VODataService records can be checked with ordinary XML schema validation tools. As setting up the necessary schema locations is somewhat involved, you might want to use DaCHS's dachs val xsd command. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The syntax (and a bit of the semantics, too) of VODataService records can be checked with ordinary XML schema validation tools. As setting up the necessary schema locations is somewhat involved, you might want to use DaCHS's dachs val xsd command. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
For VOSI tables endpoints of TAP services, the STILTS taplint validator release >3.4, or failing that the latest pre-release, will validate against the schema coming with this PR. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Comments from the IVOA Community during RFC/TCG review period: RFC_start_date - RFC_end_date | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from the IVOA Community during RFC/TCG review period: 2021-03-01 to 2021-04-23 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 member during the RFC/TCG Review Period: RFC_start_date - RFC_end_date | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from TCG member during the RFC/TCG Review Period: 2021-03-01 to 2021-04-23 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupOperationsStandards and Processes CommitteeTCG Vote : Vote_start_date - Vote_end_dateIf 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.
|