[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=23572#action_23572 ] 

William Cox commented on ENERGYINTEROP-210:
-------------------------------------------

Comments/questions interleaved.

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). 

*What specific operations and payloads do you suggest?

b. Better describe the relationship between Fig 9 and Fig 10.

*Figure 9 is a full class diagram for the EiEvent class and its associated classes. In Figure 10, the "associated classes' are not shown for clarity. The document should make that clear for all of the "Operation Payload" sections.

c. Describe the difference between EISendEventPayload and EISentEventPayload

*It's an error. The SEND version should not be in the figure.  There is no such operation in the table on line 623.

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.

*Don't understand the comment/suggestion. Please create a new item including only (d). EventInfoTypeID is a class, eventStateID seems to be what you're suggesting but it's not clear how you suggest applying it.

e. Add mechanism to handle Schema versions? (schemaVersion in OpenADR 1.0)

* This is scaffolding. The use of schemaVersion is important and useful, but made some diagrams more cluttered. It should be in the next version.

f. Add mechanism to identify test event (testEvent in OpenADR 1.0)

*See also 212, 205

This is one of several comments related to test events. See 205, 210 (this item), and 212.

> 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: William Cox
>             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