<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Times New Roman, Times, serif">Hi Markus, hi all, </font><br>
</p>
<br>
<div class="moz-cite-prefix">Le 21/05/2018 à 14:31, Markus
Demleitner a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:20180521123134.oemolvqibjfn2q5z@victor">
<pre wrap="">Hi Mireille,
On Sun, May 20, 2018 at 10:15:47PM +0200, Mireille Louys wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I did not succeed in visualising the table example you mentionned . I there
a special way to find it via taphandle , and or topcat?
</pre>
</blockquote>
<pre wrap="">
Just enter the TAP service URL (or select "GAVO DC TAP" from the
given list of services) in your client and execute the query
-- did this not work for you?
</pre>
</blockquote>
Sorry , Markus. I first tried to look via Taphandle and gaiadr2 and
lost my way. <br>
The query example as you recommended in the RFM page works fine .
Thanks <br>
<blockquote type="cite"
cite="mid:20180521123134.oemolvqibjfn2q5z@victor">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">for the choice of the ucd label, I vote for "stat.histogram" , but I suppose
it makes sense to bind it to the measure it has been collecting .
</pre>
</blockquote>
<pre wrap="">
Certainly stat.histogram would need to admit declaring what has been
aggregated. However, I'm pretty sure stat.histogram still needs to
be P. Consider the existing term stat.error, which is P because an
<error of X> is *not* somehow a subclass of <X> (contrary to, say,
stat.max, which consequently already is Q).
Analogously, a <histogram of X> is a different beast from <X>, and
clients that, for instance, cut off trailing atoms to figure out
roughly what something is would be completely mislead.
</pre>
</blockquote>
yes you are right , the context to interpret the aggregated measure
is needed . <br>
I had in mind we might want to trace the histogram of an error (
very usual requirement) <br>
then if stat.error and stat histogram are both P, we cannot choose
: <br>
<br>
stat.error;phot.mag.V is the error on a magnitude , and if I want
to give the UCD label for the histogram of this quantity, I would
like to have <br>
stat.error;phot.mag.V;stat.histogram <br>
<br>
One could even decide stat.histogram can only be suffix , because we
will interprete the meaning of the aggregated measure first.<br>
<br>
I agree it is tricky to put combination rule in this case . <br>
<br>
What are the other use-cases where we would have to use
stat.histogram for the content of a column? . <br>
Tap 1.1 allows that but do we want to encourage multiple values
inside a column ? <br>
I assume if this would be generalized, the risk to break the ucd
labeling consistency is not null. <br>
<br>
Many thanks for your feedback on this. <br>
Mireille <br>
<blockquote type="cite"
cite="mid:20180521123134.oemolvqibjfn2q5z@victor">
<pre wrap="">
So, in the example, the UCD of the dist column should be
stat.histogram;phot.mag.V
(it's not yet, but based on your feedback I'll put it in soon as a
prototype).
-- Markus
</pre>
</blockquote>
</body>
</html>