UCDList_1-4_RFM < IVOA

---+ Request for Modification for the UCD vocabulary towards UCDList v1.4

This page summarizes the steps for Modifications and Updates proposed in The UCD Maintenance workink draft .

The second (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.4 Request For Modifications, from May 2018 to Oct 2018

---++ Proposed UCD: stat.histogram

*Use Case*: A column contains not a single value but a distribution-like entity. For an example, run a query like

<pre>select 
  gavo_histogram(phot_g_mean_mag, 5, 15, 10) as dist, 
  round(100/parallax) as bin
from tgas.main
where parallax&gt;5
group by bin
</pre>

on the TAP service http://dc.g-vo.org/tap and inspect the dist column.

*Proposed Solution*: a primary-only atom stat.histogram would work for this. In the example in the use case, the service could assign a UCD stat.distribution;pos.parallax to the dist column. Hence, we'd add a new line to the UCD list:

P|stat.histogram | An array-like object with counts or ratios in bins

A footnote like "This also includes simple nonparametric distributions" or similar would be appreciated.

-- IVOA.MarkusDemleitner - 2018-05-09

---+++ Discussion

The column dist from the example certainly cannot be annotated as pos.parallax, and while there is stat.likelihood, there is no indication that this is intended to cover collection of likelihoods. I argue the UCD system should allow a plausible annotation of the dist column. If so, it appears we need some new term.

This new term should, I think, cover simple binned aggregations as well as nonparametric distributions (in the sense of \sum_{x\in\Omega} P(x)=1) in order to have sufficient generality. Hence, I'd avoid stat.distribution, which would imply normalisation.

Also, stat.distribution (or something like that) might, some day, be useful to annotate a different thing that this would *not* cover: columns containing distributions in the sense of some representation of "a gaussian with mu=3 and sigma=0.3" or "a poisson distribution with lambda=0.2".
---+++ Answer/discussion

The discussion started on the semantics mailing list . see the starting point for this discussion [[http://mail.ivoa.net/pipermail/semantics/2018-May/002575.html][here]]

<span style="background-color: transparent;">The proposed term is considering an array element instead of a single value , usually considered for the quantity tagged by a UCD.</span>

Note that the semantic tag does not describe any property of the array except its statistical definition of histogram.
---+++ Decision

<span style="background-color: transparent;">Examine more use cases where this UCD could be combined to check the P or Q status before approving addition</span>

<span style="background-color: transparent;">( -- </span>IVOA.MireilleLouys<span style="background-color: transparent;"> - 2020-02-03)</span>
---+++ Further discussion

<span style="background-color: transparent;">Being able to tell that a column contains a histogram could be useful. However, the use of the UCD only is not sufficient to describe that column. We suggest that the histogram column is connected to a </span><span style="color: #606060; font-family: ">&lt;GROUP ... /&gt; </span><span style="background-color: transparent;">through a </span><span style="color: #606060; font-family: ">ref </span><span style="background-color: transparent;">attribute. The </span><span style="color: #606060; font-family: ">GROUP </span><span style="background-color: transparent;">should define the binsize, the number of bins and the lower / upper bounds of the histogram, with units. Example:</span>
<verbatim>[...] 
<GROUP ID='histogram'>
     <PARAM name='lower_bound' value=5 unit='' ucd='phot.mag;em.opt;stat;mean'/>
     <PARAM name='upper_bound' value=15 unit='' ucd='phot.mag;em.opt;stat;mean'/>
     <PARAM name='bin_count' value=10 unit='' ucd='meta.number'/>
     <PARAM name='bin_size' value=1 unit='' ucd=''/>
</GROUP>
[...]
<FIELD ID='dist' datatype='int', ucd='stat.histogram;phot.mag;em.opt;stat;mean' ref='histogram' arraysize='*'/>
[...]</verbatim>

The result of the proposed query can't be used out of context, since the histogram properties are not described.

This is beyond the scope of Semantics/UCD, but this shows that we have to be cautious and may be propose a Note on how to deal with histograms in VOTable columns.

-- IVOA.BaptisteCecconi - 2020-02-06

Previous iteration for the Request for modifications of UCD terms is summarized in the following page. ( click the link)
---+ [[UCDList_1-3_RFM][UCDList v1.3 - from May 2017 to Feb 2018]]

Pending concepts considered in previous iteration waiting for more examples and use-case update
---++++++ <span style="color: darkgreen;">Concept: shape of planetary objects. </span>

<strong><span style="color: darkgreen;">pos.rotation</span></strong>

<strong><span style="color: darkgreen;">pos.Euler.Angle </span> </strong>

<span style="color: darkgreen;"> *Concept : orbital parameters* </span>

<span style="color: darkgreen;"> *Concept : 3D rotation parameters* </span>

<span style="color: darkgreen;"> </span>
<div style="position: absolute; left: -10000px; top: 1977px; width: 1px; height: 1px; overflow: hidden;" id="_mcePaste">

---+ Request for Modification for the UCD list

This page is proposed in the new process for UCDs update discussed at the Interop meeting in Shanghai in May 2017. The new Note Maintenance for UCD specification mentions the details of the updating process. When a new UCD term seems necessary to include in the UCD list, a record describing the request for addition can be expressed as followed : new term proposed, rationale, example of usage, etc , as show in the list below.

The term is then disussed within the maintenance committee and the semantics working group and answers from the maintenance committee is given within 1 month.

Every 6 months the list of proposed changes are examined by the TCG and the validated changes are ingested in the new version of Endorsed Note for the UCD1+ list of terms.
---+++++ Proposals from Solar and Planetary community ( B. Cecconi et al.)

#concept : electric current density <br />family: plasma environement <br />proposal: <strong>phys.flux ; phys.charge </strong><br />requires : phys.charge with definition : Electric charge and tag : Q

#concept : electric current density <br />family: plasma environement <br />proposal: <strong>phys.flux ; phys.charge </strong><br />requires : phys.charge with definition : Electric charge and tag : Q

_##answer we understood the need for two concepts : electric current density and electric charge_ _proposal for update:_

_add Q | phys.electCharge | Related to Electric charge <br /> add Q | phys.current | Electric current<br />add Q | phys.current.density | Electric current density_

_benefits : introduces phys.current; this definition is more focused on the requested concept --&gt; implies better assignment_

#concept : Incidence <br />family: Observation geometry ; Illumination conditions <br />proposal: *pos.incidenceAng* <br />requires : <br />definition : Incidence angle<br />tag : Q

#concept: Emergence angle<br />family: Observation geometry ; Illumination conditions

_##answer_ please include figure to illustrate the various required angles

proposal:<strong> pos.emergenceAng</strong><br /> definition : Emergence angle<br />tag : Q

#concept:Azimuth angle<br /> proposal: *pos.azimuthAng* <br />definition : Azimuthal angle<br />tag : Q

proposal: <strong>pos.cylindrical</strong><br />family : SSIG coordinates systems<br />rationale: no such coordinate branch in the UCD tree yet<br />definition : Cylindrical coordinates <br />tag : S

proposal: <strong>pos.cylindrical.r</strong><br />requires :pos.cylindrical<br />definition : Cylindrical coordinate (radial distance from z-axis)<br />tag : Q<br /> <br /> proposal: <strong>pos.cylindrical.th </strong><br />definition : Cylindrical coordinate (Azimuthal angle around z-axis)<br />tag : Q

proposal: *pos.cylindrical.z* <br />definition : Cylindrical coordinate (height from reference plane)<br />tag : Q

#concept Spherical Coordinates

proposal: <strong>pos.spherical</strong><br />Rationale: not present in UCD tree definition : spherical coordinates <br />tag : S<br /> <br /> proposal:<strong> pos.spherical.r </strong><br />definition : spherical coordinate (radial distance from origin)<br />tag : Q

proposal: *pos.spherical.th* <br />definition : spherical coordinate (colatitude angle)<br />tag : Q

proposal: <strong>pos.spherical.ph </strong><br />definition : spherical coordinate (Azimuth angle)<br />tag : Q

#concept : orbital parameters <br />%Comment perifocal "src.orbital.periastron" exists but is slightly different<br />%Comment periapsis : check variation in meaning <br /> proposal: *src.orbital.periapsis* <br />definition : minimal distance to the center of mass for an orbit<br />tag : P<br /><br /> #concept : rotation params <br /> proposal: *pos.rotation* <br />definition : Relative to rotation <br />tag : S<br /><br /> proposal: <strong>pos.rotation.eulerAngle </strong><br />definition : Euler angles vector <br />tag : V<br /><br />proposal: <strong>pos.rotation.quaternion </strong><br />definition : rotation quaternion vector<br />tag : V<br /> <br />proposal:<strong> pos.rotation.matrix</strong> <br />definition : rotation matrix<br />tag : V<br /><br /> proposal: <strong>pos.rotation.axis </strong><br />definition : rotation axis vector<br />tag : V

#concept: spatial resolution

rationale: linear resolution on cartesian or linear spatial axis as opposed to angular resolution <br />proposal: <strong>pos.resolution </strong><br />definition : Spatial linear resolution (not angular)<br />tag : Q

_##answer add Q | pos.resolution | Spatial linear resolution (not angular)_

%heliocentric coordinates <br />longitude and latitude can be expressed as <br />proposal: pos.bodyrc.lon;pos.heliocentric <br />proposal: pos.bodyrc.lat;pos.heliocentric <br />% induced changes in assign tool: if heliocentric, or centric except geocentric , --&gt; not earth .... change token<strong> <br /><br /> %metadata branch<br /><br />proposal: meta.checksum</strong> <br />rationale: to check integrity of data <br />definition : numerical signature of digital data <br />tag : Q

_##answer_ _add Q | meta.checksum | Numerical signature of digital data_

proposal: <strong>time.update </strong><br />answer : can use time.processing instead <br />suggestion : add update in the definition of this ucd <br /> _##answer agreed change token in the assigning tool _

<br /> # spectroscopic measures<br />#concept : reflectance

proposal: *phys.reflectance* <br />rationale : diff from albedo <br />definition, usage : radiance factor , (received radiance divided by input radiance) , may include thermal emission <br />% annotation master : to check ; consequence : change definition to albedo and remove reflectance <br />% | phys.albedo | Albedo or reflectance<br />derived usage :<br />Radiance Factor : arith.factor;phys.reflectance<br /><br /> _##answer add Q | phys.reflectance | Radiance factor, (received radiance divided by input radiance), may include thermal emission_

proposal: *phys.reflectance.bidirectional* <br />definition : bidirectional reflectance <br />tag : Q

_##answer add Q | phys.reflectance.bidirectional | Bidirectional reflectance_

proposal: <strong>phys.brdf</strong><br />rationale : specific term as much as psf for the community <br />definition : bidirectional reflectance distribution function <br />tag: Q <br /><br /> _##answer add Q | phys.reflectance.bidirectional.df | Bidirectional reflectance distribution function_

proposal: <strong>phys.reflectance.factor </strong><br />definition : reflectance normalized per direction cosine of incidence angle ??<br />tag : Q

_##answer add Q | phys.reflectance.factor | reflectance normalized per direction cosine of incidence angle_

<em>nb : check relevance and possible ambiguity with radiance factor... <br /></em>

%for normalized reflectance concept<br /> proposal *arith.ratio;phys.reflectance* <br />definition : reflectance normalized per reflectance at one wavelength

#shape of planetary objects

this is used to represent the 3D shape of object: a 3D lattice<br /><br /> proposal: <strong>phys.shape</strong><br />definition : 3D shape of a object <br />tag : Q<br />usage : phys.shape;meta.modelled for a 3D shape model<br />usage : phys.shape;pos.bodyrc.alt for elevation or terrain model (distribution of altitude on top of a reference ellipsoid or geoid )

_##discussion: postponed until a real case appears

# spectral polarization data <br /> #concept :spatial matrix<br />rationale: helps to identify or characterize measurement type

_##discussion: postponed until a real case appears

<br />proposal: <strong>phys.polarization.coherenceMatrix</strong><br />definition: coherence matrix of radio signals <br />usage phys.polarisation.coherenceMatrix;instr<br />tag:Q

_##answer add Q | *phys.polarization.coherency* | Matrix of the correlation between components of electromagnetic waves_

<em>not compatible to instr branch in the UCD tree <br /></em>

&lt;!--<br /> * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup<br />--&gt;
</div>

-- IVOA.MireilleLouys - 2020-02-03
This topic: IVOA > WebHome > IvoaSemantics > UCDList_1-4_RFM
Topic revision: r40 - 2020-03-08 - GiuliaIafrate