features for VOEvent v2.0

[Rob Seaman]

> My reading of STC is that this is also the case. What do you mean by  
> too complex? It's already included in the VOEvent 1.1 schema and  
> loaded by any validator when validating VOEvent 1.1 packets.

Bob, do you want to comment?

> No-one reads VOEvent 1.1 packets so the complexity is not an issue  
> there.

Not sure what you mean.

> Is the problem that we do not have any current tools to produce  
> VOEvents which can handle this richness?

That is certainly an issue.  Suggestions on STC-aware authoring and  
interpreting tools?

The chair would be delighted if ObsDataLocations could be created and  
consumed with great abandon.

Rob