VOEvent Update

[Rob Seaman]

Do you need more than:

<WhereWhen>
    <ObsDataLocation>
        <ObservatoryLocation/>
        <ObservationLocation/>
    </ObsDataLocation>
</WhereWhen>

This is already legal VOEvent, whatever the prototype schema says. I'm
in a session at DPS with a slow network, so am having trouble tracking
this down in coeval STC, but the intent was full STC support for
observations of all types, including orbital elements, planetary
surfaces, the Sun, etc., from all observers in space or ground (or from
other bodies in the solar system, for that matter).

By all means we should clarify the text and/or extend the schema for
VOEvent-2 while considering what to do for VOEvent-3.

Rob
--



On 10/17/17 8:12 AM, Tim Jenness wrote:
>
>> On Oct 17, 2017, at 06:40, Pierre Le Sidaner <pierre.lesidaner at obspm.fr> wrote:
>>
>> Dear All
>>
>> I have been to a VOEvent workshop dedicated to hight energy astronomy on the frame of Asterics program. There was a lot of interesting presentation on large use of event, right now and also in the near future. Dave was there and he will make a report on it.
>> This mean that we should move carefully the schema of Event. On the other hand, in planetary science we point out that the wherewhen part could not allow description of planetary objects and even may be a problem for satellite position and time description. Even spherical coordinate could be a problem as all coordinate share the same unit.
>>
>> We want to propose a possible evolution of VOEvent schema to 2.1 that will keep all actual VOEvent 2.0 valid and give more possibility for larger description on Wherewhen
>> If there is  15 mn free in the VOEvent session I would like to present that
>>
> Would we get that if we allowed STC to be embedded in WhereWhen? I know we have had arguments about this over the years but I feel that we should be allowed to be pedantically correct in WhereWhen even if we also allow the simplified form.
>
> — 
> Tim Jenness
>