<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Janet , Hi HEIG members,</p>
<p>Here are my comments about the last version of the note from
August 03. <br>
I just want to mention that july-august is the summer leave period
for people working at the university, <br>
that is why I answer now. </p>
<p>I will try to put my remarks and suggestions in Github , but I
cannot put comments on the current version via the web interface
currently. </p>
<p>Here are my remarks: </p>
<p>I believe some features need to be improved before submission :</p>
<p><i><b>Terms for data products : </b></i><br>
we have used advanced data products and analysis data products to
express, I suppose new elaborated products that are more easy <br>
to the user to take a decision, in data selection or in data
interpretation. <br>
<br>
<i>I think we must provide a clear definition for them. </i><br>
I believe both terms are fuzzy: </p>
<p>Why "advanced"? with respect to today’s available data products?
What will it mean in 2 years ? <br>
Are some advanced products not used for science analysis?
dedicated to data selection only? <br>
<br>
What are these data products intended for ? <br>
To understand better the content of a dataset, ease data analysis
or data selection or data processing ?<br>
Can we precise this goal better? <br>
<br>
This question will need to be adressed for Obscore 1.2 , but for
this Note we can keep "advanced data products" <br>
with the caveat that clarification is needed. </p>
<p><b><i>Labels :</i></b></p>
<p>#pdf<br>
evoques a Probability analysis result for some variable quantity
contained in the data.<br>
--> seems understandable <br>
#draws <br>
Analysis result after a MCMC computation for some variable in the
data like aperture photometry, astrometry, etc. <br>
Seems useful for characterising the observed dataset content, its
quality / interpretability. <br>
Q:Is it the result of interpretation of the observed data or a
side product to help or it? <br>
--> Can the definition be clarified ? <br>
<br>
#region <br>
Used for Chandra.<br>
Does it apply to other projects? How is it called elsewhere? <br>
Is it a spatial ancillary dataproduct ?<br>
Spatial map ?
Multi-dimensional significance map?<br>
STMOC is a possible format for a multi-order map, but the geometry
of the regions <br>
are tiles and not circles or polygons as shown in the exemple
proposed for <br>
#region in the VEP currently submitted at<br>
<a
href="https://github.com/ivoa-std/VEPs/pull/21/changes/c4195e1975341881d8fda22cb851ff11b5b74c1f#top"
class="moz-txt-link-freetext">https://github.com/ivoa-std/VEPs/pull/21/changes/c4195e1975341881d8fda22cb851ff11b5b74c1f#top</a><br>
<br>
--> Seems useful for characterising the dataset quality /
interpretability.<br>
Q:Is it the result of observed data interpretation or a side
product to help or it? </p>
<p><b><i>Appendix B : Response table </i></b><br>
In order to distinguish response files from observation files as
targeted in the ObsCore specification, we propose to distribute
response data products in a separate table in TAP and to use it
in a Join operation with the ivoa.obscore table that describes
the event-list .<br>
<br>
The type of response is defined in the column
\emph{resp_dataproduct_type} and follows the <i>response-type</i>
ivoa vocabulary. <br>
<br>
Each response is searchable by its dataproduct_type
(resp_dataproduct_type)<br>
and by some axes properties on position, energy, time for
selection . <br>
They correspond to the actual coverage of the response data set, <br>
which can differ slightly from the one of the original data set
(event-list) they can apply to. <br>
The response file may apply on selected events from the
event-list, based on event_type, <br>
source modeling , or energy constraints. <br>
Therefore the coverage in space, energy and time of a response
function may differ <br>
from the one computed on the primary event-list taken in the
observation. <br>
<br>
In the uses cases discussed in the note, responses are searched
based on the IDs for observation or event-list <br>
they are linked to in the archive, so by \emph{obs_id} or
\emph{obs_publisher_id} in the ObsCore table.
<br>
These can be used as foreign keys in the join operation between
the response table and the ivoa.obscore.
<br>
<br>
The results can be sorted by their <i>resp_data_product_type</i>
to discover #psf or #edisp or #arf, etc. <br>
So one response table only is needed . <br>
<br>
Introducing for instance <i>response_psf</i> or r<i>esponse_edisp</i>
tables whose metadata content can vary for each archive,<br>
just break interoperability. <br>
The response_table should contain the mandatory attributes defined
in the core response table defined Tab. 8, <br>
and if needed , can also contain optional columns for some
particular data providers and users. <br>
<br>
Those columns can’t be standardized. <br>
We have not explored use cases requiring any distinction between
response tables . <br>
<br>
In any case it is up to the user to finally check the response
file in details before using it for calibration. <br>
<br>
</p>
<p>thanks for your reading, </p>
<p>Best , Mireille</p>
<p><br>
</p>
<div class="moz-cite-prefix">Le 12/08/2026 à 11:08 PM, Janet Evans
via heig a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:8C5D1F3C-5FBD-4BAE-A64E-70D376D9F260@cfa.harvard.edu">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<span style="font-family: ArialMT;">Dear HEIG,</span>
<div style="font-family: ArialMT;"><br>
</div>
<div style="font-family: ArialMT;">Apologies for the long gap in
communication. Here is a summary of some of the things that
have happened since our last HEIG meeting.</div>
<div style="font-family: ArialMT;"><br>
</div>
<div style="font-family: ArialMT;">o IVOA Interop in Strasbourg </div>
<div style="font-family: ArialMT;"><span class="Apple-tab-span"
style="white-space: pre;"> </span>Great meeting for HEIG with
interest in the Obscore extension, a plenary to present the HE
Obscore extension doc details and the demos prepared by this
group.</div>
<div style="font-family: ArialMT;">o Semantics meeting at Interop </div>
<div style="font-family: ArialMT;"><span class="Apple-tab-span"
style="white-space: pre;"> </span>Several of us met with the
Semantics WG to settle several vocabulary keywords - it was a
good meeting</div>
<div style="font-family: ArialMT;">o Further Obscore Note input
and final review/scrub</div>
<div style="font-family: ArialMT;"><span class="Apple-tab-span"
style="white-space: pre;"> </span>There is a new section 6 along
with a vocabulary update and scrub for typos/etc.</div>
<div style="font-family: ArialMT;"><br>
</div>
<div style="font-family: ArialMT;">It’s now your turn to review
the document as we prepare to turn it over to the TCG/Exec for
Endorsed Note status. </div>
<div style="font-family: ArialMT;">Here’s the schedule we’re
working to:</div>
<div style="font-family: ArialMT;"><span
style="color: rgb(10, 10, 10); font-family: "Google Sans", "Helvetica Neue", sans-serif; orphans: 2; widows: 2; background-color: rgb(255, 255, 255);"><span
class="Apple-tab-span" style="white-space: pre;"> </span>Wed,
Aug 12 — Janet sends notice of final doc to HEIG for review
(typos/minor edits, no new content)</span></div>
<div style="font-family: ArialMT;"><span
style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);"><span
class="Apple-tab-span"
style="color: rgb(10, 10, 10); font-family: "Google Sans", "Helvetica Neue", sans-serif; white-space: pre;"> </span><font
color="#0a0a0a"
face="Google Sans, Helvetica Neue, sans-serif">Tue, Aug
25 — End of HEIG review/feedback</font></span></div>
<div style="font-family: ArialMT;"><span
style="orphans: 2; widows: 2; background-color: rgb(255, 255, 255);"><font
color="#0a0a0a"
face="Google Sans, Helvetica Neue, sans-serif"><span
class="Apple-tab-span" style="white-space: pre;"> </span>Thu,
Aug 27 — Janet sends note to TCG with request for
review/endorsed status </font></span></div>
<div style="font-family: ArialMT;"><br>
</div>
<div style="font-family: ArialMT;">The document is available in
GitHub (<a
href="https://github.com/ivoa/HighEnergyObsCoreExt?tab=readme-ov-file"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/ivoa/HighEnergyObsCoreExt?tab=readme-ov-file</a>);
I’ve also appended the PDF below.</div>
<div style="font-family: ArialMT;"><br>
</div>
<div style="font-family: ArialMT;">Best regards,</div>
<div style="font-family: ArialMT;">-janet</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<br class="Apple-interchange-newline">
<div>
<meta charset="UTF-8">
<div dir="auto"
style="font-family: Arial; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><b>Janet
Evans | Software Development Manager | Chandra X-ray Center</b><br>
Center for Astrophysics | Harvard & Smithsonian<br>
Office: (617) 495-7160 </div>
<div dir="auto"
style="font-family: Arial; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">60
Garden Street | MS 81 | Cambridge, MA 02138</div>
<span
style="font-family: Arial; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"></span><br>
<br class="Apple-interchange-newline">
</div>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<pre class="moz-signature" cols="72">--
--
Mireille Louys, MCF (Assistant Professor)
Centre de données Astronomiques (CDS) Equipe Images, ICube
Observatoire de Strasbourg Telecom Physique Strasbourg
11, rue de l' Université 300, Bd Sebastien Brandt CS 10413
F-67000 Strasbourg F-67412 Illkirch Cedex</pre>
</body>
</html>