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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23632#action_23632 ] 

Girish Ghatikar  commented on ENERGYINTEROP-210:
------------------------------------------------

Bill,
a. This query information is described in #214.
b. Yes, adding some text as described will help.
c. Agree - add all operations to table on ln 623.
d. This reflects interactions between VEN and VTN for different types of DR events/programs (e.g., VEN participation in both CPP and DBP programs). in OpenADR 1.0, the eventStateID was intended to show different types of programs/events as part of one payload - in EI we should at least consider the OpenADR style, or even better allow multiple XSDs (one for CPP and one for DBP) that a VEN can poll. The architecture needs discussion.
e. OK -- useful for client testing and conformance. We should at least mention.
f. Yes! 


> 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: Improvement
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 lines 643-649; wd16 lines 643-649
>            Reporter: Girish Ghatikar 
>            Assignee: Girish Ghatikar 
>             Fix For: wd17
>
>
> 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