VOEvent used for solar knowledge base

[Frederic V. Hessman]

>> The current proto-proposal for an appropriate "Standard  
>> Vocabulary" description fits easily and would be
>> ucd="phys.magneticField;morphology.loop"
>
> I like Rick's idea for inclusion of lmsal event concepts as UCDs.  
> I've just had a look at the UCD 1+ vocabulary at http://vizier.u- 
> strasbg.fr/UCD/ucd1p-words.txt to see what overlaps exist between  
> HPKB defined event types and related parameters (more details at  
> http://www.lmsal.com/helio-informatics/hpkb/details_b.html). For  
> example, I see phys.magField and src.morph, but nothing for "loop".  
> What is the VOEvent packet etiquette for adding ucd attributes with  
> values that might someday be in the UCD list or the "Standard  
> Vocabulary" but aren't yet?

Good question: those of us working on the "Standard Vocabulary" know  
that there are fundamental collisions involved:  the UCD1+ vocabulary  
is very tightly controlled (for obivous and good reasons) but we see  
a need to democratize the use of VO vocabularies; we want to go far  
beyond the current table-labeling of UCD but want to keep the UCD- 
like flavor; we want to permit specialized vocabularies but don't  
want semantic chaos.

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.

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 (after all, we're still working on the intial  
proposal) but hopefully OK in the near future (hopefully Andrea will  
be able to present the proposal at the next IVOA meeting).  The basis  
has to be done carefully and officially, but - once adopted - the  
idea makes things much simpler and much more flexible.

> If HPKB concepts and parameters can be mapped to existing or  
> candidate UCDs, then ucd attributes as shown in Rick's example  
> could be added to the SolarSoft vobs/ontology package that  
> generates event packets for HPKB. LMSAL guys, any comments?

I'd wait for the official proposal but keep pushing the IVOA when it  
does appear so that we can quickly have something to start playing  
with.  The proposal will at least be in a form that can actually be  
used (i.e. a published schema for "VOcabulary" and the proposed SV in  
this format).

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/20070720/805532c4/attachment-0001.html>