Request for Modification (RFM) for the UCD vocabulary towards UCDList v1.7

This page summarises the steps for Modifications and Updates proposed in the UCD List Maintenance recommendation. The UCDListMaintenancePage summarises the past and current RFMs.

The third (on going) iteration for the Request for modifications of UCD terms is summarized in the following content.

These terms are submitted for evaluation to the UCD science committee (see details in the Maintenance Specification document).

UCDList v1.7 Request For Modifications, from Jan 2025 to now

Proposed RFMs

---

Still in discussion from RFM 1.7

Proposal from MarkusDemleitner & BaptisteCecconi ( VEP-UCD-005, initially in UCDList 1.4 RFM)

• Proposed term: stat.histogram
• Proposed description: An array-like object with counts or ratios in bins
• Prefix: P
• Rationale:
• Used-in:
• Discussion: See VEP-UCD-005, and UCDList 1.4 RFM for the detailed discussion.

Sci-UCD Further Discussion: The same discussion as that of pos.moc applies for the use cases. Depending on how what is tagged, P or S flag should be used, and a specific dataproduct_type may also be needed to advertise a product in an ObsTAP or EPN-TAP table.

BC [2023-06-22]: what about using `stat.distribution` which would be more generic (with possible child `stat.distribution.cumulative` or `stat.distribution.histogram`) ?

BC [2024-03-21]: pending , needs more discussion

UCD Proposal for the distribution of High Energy data (M.Louys for the group)

Following section 5.3 of the current Note "IVOA ObsCore Extension and Discovery of High Energy Astrophysics Data" ( https://github.com/ivoa/HighEnergyObsCoreExt )

Proposal from M.Louys ( VEP-UCD-015)

• Proposed term: phys.pulseHeight or phys.pulse.amplitude
• Proposed description: Amplitude measured by a pulse analyser after a particle or radiation detector (photon, gamma ray, ...).
• Prefix: Q
• Description: In event-list data product obtained in X-ray or Gamma-ray, the need to characterise the raw measure provided by the detector has appeared. A similar requirement was formulated for radio data as well.
• Rationale: This term would be useful to refer to raw data coming out of a detector and not calibrated yet. The need for such a term was mentionned during the preparation of the IVOA Note "VO Data discovery for High Energy data sets".
• Used-in: Chandra event-list, CTA event-list before calibration.
• Discussion:
  • There may be an overlap with the proposal for "phys.adu" in VEP-UCD-14.txt. To be discussed.
  • [2024-03-21] Existing UCD for pulse: "src.var.pulse" and for amplitude: "src.var.amplitude" (but with E prefix, which should be changed Q to have this word applied to any other primary word)
• BC [2024-03-21]: Proposed change: "src.var.amplitude" prefix set to "Q".
• BC/BK [2025-12-01]:Proposed solution and agreed : "src.var.amplitude;src.var.pulse;stat.uncalib"

Proposal from Mireille Louys for HEIG VEP-UCD-27-stat_confidenceLevel (amendment of definition)

VEP-UCD-027-stat_confidenceLevel currently discussed

Proposal from Mireille Louys for HEIG VEP-UCD-26-particle_types

VEP-UCD-26-particle_types New terms currently discussed

Proposal from Mireille Louys for HEIG VEP-UCD-25-em_gamma_energy_list

VEP-UCD-25-em_gamma_energy intervals New terms currently discussed

UCD proposal applied as changes for UCDList1.7

still in discussion

Summary for iteration UCDList1.6 to UCDList1.7

Term	VEP-UCD link	Modification Type	Decision

UCD proposals rejected and solved

Term	VEP-UCD link	Suggestion	Use instead
phys.pulseHeight	VEP-UCD-015	can combine existing UCD	src.var.amplitude;src.var.pulse;stat.uncalib

UCD proposals not solved yet --> for next step

Term	VEP-UCD link	Modification Type	Decision

<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->