[OASIS Issue Tracker] Updated: (ENERGYINTEROP-210) Critical: UMLClass Diagrams for EiEvent and Associated Classes, Operation Payloads(WD15, ln. 643-649)

[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-210:
--------------------------------------

        Parent:     (was: ENERGYINTEROP-324)
    Issue Type: Bug  (was: Sub-task)

> Critical: UML Class Diagrams for EiEvent and Associated Classes, Operation Payloads (WD15, ln. 643-649)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-210
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-210
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 lines 643-649; wd16 lines 643-649
>            Reporter: Girish Ghatikar 
>            Assignee: Girish Ghatikar 
>             Fix For: wd19
>
>
> a. Add mechanism for VEN to query the VTN to find what signals to expect for a specific program (e.g, pg 76 of OpenADR 1.0 has name of the type from EventInfoType).
> b. Better describe the relationship between Fig 9 and Fig 10.
> c. Describe the difference between EISendEventPayload and EISentEventPayload
> d. Allow mechanism for interactions between VEN and VTN for transactions/ For example, the eventStateID in OpenADR 1.0 is intended to handle transactions by avoiding data payload issues. Other option (may be better) is to create a framework that allow creation of multiple XSDs for each of the types.
> e. Add mechanism to handle Schema versions? (schemaVersion in OpenADR 1.0)
> f. Add mechanism to identify test event (testEvent in OpenADR 1.0)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira