OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-481) 1039eiRequestEvent - consumer/provider is either; which event is requested, howto handle event cancel



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

Ed Koch  commented on ENERGYINTEROP-481:
----------------------------------------

I never quite understood the notion that the request can be initiated by either the VTN or the VEN.  I'm pretty sure that when we profile this in the OADR Alliance that we won't support VTN requesting the events from the VEN.

The request is suppose to return ALL events.  It is supposse to be a snap shot in time of all the events that exist and are in process. If in subsequent requests an event has disappeared from the list then it no longer exists and the implication is that it has been cancelled.  I've seen this explicitely stated somewhere.

> 1039 eiRequestEvent - consumer/provider is either; which event is requested, how to handle event  cancel
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-481
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-481
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: spec
>    Affects Versions: wd25
>         Environment: Bartell
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>
> Table 8-1 says consumer/provider for eiRequestEvent is either. Does this mean that either the VEN or VTN can initiate the request? This case is not covered in the sequence diagram provided in Figure 8-1. I think this is covered in Figure 1-2 w/o the either scenario.
> Which event is being requested? Is it "assumed" to be current or next if there is no current? If this is how it is done, what happens if an event is cancelled? When the VEN requests another event message and a new event shows up it is assumed the event if over? I thought 9.3.1 Interaction Patterns for the EiStatus Service would clear this up, but there is event id there either.

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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]