<--
LogisticsSunday, May 14, 2017 @16:00 CST (08:00 UTC) Wednesday, 17 May 2017 - 12:30 CST (4:30 UTC)Agenda FM69
Argentina-NOVAArVOAstroGridAustralia-VOBRAVOChina-VOChiVOCVOEuro_VOESAVOFrance VOGAVO | ||||||||
Changed: | ||||||||
< < | The GAVO Data Centers in Heidelberg and Potsdam keep maintaining and | |||||||
> > | The GAVO Data Centers in Heidelberg and Potsdam keep maintaining and developing services. A substantial number of new services have been created. | |||||||
Deleted: | ||||||||
< < | developing services. A substantial number of new services have been created. | |||||||
Changed: | ||||||||
< < | In software, we have been busy removing features from DaCHS and | |||||||
> > | In software, we have been busy removing features from DaCHS and smoothing out legacy wrinkles in preparation for a 1.0 release. We also keep developing pyVO, having updated the Registry interface to use standard RegTAP rather than the proprietary STScI interface. First Datalink code exists. A bugfix release of the spherical geometry database extension pgsphere is imminent, a release with added MOC functionality will take a bit longer (but interested parties are welcome to betas). | |||||||
Deleted: | ||||||||
< < | smoothing out legacy wrinkles in preparation for a 1.0 release. We also keep developing pyVO, having updated the Registry interface to use standard RegTAP rather than the proprietary STScI interface. First Datalink code exists. A bugfix release of the spherical geometry database extension pgsphere is imminent, a release with added MOC functionality will take a bit longer (but interested parties are welcome to betas). | |||||||
Changed: | ||||||||
< < | In standards, we worked on VOResource 1.1 adoption; our Registry | |||||||
> > | In standards, we worked on VOResource 1.1 adoption; our Registry interface at reg.g-vo.org has been extended to provide a prototype for working with the new features. We also continued to work with other projects in making our GloTS service (which currently is what most clients base their TAP table discovery on) obsolete eventually (that's the discovering dependent data note). We're also cooperating on EPN-TAP evolution, for instance, by working out how GeoJSON can be integrated into the VO stack. | |||||||
Deleted: | ||||||||
< < | interface at reg.g-vo.org has been extended to provide a prototype for working with the new features. We also continued to work with other projects in making our GloTS service (which currently is what most clients base their TAP table discovery on) obsolete eventually (that's the discovering dependent data note). We're also cooperating on EPN-TAP evolution, for instance, by working out how GeoJSON can be integrated into the VO stack. | |||||||
Changed: | ||||||||
< < | GAVO continues activities in bolstering VO takeup by reaching out to | |||||||
> > | GAVO continues activities in bolstering VO takeup by reaching out to scientists. One highlight since the last Interop has been a Gaia data access workshop in Heidelberg that included in-depth introductions into several VO techniques. | |||||||
Deleted: | ||||||||
< < | scientists. One highlight since the last Interop has been a Gaia data access workshop in Heidelberg that included in-depth introductions into several VO techniques. | |||||||
HVOVObs.itJapan-VO | ||||||||
Added: | ||||||||
> > | Japan-VO has recently released a new feature: a web-based quick-look system for Suprime-CAM that had been equipped with the Subaru telescope. This web-based quick-look system utilizes our experience with the ALMA WebQL system (we demonstrated the system in the IVOA interop meeting in South Sfrica). An exapmle can be found at http://jvo.nao.ac.jp/subaruwebql/SubaruWebQL.html?dataId=SUPM1153EF6501CD700 . You can zoom-in and zoom-out images. After releasing the Suprime-CAM QL, data request to the JVO site incresed to ~500-600 GB per month. We are updating the ALMAWebQL. | |||||||
RVOSA^3SVOUkraine_VOUSVOAHEASARC:
Report from the TCGRegistryVOResource 1.1 (with new features like support for DOIs and ORCIDs, mirror URLs, vocabularies, license URIs and many other little fixes) has seen first implementations and some minor changes. There is also a draft for RegTAP 1.1 giving access to the new features. We have not gone for PR before Shanghai as we wanted more implemenation experience. Registry Interfaces 1.1 is in late RFC; a couple of uncomplicated comments have come in and have been taken care of, some reviews are still missing. The note on discovering dependent resources ("table registration") still is in RFC. Many major data centers have not yet fully adopted the proposed method, so the prototype interface to it in TOPCAT still is significantly less complete that the current GloTS-based one. We hope we can convince the relevant publishing registry operators to provide the missing metadata until the next interop. On enabling STC searches in the Registry, we have now a first implementation with MOC-based footprints in Heidelberg, fed from harvesting separate footprint endpoints and in-record, "classic" STC-X coverages. There's still some implemenation work to do before this fully supports ADQL geometry operations (so far, only operations with points are implemented), but it's already clear that one of the major challenges to work out is how to deal with the plethora of resources declaring themselves as covering the entire sky. On the focus on time series, we're now discussing a simple hack based on utype annotation of tablesets of SSA services to allow clients to identify time series services until a proper SSA evolution (or something else) comes around (unless the IVOA decides that time series discovery should go through obscore exclusively). We're also co-operating with the Edu IG on making tutorials and similar material discoverable. Based on experience with the VOTT directory of tutorials (which is based on prototype records), we've proposed some changes to the extension schema specified in a draft note that's been around for a while. SimpleDALRegExt has been ready for REC since last year; all that's missing is Exec approval.SemanticsUCD: New terms added to the UCD tree. Update of the UCD v1.3 working draft .
|