VOEvent References

[Frederic V. Hessman]

I understand, and this is all very good, but does IVOA then have to  
create VO standards for everyone who might need it?  My examples of  
SWIFT telemetry and Celestia simulation files weren't (entirely)   
tongue-in-cheek.

If what we need is an astronomical label in a standardized format,  
then why not simply have a means of defining and using standardizable  
astronomical labels and leaving the rest to the users?  If someone  
wants to create blue-painted VOEvents, then let's let them say "blue"  
and not have to hand them the paint.

Rick

On 21 Mar 2011, at 17:35, Steve Allen wrote:

> On Mon 2011-03-21T15:44:09 +0000, Norman Gray hath writ:
>> I know of the 'vnd.'  route, and have heard of some sort of MIME
>> fast-track, but wasn't sure if these were the same thing.  Do you  
>> know
>> of the relationship between them?
>
> RFC 4288 changed the rules.  Section 3.1 has the notion of the
> "standards tree".
> 	Registrations in the standards tree MUST be approved by the
> 	IESG and MUST correspond to a formal publication by a
> 	recognized standards body.
> That's supposed to mean that after the international standard exists,
> the internet part of getting the MIME type is just "announce and  
> expect
> approval".
>
> --
> Steve Allen                 <sla at ucolick.org>                WGS-84  
> (GPS)
> UCO/Lick Observatory--ISB   Natural Sciences II, Room 165    Lat   
> +36.99855
> 1156 High Street            Voice: +1 831 459 3046           Lng  
> -122.06015
> Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt  
> +250 m