VOEvent, unique id's, and IVORNs

[Rob Seaman]

Matthew says:

> Yes, the IDs are currently incorrect; however, the publisher ID  
> does not need to be an Organisation resource but should rather be  
> registered as a VOEvent Publisher resource. The problem, of course,  
> is that we have not yet worked out the metadata that we require to  
> describe VOEvent resources in the registry. This is something we  
> should try and get ready for discussion at VOEvent III/IVOA Interop.

Yes, characterizing the VOEvent "footprint" in the registries seems  
like a key issue for the next six months.

Note that Roy and I (and maybe some others) had some discussions  
about the packet IDs late in the run up to the v1.0 spec.  I'm sure  
the document is still not capturing the essence of the situation, but  
the intent was certainly to allow IDs as described in the last few  
messages.

Rob