[OASIS Issue Tracker] Commented: (ENERGYINTEROP-490) Do not supporteiChangeEvent - Use cancel and create to do changes to existing event.

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

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

Girish Ghatikar  commented on ENERGYINTEROP-490:
------------------------------------------------

I agree with Ed K -- the change event is preferred over cancel and re-issue of event. If the building controls are programmed to respond automatically to any event issues, it must be able to accommodate the change event. If the building can't participate with the change, it can always opt out. 



> Do not support eiChangeEvent - Use cancel and create to do changes to existing event.
> -------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-490
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-490
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: wd25
>         Environment:  Psoter, Eugene of PG&E
>            Reporter: Bruce Bartell
>            Assignee: Ed Koch 
>             Fix For: wd28
>
>
> Technical: Regarding the EventServices, if an EiChangeEvent operation is performed, the consumers may have a significant amount of work to do to understand what is changed and then to update all the downstream parties regarding a change. My suggestion would be to not support this operation and if a change to an event was required, that the event be cancelled and a new event created which would trigger a new set of transactions regarding that 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