[OASIS Issue Tracker] Issue Comment Edited: (ENERGYINTEROP-212) 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-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23563#action_23563 ] 

William Cox edited comment on ENERGYINTEROP-212 at 11/21/10 9:10 PM:
---------------------------------------------------------------------

(a) Where would the custom data go? The figure has 6 classes.

(b) We had been thinking that the event wouldn't get to the VEN if the optout were visible at the VTN. Good catch. Should the filter mechanism from EiConstraint be used, or a simple response "venOptout"? In either case, this avoid a race condition and should be included.

Note that the responses/ACKs are not defined in wd16 but are application depended; this should be addressed in a future draft (i.e., the contents of the EiCreatedEventPayload [typo in figure] attribute eventCreatedAck can be a string "Opted out". Other values not defined). SEE ALSO 217 and 232.

(c) test events are only in EiStatus, and were copied from OpenADR 1.0.  Other comments (e.g. ENERGYINTEROP-205 for extension, your -210) address this construct.

Do we have an explanation of why test events are important or useful? 

      was (Author: william.cox):
    (a) Where would the custom data go? The figure has 6 classes.

(b) We had been thinking that the event wouldn't get to the VEN if the optout were visible at the VTN. Good catch. Should the filter mechanism from EiConstraint be used, or a simple response "venOptout"? In either case, this avoid a race condition and should be included.

Note that the responses/ACKs are not defined in wd16 but are application depended; this should be addressed in a future draft (i.e., the contents of the EiCreatedEventPayload [typo in figure] attribute eventCreatedAck can be a string "Opted out". Other values not defined).

(c) test events are only in EiStatus, and were copied from OpenADR 1.0.  Other comments (e.g. ENERGYINTEROP-205 for extension, your -210) address this construct.

Do we have an explanation of why test events are important or useful? 
  
> UML Class Diagrams for EiEvent and Associated Classes, Operation Payloads (WD15, ln. 643-649)
> ---------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-212
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-212
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 643-649  wd16 643
>            Reporter: Girish Ghatikar 
>            Assignee: William Cox
>             Fix For: wd17
>
>
> a. Add provision for adding custom data (not critical)
> b. Describe and add a use case for VEN to respond to the event request (e.g., response that client is opting out).
> c. Describe and add a use case for VEN to participate in a test event. 

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