SimpleDALRegExt1.2 Proposed Recommendation: Request for Comments | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
While future versions may be migrated elsewhere, VODataService 1.2 is managed by the legacy volute repository at: http://volute.g-vo.org/svn/trunk/projects/registry/SimpleDALRegExt/
SummarySimpleDALRegExt defines a group of registry extensions for describing related "Simple" DAL services: Cone, Image, Spectra, etc. Occasional tweaks to vocabularies and incremental changes to the services' own standards are tracked here to keep potential registry search results in line with actual service capabilities, and to show connections between resources in new ways: in this case, adding auxiliary capability descriptions (see below.)Changes since 1.1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Most of the document is unmodified. Some vocabulary cruft has been removed and tested with searches across all current registries to assure backward compatibility. There are three changes which should be reviewed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Most of the document is unmodified. Some vocabulary cruft has been | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | removed and tested with searches across all current registries to assure
backward compatibility. There are two changes which should be reviewed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Reference Interoperable Implementations | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The auxiliary capabilities for the S-Protocols are a consequence of the Endorsed Note on discovering data collections. Compared to TAP auxiliary capabilities, they have not been used much yet (there are ivo://org.gavo.dc/lensunion/q/im and ivo://org.gavo.dc/hppunion/q/im, though). Hence, to our knowledge there is no client takeup of them. Consider this change editorial in nature; the standards identifiers from discovering data collections simply needed to be mentioned in this spec. Similarly, using a vocabulary for the reference frames rather than an in-schema list is just intended to cut down on the number of lists of reference frames in the various standards. It has no operational implications (even less so since to date few services or clients actually offer different reference systems in SSAP queries). The declaration of product type, on the other hand, has operational consequences; several services in the VO already declare their product type; try | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The auxiliary capabilities for the S-Protocols are a consequence of the Endorsed Note on discovering data collections. Compared to TAP auxiliary capabilities, they have not been used much yet (there are ivo://org.gavo.dc/lensunion/q/im and ivo://org.gavo.dc/hppunion/q/im, though). Hence, to our knowledge there is no client takeup of them. Consider this change editorial in nature; the standards identifiers from discovering data collections simply needed to be mentioned in this spec. Similarly, using a vocabulary for the reference frames rather than an in-schema list is just intended to cut down on the number of lists of reference frames in the various standards. It has no operational implications (even less so since to date few services or clients actually offer different reference systems in SSAP queries). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | SELECT ivoid, res_title, detail_value FROM rr.resource NATURAL JOIN rr.res_detail WHERE detail_xpath='/capability/productType' | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | on a RegTAP service. On the client side, version 3.15_3 (beta) of the spectral analysis programme SPLAT uses this to let users select time series services (as opposed to spectral services). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from the IVOA Community during RFC/TCG review period: 2021-03-01 to 2021-11-15 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | 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: 2021-03-01 to 2021-04-23 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Comments from TCG member during the RFC/TCG Review Period: 2021-03-01 to 2021-11-15 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 GroupThis document points to two vocabularies : product type (https://www.ivoa.net/rdf/product-type/2020-03-09/product-type.html) and refframe (http://www.ivoa.net/rdf/refframe), which are still not approved. This can't go forward until refframe and product-type are fixed.
Data Curation & Preservation Interest GroupEducation Interest GroupKnowledge Discovery Interest GroupSolar System Interest GroupTheory Interest GroupTime Domain Interest GroupOperationsYes, it looks OK. I made a few comments of a mostly trivial nature which Markus addressed. Only one worth recording here:
Standards 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.
|