VOEvent used for solar knowledge base

[Frederic V. Hessman]

On 20 Jul 2007, at 5:34 pm, Rob Seaman wrote:

> On Jul 20, 2007, at 2:42 AM, Frederic V. Hessman wrote:
>
>> The initial SV proposal will be to create
>> 	- a "VOcabulary" schema for publishing simple vocabularies that  
>> can be translated between each other (if the multitude of  
>> available vocabularies aren't good enough for your special  
>> purpose, create your own as long as you publish it in a form so  
>> that others can use it; we'll have lots of good examples for this  
>> in the proposal);
>> 	- a very official UCD-like list of terms - the "Standard  
>> Vocabulary" itself - which can serve as a basic-vocabulary and the  
>> basic translation-medium.
>> The SV and UCD vocabularies would eventually have to be merged  
>> into one for long-term practicability but could exist side-by-side  
>> for an interim period.
>
> Perhaps you could comment on how the final assertion plays with the  
> goal of publishing multiple application specific vocabularies  
> (which I agree with strongly, particularly for VOEvent).

The whole point of VOcabulary will be to enable this.  A while back,  
there was some discussion of how to enable specific vocabularies and  
VOcabulary is ultimately the result of this discussion.

At the Tucson VOEvevnt/HTN meeting, I asked for suggestions about a  
VOEvent-specific vocabulary: things like

	GRB
	SNIa
	SNIb
	SNII
	orphanTransient
	...

I'd be happy to prepare a VOEvent-specific VOcabulary as part of the  
proposal if people would suggest terms they'd like to see.  The SV  
should - by definition - cover most of the UCD-like details, but  
VOEvent might like to use it's own abbreviated terms for things that  
take a bit of explaining (e.g. "GRB" =  
"ucd:em.gamma;sv:variation.burst;star.supernova;..."

> Will UCDs (and utypes, for that matter) simply become instances of  
> vocabularies?

There will be a VOcabulary representation of UCD, but this probably  
won't be the official one (for starts).

>> The bottom line is that we aren't yet there, so if you are worried  
>> about perfect VO-compatibility, using SV in UCD attributes should  
>> be verboten for now
>
> However, note that the VOEvent <Why> element relies on natural  
> language.  There is no particular reason that SV and UCD might not  
> be deemed "natural".

The point is that your <VOEvent> has two potential customers: real  
humans and computers.   The <Description>-like stuff is mostly or the  
former and SV+UCD mostly for the latter.

Rick

------------------------------------------------------------------------ 
------------------------
Dr. Frederic V. Hessman     Hessman at Astro.physik.Uni-Goettingen.DE
Institut für Astrophysik          Tel.  +49-551-39-5052
Friedrich-Hund-Platz 1         Fax +49-551-39-5043
37077 Goettingen                 Room F04-133
http://www.Astro.physik.Uni-Goettingen.de/~hessman
------------------------------------------------------------------------ 
-------------------------
MONET: a MOnitoring NEtwork of Telescopes
http://monet.Uni-Goettingen.de
------------------------------------------------------------------------ 
-------------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20070723/35f5de52/attachment-0001.html>