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] Updated: (ENERGYINTEROP-208) Critical:Provide mechanism for events schedules inside of EiEvent Service (WD 15,ln. 627-644)



     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated ENERGYINTEROP-208:
--------------------------------------

       Proposal: 
- Add relation to notification time, start/end time, duration, etc. In OpenADR 1.0 described as scheduleType (pg 76)


  was:- Add relation to notification time, start/end time, duration, etc. In OpenADR 1.0 described as scheduleType (pg 76)

    Environment: Girish Ghatikar WD15 lines 627-644
    Description: 
2. Provide mechanism for events schedules inside of EiEvent Service (WD 15, ln. 627-644):
- Is this part of Emix::wscal::Sequence gluon? 

  was:
2. Provide mechanism for events schedules inside of EiEvent Service (WD 15, ln. 627-644):
- Is this part of Emix::wscal::Sequence glue-on? 

     Resolution: This should be wscal::Sequence (if the reference is to the class in Figure 9 labeled "Emix::wscal::Sequence" containing a gluon.

The comment for scheduleType in OpenADR 1 schemas for this enumeration (values None, Dynamic, Static) is

• None - there is no schedule and thus the Event Info does not change values during the entire DR event window.
• Dynamic - The time schedule is not fixed during configuration, but can be set when the DR Event is issued. =
• Static -=The schedule is fixed when the DR program is configured within the DRAS

These correspond to

Static -- a fully bound wscal:Sequence
Dynamic -- a partially bound wscal:Sequence, and when the event is issue the sequence is bound to a starting time (e.g.)
None -- no schedule

Please explain how the example of scheduleType does something different than the (perhaps unclear) application of wscalendar Sequence.

> Critical: Provide mechanism for events schedules inside of EiEvent Service (WD 15, ln. 627-644)
> -----------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-208
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-208
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: spec
>    Affects Versions: wd15
>         Environment: Girish Ghatikar WD15 lines 627-644
>            Reporter: Girish Ghatikar 
>            Assignee: William Cox
>
> 2. Provide mechanism for events schedules inside of EiEvent Service (WD 15, ln. 627-644):
> - Is this part of Emix::wscal::Sequence gluon? 

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