[Heig] Meeting Notes & Actions - 02Apr25 meeting

[BONNAREL FRANCOIS gmail]

Dear all,
As promised during the 2nd of april meeting I completed the issue (more 
a comment) on the access and description section of the IRFs (2.1.4)

The content of this section considered as requiredc for IRF  looks very 
similar to the content of a DataLink {links} table

The section reads
"In the table access protocol (TAP) service we could add an IRF Table,
with the following columns:
• event-list datapublisher_id
• irf_type, category of response: EffectiveArea, PSF, etc.
• irf_description, one line explanation for the role of the file
• Access.url, URL to point to the IRF
• Access.format, format of IRF
• Access.size, size of IRF file"

event-list datapublisher_id : to be added to the table
irf_type : can be stored in DataLink "content_qualifier" FIELD with a 
specific ivoa irf_type vocabulary (to be defined)
irf_description : the DataLink "description" FIELD is appropriate
Access.url --> DL "access_url" FIELD
Access.format --> DL "content_type" FIELD
Access.size --> DL "content_length" FIELD

in "semantics" FIELD we could have a new "irf" term as sub-term of
"calibration"

(Semantics describes the relationship between a dataset (event-list 
there) and the related material, while the content_qualifier describes 
this material in detail)

in ID, we should have the list of identifiers of related event-lists, if 
known.

This table could be stored in a tap service or accessed via the DataLink 
parameter interface

Cheers

François



Le 03/04/2025 à 20:07, Janet Evans via heig a écrit :
> Dear HEIG Folks,
>
> Here are the notes/actions from yesterday’s meeting - 
> corrections/feedback welcomed:
> https://wiki.ivoa.net/twiki/bin/view/IVOA/HEIG_02Apr25
>
> **The thing I forgot to do was write down the names of folks at the 
> meeting - if your name was skipped, please update the doc or let me 
> know and I’ll fix it.
> *
> *
> *Actions:*
> o JE: update the Obscore Google sheet with*new columns* (Currently 
> exist in Obscore (y/n), Required/Optional keyword) and add a *Use case 
> sheet *for inputs - DONE
>  See: 
> https://docs.google.com/spreadsheets/d/16e0mWWD5hn6fLYQFf7SqD4crJvGlroV44Zs3uRCZqGM/edit?gid=0#gid=0
> o MS further plan the Paris meeting April 29/30 and let the group know 
> the topics/times/contribs needed
> o Ian: Update the Obscore google sheet/Note with your inputs - inform 
> the group when you've made a pass
> o All: think about what Obscore inputs makes sense for your project 
> and add to the Google sheet
> o JE/BK: Initiate planning of the Plenary with other groups and ensure 
> HEIG has their part complete
> o BK/others: further plan structure of HEIG Obscore note
>
> Next meeting will be at the Paris meeting (Apr 29/30) TBD … we expect 
> more input from Mathieu as planning goes forward.
>
> Best regards,
> -janet & bruno
>
> *—**—**—**—**—**—*
> Janet Evans
> Chandra Data System Software Development Manager
> Chandra X-ray Center
> Center for Astrophysics | Harvard & Smithsonian
>
> Office: (617) 495 7160 | Cell: (617) 688 6084
> 60 Garden Street | MS 81 | Cambridge, MA 02138
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/heig/attachments/20250413/587867a9/attachment.htm>