Major See also ENERGYINTEROP-595 and ENERGYINTEROP-597. This partially addresses ENERGYINTEROP-481 (previously closed).
The following use case was described:
A VEN pushes a list of the event IDs it's working on to its VTN. This can be symmetric, allowing for push of relevant and/or restricted set of Event IDs.
The events are those that are "pending".
This relates to text using pending at table/text lines 1011, 1164, 1344, and 1869.
Add a definition of Pending:
A PENDING event is one where the present time is within the closed interval from and including the notification time, and to and including the end time.
(in other words, the present is in the [notification-time, end-of-event-time] closed interval)
I propose that the service be named not Status (because it's not clearly event status) but"EiPushPendingEvents".
Source is either Ven or VTN. May be limited to those that the sender wants to communicate. No response, as it's a hint and oneway.
Attributes of the request:
List of EventIDs, possibly empty
VEN ID [0..1]
VTN ID [0..1]
emix:MarketContextType [0..1] - if absent, relationships in any market context that the destination and source of the request are engaged in.