Update of the section 6, Proposal for the ivoa.obscore_he attributes

HighEnergyObsCoreExt.tex

@@ -23,9 +23,9 @@
 %\usepackage{minted}
 \setlength {\marginparwidth }{2cm}
 \usepackage{todonotes}
+\usepackage{array}
 \usepackage{amsmath}
 \usepackage{amssymb}
-
 \usepackage[nopostdot,style=super,nonumberlist,toc]{glossaries}
 
 \newacronym{IVOA}{IVOA}{International Virtual Observatory Alliance}
@@ -115,7 +115,7 @@ \section{High Energy Astrophysics Data}
 
 Though \textbf{event-lists} \emph{may} include estimators for calibrated physical values, they typically still have to be corrected for the photometric, spectral, spatial, and/or temporal responses of the telescope and detector combination to yield scientifically interpretable information. The mappings between the observables and physical measurements of the source properties are called \glspl{IRF}; using techniques like forward-folding, they enable one to fit a model (with any combination of spectral, spatial, and temporal components) of the true flux of particles from a source arriving at the instrument to the measured quantities. The \glspl{IRF} generally evolve over time with the instrument and observation characteristics, and are usually defined for a specific time interval and decomposed into a standard set of independent components (see section 3.1.5 of \citep{2024ivoa.note.heig}), such as the spatial point-spread function or the energy-migration matrix, where each component may be stored or computed separately.  Some of the \glspl{IRF} are probabilistic in nature\footnote{The energy matrix is a probability density funtion}, and in addition may depend on the set of events selected for analysis by the end user. They are usually not invertible, so methods such as forward-folding fitting (using source models that are estimated) are needed to estimate physical properties given observables. Since both \glspl{IRF} and \textbf{event-lists} are required to process \gls{HEA} data, some \gls{IVOA} standards must be be modified in order to expose both of them via the \gls{VO}.
 
-In the following, the current ObsCore standard will be discussed in Section \ref{sec:obscore}, focusing on attributes that need to be modified. Then, we propose the creation of a \gls{HEA} extension of ObsCore in Section \ref{sec:obscoreext}, as some attributes are very specific to our domain. In these two sections, the discussion focuses on the attribute definitions rather on the attribute values. In Section \ref{sec:voc}, enhancement of vocabulary is proposed for some ObsCore attributes, DataLink semantics, UCDs and MIME-types.
+In the following, the current ObsCore standard will be discussed in Section \ref{sec:obscore}, focusing on attributes that need to be modified. Then, we propose the creation of a \gls{HEA} extension of ObsCore in Section \ref{sec:obscoreext}, as some attributes are very specific to our domain (see \S\ref{sec:ibscoreext}). In these two sections, the discussion focuses on the attribute definitions rather on the attribute values. In Section \ref{sec:voc}, enhancement of vocabulary is proposed for some ObsCore attributes, DataLink semantics, UCDs and MIME-types.
 
 \section{ObsCore Attribute Definitions for High Energy Astrophysics Data}
 \label{sec:obscore}
@@ -499,7 +499,7 @@ \subsubsection{Evolution of UCD list}
 
 \subsection{MIME-types Enhancements}\label{sec:mimetypes}
 
-Data files used in the \gls{HE} domain should have appropriate MIME-types, so that they can be shown in ObsCore tables or elsewhere.
+Data files used in the \gls{HEA} domain should have appropriate MIME-types, so that they can be shown in ObsCore tables or elsewhere.
 
 Formats based on FITS could thus be declared as:
 
@@ -508,6 +508,42 @@ \subsection{MIME-types Enhancements}\label{sec:mimetypes}
 \item {\bf x-fits-vodf}: for FITS files following the VODF specification \citep{2023arXiv230813385K}
 \end{itemize}
 
+\section{Proposal of the {\it ivoa.obscore\_hea} attributes}\label{sec:ibscoreext}
+
+This section summarizes the proposal for the \gls{HEA} extension of Obscore. Note that the name of the extension could be {\it ivoa.obscore\_hea}, {\it ivoa.obscore-hea}, {\it ivoa.obscore\_he} or {\it ivoa.obscore-he}. We use here the first term in the Appendix \ref{sec:uc}.
+
+\begin{center}
+\begin{tabular}{ | m{2.5cm} | m{3em} | m{3em} | m{3em} | m{6cm} | m{2.3em} |}
+\hline
+{\centering \bf Column Name}     &{\centering \bf UType} &{\centering \bf Unit} &{\centering \bf Type} &{\centering \bf Description} &{\centering \bf MAN}\\
+\hline
+ ev\_xel & TBD &  unitless & int & Number of events in an event\_list & NO \\
+\hline
+ s\_ref\_energy & TBD & eV & float & Energy at which the ObsCore spatial characterisation attributes s\_fov , s\_region, s\_resolution are defined & NO \\
+\hline
+ em\_ref\_energy  & TBD & eV & float & Energy at which the ObsCore spatial characterisation attributes em\_res\_power, em\_resolution are defined & NO \\
+\hline
+ s\_ref\_oaa & TBD & deg & float & Off-axis angle (i.e., the angular separation of the target or source from the telescope optical axis) at which the ObsCore spatial characterisation attributes s\_fov , s\_region, s\_resolution are defined & NO \\
+\hline
+ em\_ref\_oaa & TBD & deg & float & Off-axis angle (i.e., the angular separation of the target or source from the telescope optical axis) at which the ObsCore spectral characterisation attributes em\_res\_power, em\_resolution are defined & NO \\
+\hline
+  t\_intervals & TBD & unitless & TMOC &List of observation intervals or stable/good time intervals describing the exact observation time coverage  & NO \\
+\hline
+  energy\_min & TBD & float & eV & Energy associated to the Obscore attribute em\_max, describing the minimal energy of the dataset & NO \\
+\hline
+  energy\_max & TBD & float & eV & Energy associated to the Obscore attribute em\_min, describing the maximal energy of the dataset & NO \\
+\hline
+  obs\_mode & TBD & unitless & string &  Observation mode of the observation (e.g. TBU) & NO \\
+\hline
+  tracking\_mode & TBD & unitless & string & Tracking mode of an observation (e.g., sidereal rate, moving target [solar system] tracking, drift scans)  & NO \\
+\hline
+  analysis\_mode & TBD & unitless & string & Data reduction/analysis mode& NO \\
+\hline
+  event\_type & TBD & unitless & string & Data quality flag of the events (e.g. ``good psf'', ``good rejection'', ``Nhit (100,200)'' & NO \\
+\hline
+\end{tabular}
+\end{center}
+
 \pagebreak
 \printglossaries