[OASIS Issue Tracker] Updated: (ENERGYINTEROP-207) Critical:Include simple client information in EiEvent Service text and figure 9(WD15, ln. 619-644, figure 9)

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

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

William Cox updated ENERGYINTEROP-207:
--------------------------------------


(a) the EiEvent service allows getting all open events. Is there a need for Canceled events? Filtering can be done at the VEN. 

Should filtering be optionally done at the VTN?

(b) The operation models are addressed in the Program definition pending for wd17. This is related to the discussion about levels for event response with the number of levels and the number that's "normal/moderate".

(c) I don't understand what's requested in this item. EI is not a time server, there are many other protocols for that. A timestamp in each message could achieve this, but lower levels in messaging tend to do that. Why is this application level?

> Critical: Include simple client information in EiEvent Service text and figure 9 (WD15, ln. 619-644, figure 9)
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-207
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-207
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Bug
>          Components: spec
>    Affects Versions: wd15
>         Environment: Girish Ghatikar wd15 lines 619-644 and figure 9
>            Reporter: Girish Ghatikar 
>            Assignee: William Cox
>
> OpenADR 1.0 EventState.xsd includes SimpleClientDREventData with following elements, which are similar to those offered by other standards  (e.g., Zigbee/SEP):
> a, DR Event status (EventStatus in OpenADR 1.0)
>  - The EventStatus can take these values: NONE, FAR, NEAR, ACTIVE, CANCELED
> b. Operation Modes (OperationModeValue in OpenADR 1.0)
>  - the OperationModeValue can take these values: NORMAL, MOD, HIGH, SPECIAL
> c. Current Time (currentTime in OpenADR 1.0)

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