Hi,
Please find enclosed the first stab at the VOEvent extension schema as presented and discussed at the last couple of IVOA meetings.
The schema defines two new resource types: VOEventStream and VOEventServer. It also defines two new capabilities: Subscription and SimpleEventAccess. The latter one is really a placeholder until the details of SEAP have been nailed down (expect an internal Working Draft of the specification by IVOA Baltimore).
Two instance documents are provided for illustration - a VOEventStream instance corresponding to the VOEvent GCN stream and a VOEventServer instance for Caltech.
The purpose at the moment is to figure out what metadata we are missing and whether this organisation makes the most sense.
Cheers,
Matthew