| |
| META TOPICPARENT |
name="InterOpJune2025" |
[ back to main programme page ]
DRAFT Schedule
| Registry Session #1: Tuesday June 3, 2025 @11:00-12:30 ET (Session #3) Room 1309 |
| Speaker |
Title and Abstract |
Materials |
Time |
| Renaud Savalle (PADC) (remote) |
Intro and Documents Status
Review of current WG work |
|
5 |
Tess Jaffe (NAVO)
(in person) |
The new Registry GitHub Project board and Spring Cleaning hackathon objectives
Presentation of Registry Session #2: Spring Cleaning Hackathon |
|
5 |
Hendrick Heinl (INAF)
(remote) |
Update about the plans for a 2026 Registry good practices event for data providers
TBC |
|
10+5 |
| Renaud Savalle (PADC)(remote) |
StandardRegExt and OpenAPI
I will give a short summary of the StandardRegExt-1.1 RFC status and propose a way to embed OpenAPI specifications to describe input/input parameters of a standard. |
|
5+5 |
|
|
<
< |
Gilles Landais (CDS)
(remote) |
Use of VODataService for VizieR records
TBC |
|
10+5 |
|
>
> |
Gilles Landais (CDS)
(remote) |
Use of VODataService for VizieR records
Starting from the current metadata issue concerning relations between tables and services , we propose to discuss on a serialization evolution that could be used in the current landscape. We will explore the new features described in VODataService1.2 and 1.3, to extrapolate and evaluate an other serialization. |
|
10+5 |
|
| |
Markus Demleitner (Univ. Heidelberg/GAVO)
(in person) |
Metadata for continually updated resources
The Virtual Observatory contains quite a few resources that are continuously updated (observatory archives, VOEvent streams, etc). One question this raises is: what would be a useful temporal coverage specification for these? Perhaps more importantly: Can we come up with some metadata that lets clients decide for which resources a later re-visit will likely yield different results? |
|
15+5 |
| All |
Discussion
topics TBC |
|
20 |
| Registry Session #2: Spring Cleaning Hackathon: Thursday June 5, 2025 @14:00-15:30 ET (Session #12) Room 1309 |
| Speaker |
Title and Abstract |
Materials |
Time |
|
|
<
< |
Tess Jaffe (NAVO)
(in person) |
The Registry Working Group has begun to keep a project board on GitHub where we can track and discuss issues with the metadata in the Registry. Incorrect or missing metadata make services and/or datasets harder to find, so fixing these issues to make a more complete and consistent Registry will improve the functioning of the entire VO ecosystem. Please come to our very first Spring Cleaning Hackathon at the Interop if you are interested in issues related to your own services' metadata or if you are interested more broadly in how to enable VO clients to find the right data and services. Current topics to get started with include: consistency among Registries; the usage of UCDs to describe tabular data; subject and concept metadata and the UAT; spatial coverage; and whatever else participants are interested in discussing and/or hacking on. Take a look at the Python notebook with examples of how to evaluate issues across the Registry or at specific publishers. |
GitHub repo |
90 |
|
>
> |
Tess Jaffe (NAVO)
(in person) |
The Registry Working Group has begun to keep a project board on GitHub where we can track and discuss issues with the metadata in the Registry. Incorrect or missing metadata make services and/or datasets harder to find, so fixing these issues to make a more complete and consistent Registry will improve the functioning of the entire VO ecosystem. Please come to our very first Spring Cleaning Hackathon at the Interop if you are interested in issues related to your own services' metadata or if you are interested more broadly in how to enable VO clients to find the right data and services. Current topics to get started with include: consistency among Registries; the usage of UCDs to describe tabular data; subject and concept metadata and the UAT; spatial coverage; and whatever else participants are interested in discussing and/or hacking on. Take a look at the Python notebook with examples of how to evaluate issues across the Registry or at specific publishers. |
GitHub repo |
90 |
|
| |
Relevant Links and Information
<--
--> |
