<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace">Hi Semantics,</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">I also agree with Markus' view.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Can I ask something that might derail the topic a bit?</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Would it be that bad to have controlled units lists </div><div class="gmail_default" style="font-family:monospace">alongside the VOUnit REC, using an approach similar </div><div class="gmail_default" style="font-family:monospace">to ADQL-UDF or SAMP-MTypes or ... i.e. non normative </div><div class="gmail_default" style="font-family:monospace">but shared within specific communities?</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">I think solar physics could be a case, but other </div><div class="gmail_default" style="font-family:monospace">specific domains might benefit.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Goal would be: clients aware of these might use them, </div><div class="gmail_default" style="font-family:monospace">unaware clients/researchers will just skip by.</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">I suppose all of these should go within the 'unknown' </div><div class="gmail_default" style="font-family:monospace">§2.11 quoted ones. </div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Pro: </div><div class="gmail_default" style="font-family:monospace">- common units outside the normative VOUnits can be </div><div class="gmail_default" style="font-family:monospace">used with some more meaning</div><div class="gmail_default" style="font-family:monospace">- VOunits can be kept clean of domain specific, even </div><div class="gmail_default" style="font-family:monospace">if widely used, solutions</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Cons: </div><div class="gmail_default" style="font-family:monospace">- extra parsing step for those who want to interpret </div><div class="gmail_default" style="font-family:monospace">them (remove quote, go on parsing)</div><div class="gmail_default" style="font-family:monospace">- extra controlled lists maintenance</div><div class="gmail_default" style="font-family:monospace">- (a sentence in VOUnits - §2.8? -)</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">Cheers</div><div class="gmail_default" style="font-family:monospace"> Marco</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno mar 31 mag 2022 alle ore 19:24 Patrick Dowler <<a href="mailto:pdowler.cadc@gmail.com">pdowler.cadc@gmail.com</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-size:small">I agree with Markus' last argument. This makes it 100% clear to me</div><div style="font-size:small"><br clear="all"></div><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div>--<br></div><div>Patrick Dowler<br></div>Canadian Astronomy Data Centre<br></div>Victoria, BC, Canada<br></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 30 May 2022 at 04:20, Markus Demleitner <<a href="mailto:msdemlei@ari.uni-heidelberg.de" target="_blank">msdemlei@ari.uni-heidelberg.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Tom,<br>
<br>
On Fri, May 27, 2022 at 05:35:54PM +0000, Tom Donaldson wrote:<br>
> Based on the discussion so far I’m disinclined to try to introduce<br>
> a change in astropy to support Sun, although as a data provider it<br>
> may still be the best option for us for a handful of columns. As<br>
> Markus said, it is unlikely to be handled automatically by a<br>
> client. I don’t see a way for astropy to map it to a concrete<br>
> unit, but I suppose it could be of limited use to a human.<br>
<br>
Ah, let's keep machine-readable info in machine-readable fields (like<br>
unit) and let's have human-readable info in human-readable fields<br>
(which would be description in this case). I submit<br>
<br>
unit: <empty><br>
description: Angular momentum relative to the sun<br>
<br>
even for humans is preferable to<br>
<br>
unit: Sun<br>
description: Angular momentum<br>
<br>
<br>
-- Markus<br>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div><font face="monospace">Marco Molinaro</font></div><div><font face="monospace">INAF - Istituto Nazionale di AstroFisica</font></div><div><font face="monospace">Osservatorio Astronomico di Trieste</font></div><div><font face="monospace">email <a href="mailto:marco.molinaro@inaf.it" target="_blank">marco.molinaro@inaf.it</a></font></div><div><span style="font-family:monospace">tel. [+39] 333 33 20 564 [also Telegram]</span><br></div></div></div></div></div></div></div>