VOEvent and Heliophysics Knowledge Base: new schema

[Frederic V. Hessman]

>> Second, I went through the schema looking for potential vocabulary  
>> issues.
>> Whenever no obivous IAU thesaurus equivalent existed, I've added a  
>> new term based on the IMSAL list.
>> The basic list of tokens you appear to need and the present  
>> equivalents in the proposed IVOA thesaurus (labels and tokens) are:
>>
>> 	IMSAL		IVOAT (ivoat=http://www.astro.physik.uni-goettingen.de/ 
>> ~hessman/rdf/IVOAT/#)
>>
>> 	ActiveRegion	 "active regions" 			ivoat:activeregions
>> 	BrightPoint	 "bright points"  			ivoat:brightpoints
>> 	CME		 "CME" = "coronal mass ejections"	ivoat:coronalmassejections
>> 	CoronalDimming	 "coronal dimming" 			ivoat:coronaldimming
>> 	CoronalHole	 "coronal holes" 			ivoat:coronalholes
>> 	CoronalWave	 "coronal waves" 			ivoat:coronalwaves
>> 	Filament	 "coroanl plumes"??? 			ivoat:coronalplumes
>> 			 "solar filaments"??? 			ivoat:solarfilaments
>> 	FilamentEruption "solar filaments" 		 	ivoat:solarfilaments
>> 			+"eruptions" 				ivoat:eruptions
>> 	Loop		 "coronal loops"??? 			ivoat:coronalloops
>> 	Oscillation	 "solar oscillations" 			ivoat:solaroscillations
>> 	Sunspot		 "sunspots" 				ivoat:sunspots
>> 	EmergingFlux	 "emerging flux" 			ivoat:emergingflux
>
> This list looks good to me, although the LMSAL group will be the  
> experts on which solar vocabularly terms are of interest. Is there  
> an example of how the combination of two tokens (in the case of  
> FilamentEruption) works in practice, either in an existing schema  
> or other XML doc?

No, indeed: we've just barely got past the point of agreeing that  
there should be vocabularies/thesauri.

Indeed, this need will be common to all VO contexts, so it would be  
great to have a standard solution.   I once suggested using the  
rdf:Bag et al. elements, e.g.

	<rdf:Bag id="LMSAL:FilamentEruption">
		<rdf:li resource="ivoat:solarfilaments">
		<rdf:li resource="ivoat:eruptions">
	</rdf:Bag>

but I admit that it's not an elegant solution (assuming that our  
computers care).  Our original idea of using a UCD-like may have had  
many faults, but the ease of concatenation wasn't one of them.  Now  
that the semantics crew is about to suggest SKOS as the IVOA  
standard, we've almost defined the path but haven't defined the goal.

Rick