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) 1039 eiRequestEvent - consumer/provider is either; which event is requested, how to handle event cancel


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

William Cox commented on ENERGYINTEROP-481:
-------------------------------------------

A black start on a VEN or VTN can query its partners (assuming it knows them) and get the list of outstanding events.  These are ones that are pending, not past, and may extend indefinitely in the future.

The implication that an event has been canceled if it's  missing is used in the PULL patterns for the EiEvent services; it's what makes detection of canceled events possible via PULL.

Figure 811 line 1128 in wd28 omits this pair from the interaction diagram; they should be added.

The number of events to be returned include at least those that are current and near-term pending, where the definition of that is implementation defined.

This should be clarified in the text.



> 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
>            Priority: Minor
>             Fix For: wd29
>
>
> 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]