[OASIS Issue Tracker] Updated: (ENERGYINTEROP-410) Need to addcurrent value to signals

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

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

William Cox updated ENERGYINTEROP-410:
--------------------------------------

    Fix Version/s:     (was: wd25)

As a cached value, I have no problem with this. 

As time stamps that one tries to use to connect event components together, there are problems.

The core proposal would seem to be to add a currentValue to the header (EiEventBase) for the list, in conjunction with the SignalTypeType element it allows the use of that cached value.

Time stamps are fine, but shouldn't be used beyond the limits of reliability. They are NOT an event ID.

> Need to add current value to signals
> ------------------------------------
>
>                 Key: ENERGYINTEROP-410
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-410
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd22
>         Environment: Ed Koch
>            Reporter: Ed Koch 
>            Assignee: Ed Koch 
>
> Need to add a currentValue attribute to the EIEventSignalType.
> This information reflects the current value of the signal.  It is redundant information to the singal value scheudle and was used in OpenADR 1.0 to reflects the value of the signal at the time that the payload was created.  Even though this is redundant information it makes it much easier for simple devices to determine the current signal value without needed to parse the entire singal schedule. 
> Note that I believe the payload created time is reflected in the EIEventCreated.createdTime attribute. With respect to the RequestEventPayload payload type we may be missing this attribute.
> SEE ATTACHED COMMENTS WTC

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