[Semantics] Re: UCDs and arrays : histogram case

[Mireille Louys]

Hi Markus , Hi all,

Thanks for uploading this requirement on the RFMforUCD page.

I did not succeed in visualising the table example you mentionned . I 
there a special way to find it  via taphandle , and or topcat?

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 .

if we would allow it to be Q status , then we can cover various cases :

  * /stat.histogram/  as a suffix is needed when you do need to state
    the histogram of what you are describing. For instance
      o /stat.error;stat.histogram/  would mean the stat histogram of
        position error , for instance
      o /mag;stat.histogram for the histog of magnitudes on one region
        for instance
        /
      o /....
        /

Do we have cases  where several measures / columns are described with a 
histogram computation for each  in the same table?

We can discuss this on this list , and I would also be happy to discuss 
this with examples at the next Interop .

thanks , Mireille


Le 09/05/2018 à 09:28, Markus Demleitner a écrit :
> Hi Semantics,
>
> On Tue, May 08, 2018 at 11:34:44PM +0200, Baptiste Cecconi wrote:
>> I tend to say that stat.distribution would be a better option than
>> stat.probability or stat.likelihood.
> Well, I've made it stat.histogram, and I've put in some rationale on
> http://wiki.ivoa.net/twiki/bin/view/IVOA/RFMforUCD
>
>> Markus, please send a request to the UCD working group, as
>> described here:
>> http://wiki.ivoa.net/twiki/bin/view/IVOA/IvoaSemantics#UCD_list_update
>> <http://wiki.ivoa.net/twiki/bin/view/IVOA/IvoaSemantics#UCD_list_update>
>> (it will be good opportunity to check the process... :-)
> First feedback on process issues:
>
> (a) there should be a clear template for how such a proposal should
> look like; the existing proposals are a bit nonuniform.  I've make it
> "Use Case", "Proposed Solution" and a section "Discussion" now.
>
> I have a hunch that we should plan for discussions to take place on
> the mailing list, though, so I wonder if that last bit shouldn't just
> be links into the list archives.
>
> (b) I was severely confused as to which page to put my proposal on.
> I've eventually decided the idea is to put it on RFMForUCD directly
> and then archive away things now and then.  I like that.  But please
> don't use headlines as link anchors to archive pages; they should be
> in enumerations.  If I had to do it, I'd write
>
>     * [[UCDList1dot42017June2018FebRFM|Archive: UCD proposals 2017-05 through 2018-04]] (leading up to list v1.5)
>
> and go on like this.
>
> (c) I had a strange mixture of total confusion and reassurance I was
> right putting my proposal directly to RFMforUCD when I discovered in
> the source of RFMforUCD a div with the old material hidden away with
> CSS.  Let's not do that -- twiki keeps your history, so in general
> there's no reason to comment things out.
>
>             -- Markus

-- 

-- *Mireille Louys, Assistant Professor * CDS IPSEO, MIV, Laboratoire 
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 tel: +33 3 68 85 24 34

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/semantics/attachments/20180520/c4540d1b/attachment.html>