|
|
ENERGYINTEROP-513
|
ENERGYINTEROP-515
The eiCreateAvailPayload has one confusing issue: It is our understanding that the VEN would specify the behavior characteristic (Force, etc) but behavior does not appear in the create payload.
|
William Cox (Inactive)
|
Toby Considine (Inactive)
|
|
Closed |
No Action
|
|
|
|
|
|
|
ENERGYINTEROP-510
|
ENERGYINTEROP-515
The schema payload for eiRegisteredParty contains multiple undefined IDs
|
Gerald Gray (Inactive)
|
Toby Considine (Inactive)
|
|
Closed |
Fixed
|
|
|
|
|
|
|
ENERGYINTEROP-509
|
ENERGYINTEROP-515
Section 10 - How does one know whether the marketContext returned in a Status response is just a confirmation of the request or something different?
|
Toby Considine (Inactive)
|
Toby Considine (Inactive)
|
|
Closed |
Fixed
|
|
|
|
|
|
|
ENERGYINTEROP-508
|
ENERGYINTEROP-515
Section 10 - Why would the requestStatus operation contain market context in the payload? Perhaps having an ID of some sort might make sense to filter the request response, but why the entire marketContext?
|
William Cox (Inactive)
|
Toby Considine (Inactive)
|
|
Closed |
Fixed
|
|
|
|
|
|
|
ENERGYINTEROP-507
|
ENERGYINTEROP-515
Section 10 - There is confusion about how to get a VTN Market Context outside the framework of a specific event
|
Toby Considine (Inactive)
|
Toby Considine (Inactive)
|
|
Closed |
Fixed
|
|
|
|
|
|
|
ENERGYINTEROP-506
|
ENERGYINTEROP-515
Section 4.4 - "These durations are expressed in the Emix Resource Description" - Emix Resource Description not included
|
Toby Considine (Inactive)
|
Toby Considine (Inactive)
|
|
Closed |
Fixed
|
|
|
|
|