features for VOEvent v2.0

[Matthew Graham]

Hi,

On Apr 7, 2010, at 4:38 PM, Rob Seaman wrote:

>> 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.

You have software that looks at the VOEvent packet, you don't read it like an ATEL.

>> 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.

I am working on a Python library to support VOEvent 1.1 including STC.

	Cheers,

	Matthew