VOEvent - Param comment

Alasdair Allan aa at astro.ex.ac.uk
Mon Aug 7 08:42:11 PDT 2006


Petr Kubanek wrote:
> To solve that, I recomend putting UCDs in tags. So instead of the  
> example:
>
> <Param name="TRIGGER_NUM" value="114299" ucd="meta.id" />
> <Param name="RATE_SIGNIF" value="20.49"  ucd="stat.snr" />
> <Param name="GRB_INTEN  " value="73288"  ucd="phot.count" />
>
> Let's have something like:
>
> <GRB>
>  <trigger_num>114299</trigger_num>
>  <rate_signif>20.49</rate_signif>
>  <grb_inten>73288</grb_intent>
> </GRB>
>
> etc. for other events (transits,..).

For every type of event every imaginable?

> In schema that will maternize as choice for different event types.

That's a lot of different schema, and a new one every time you want  
to send an event that's even slightly different from the "standard"  
types. I don't think that's particularly practical, and I think it  
presents a massive hurdle to the users and publishers that people  
won't be prepared to accept.

Al.



More information about the voevent mailing list